[Typescript] - Error when setting agent configuration

It looks like there might be an issue setting/getting the agent configuration. If you do:
const config = agent.getConfiguration();
agent.setConfiguration(config);

I get the error:
Uncaught (in promise) ReferenceError: AgentErrorStates is not defined
    at Agent.setConfiguration (connect-streams.js?550c:24094)
    at setDeskphone (actions.ts?2313:110)
    at eval (actions.ts?375c:30)
    at new Promise (<anonymous>)
    at setAudioSettings (actions.ts?375c:14)
    at eval (actions.ts?375c:11)
    at new Promise (<anonymous>)
    at loadAudioSettings (actions.ts?375c:9)
    at Object.eval [as __] (index.tsx?ee8a:114)
    at j (index.js?a178:368)

The error response from amazon-connect-streams isn't working, I think this line should be connect.AgentErrorStates: https://github.com/amazon-connect/amazon-connect-streams/blob/master/src/api.js#L464
But the reason the error gets thrown at all is because the response from agent.getConfiguration() doesn't include locale:
configuration.agentPreferences.locale = undefined

Workaround
To avoid the error i'm using:
const config = agent.getConfiguration();
  const newConfig = {
    ...config,
    agentPreferences: {
      ...config.agentPreferences,
      locale: 'en_US'
    }
  };
  agent.setConfiguration(newConfig)

Hi @tjw0051, hope you are well.
The workaround didn't work for me, here is my code snippet:
function switchToPhone() {
console.log("In Swtich Phone");
var config = myagent.getConfiguration();
config.extension = "+18005550100";
config.softphoneEnabled = false;
config.agentPreferences.locale= 'en';
myagent.setConfiguration(config, {
    success: function () {
        console.log("Config changed");
    },

    failure: function (err) {
        console.log("Error " + JSON.stringify(err));
    }

});

}
See if you can help.
Thanks in advance.

I think you're correct that the line in api.js should use connect.AgentErrorStates.INVALID_LOCALE. We'll fix this and update this issue when the change is made.
However, per the documentation for agent.setConfiguration(), "only the extension and softphoneEnabled values can be updated." We don't currently support setting other fields using this function, and for getConfiguration we only support the documented fields, currently: agentStates, dialableCountries, extension, name, permissions, routingProfile, softphoneAutoAccept, softphoneEnabled, and username.

Closing this issue as the bug is fixed in version 1.6.9.


Upgrade to the currently best password hasher

See this for details:
https://docs.djangoproject.com/en/1.10/topics/auth/passwords/#how-django-stores-passwords
We're fine with adding extra dependencies, so it seems like we should upgrade to the best available option.

@timabbott can you suggest me best option?

@sinwar did you read the Django doc I linked to?  It explains that Argon is the best option today.

sorry I didn't read. I'm taking this up @timabbott


DOC: add docs on parallel execution and thread safety

The thread safety part is inspired by the NumPy docs on the same topic: https://numpy.org/devdocs/reference/thread_safety.html
The thread safety docs are added now because there will likely be significant interest in them from users and downstream projects testing free-threaded Python.

I did a final pass over the raw text and checked the basic formatting of the rendered version linked from CircleCI.
merged, thanks


New version: TechSmith.Camtasia version <IP_ADDRESS>812

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978334960
2024-04-02 17:57:38.426 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFCC59C11F: (caller: 00007FFFCC328D6F) LogHr(1) tid(157c) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFCC4A2B08: (caller: 00007FFFCC54BC20) Exception(1) tid(157c) 8A15005E ]
2024-04-02 17:57:38.426 [REPO] Failed to open available source: msstore
2024-04-02 17:57:41.614 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFCC59C11F: (caller: 00007FFFCC328D6F) LogHr(1) tid(17e0) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFCC4A2B08: (caller: 00007FFFCC54BC20) Exception(1) tid(17e0) 8A15005E ]
2024-04-02 17:57:41.615 [REPO] Failed to open available source: msstore
2024-04-02 17:57:48.742 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFB164C11F: (caller: 00007FFFB13D8D6F) LogHr(1) tid(3f8) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFB1552B08: (caller: 00007FFFB15FBC20) Exception(1) tid(3f8) 8A15005E ]
2024-04-02 17:57:48.742 [REPO] Failed to open available source: msstore
2024-04-02 17:57:51.748 [CLI ] Package hash verification failed. SHA256 in manifest [0685c3054bbc59a1b1502257d0dafdf4dec22f0965ada2ea88939b4f729b795c] does not match download [d652ace87dc6b2b4bcf85e17e099a6928414134a71e4f5e45e580148c759a685]

(Automated response - build 876.)

Automatic Validation ended with:

Installation failed with exit code -1978334960
2024-04-02 17:57:38.426 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFCC59C11F: (caller: 00007FFFCC328D6F) LogHr(1) tid(157c) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFCC4A2B08: (caller: 00007FFFCC54BC20) Exception(1) tid(157c) 8A15005E ]
2024-04-02 17:57:38.426 [REPO] Failed to open available source: msstore
2024-04-02 17:57:41.614 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFCC59C11F: (caller: 00007FFFCC328D6F) LogHr(1) tid(17e0) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFCC4A2B08: (caller: 00007FFFCC54BC20) Exception(1) tid(17e0) 8A15005E ]
2024-04-02 17:57:41.615 [REPO] Failed to open available source: msstore
2024-04-02 17:57:48.742 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!00007FFFB164C11F: (caller: 00007FFFB13D8D6F) LogHr(1) tid(3f8) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!00007FFFB1552B08: (caller: 00007FFFB15FBC20) Exception(1) tid(3f8) 8A15005E ]
2024-04-02 17:57:48.742 [REPO] Failed to open available source: msstore
2024-04-02 17:57:51.748 [CLI ] Package hash verification failed. SHA256 in manifest [0685c3054bbc59a1b1502257d0dafdf4dec22f0965ada2ea88939b4f729b795c] does not match download [d652ace87dc6b2b4bcf85e17e099a6928414134a71e4f5e45e580148c759a685]

(Automated response - build 876.)

Hi Stephen, I'm running this again but is it something to do with the dependency?


scrollbar and resize examples

I'm not very bright with CSS and I've been trying to recreate the dat.GUI features of automatic scrollbar when overflowing and resize width by using a container. Everything I've tried has failed so far and it's all rather embarrassing! Is there an example out there, that anybody knows of, where tweakpane can be given scroll and resize abilities?

Similar issue: #98
If this doesn't resolve your issue, could you share a demo or an example of the behavior of dat.GUI?

Yes, I had found #98 but the example is no longer there (404). The demo would be to create a long dat.GUI pane and you can resize it by dragging the left edge and use the mouse wheel to scroll parts of it into view.

Yes, I had found #98 but the example is no longer there (404).
The demo would be to create a long dat.GUI pane and you can resize it by dragging the left edge and use the mouse wheel to scroll parts of it into view.

Both of those features are out of scope of Tweakpane, so you should implement them yourself.
1. Scrolling
You should set height and overflow: scroll of the pane container (default value: .tp-dfwv). For example:
:root .tp-dfwv {
  position: fixed;
  overflow: scroll;

  top: 0;
  bottom: 0;
  right: 0;
}

2. Resizing
It is more complicated than the previous one so I won't show the actual code. In my expectation, you have to add an element into the edge, handle mouse events, and then apply changes to the pane container width. Some search keywords like js element resize drag may help you.

Yes, out of scope, I fully understand. I've been using jquery-resizable-dom on a container to make the Tweakpane horizontally resizable but then giving the container a fixed vertical size to allow overflow scrolling (by tying to the bottom) covers part of my three.js canvas so it cannot respond to mouse events.
I'll keep trying to come up with something that works, and I'll post it here if useful to others using tweakpane to replace dat.GUI, but I'm just not very smart with CSS.
I was just hoping there was a less hacky way of achieving these dat.GUI built-in features.


remove support for batch_size from dream.py

Per https://github.com/lstein/stable-diffusion/issues/204, this doesn't seem to be getting much use. It's annoying because the later images do not have a recoverable seed - that's both a bad experience for users and problematic internally because it means you end up with multiple images with the same seed/config.
I haven't changed any of the more "backend" code, like the diffusers; training and everything should work just the same as before. This only effects the dream.py and simplet2i wrappers.
PngWriter still has some code which refers to batch_size, but that code is in need of further refactoring, which I'll get to after this.

sliiightly mourned but only used in cases i was generating a lot of stuff at once. I think it reduced the time to make huge batches of images by about 10-15% give or take

I've been experimenting with batch sizes in comparison with AUTOMATIC1111's implementation.
From a few experimentations on a GTX 1080, I've discovered rather replicably that increased batch sizes (for GPUs that support it) can significantly cut down generation times; e.g. a batch size of 4 (compared to 4 iterations of 1) can cut down generation times from 20%-40%. When generating a large number of images, the time reduction is even more prominent.
Was surprised to discover that this feature has been removed from InvokeAI's implementation. Would have been great if this feature was still around, but I understand the difficulty presented by conflicting/unrecoverable seed values and how this makes SD non-deterministic.

yeah, since switching to automatic1111 i only do things in batches of like 6 because of the huge speed increase on an RTX 3090.


'Execute SQL script' runs statements in parallel if more than 2 results are present in Results panel

System information:

Operating system (distribution) and version : MacOS Catalina 10.15.7
DBeaver version : 7.2.3
Additional extensions

Connection specification:

Database name and version DB2 9.5
Driver name DB2 LUW
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
Problem appears when trying to run a script with multiple lines using the 'Execute SQL script' button. If there are no results for that script already it run ok, all the statements in order. If there are more than 2 results present it runs all the statements in the script in parallel.
Steps to reproduce, if exist:

Open/Create script with multiple statements.
Run 2 statements, generating 2 results in the result panel
Click on 'Execute SQL script' button.
All the statements will be ran in parallel

I try to reproduce the issue according your steps.

Execute a script to receive several result tabs with following statements: drop the table, create the table, select * from the table and from another table.
Execute the script again.

The execution is succesfull: the table is dropped, then created and a data is displayed from the tables.
What does go wrong in your case?

I have a similar problem since I update my version from 7.2.1 to 7.2.5.
Steps to reproduce:

Execute script (+100 statament) - Run OK
Move to other sql files execute singular statement - Run OK
Execute the first step again  - - Run ERROR - statements in parallel

Cannot reproduce. Here is the test statement:
SELECT * FROM QTEST2;
TRUNCATE QTEST2 immediate;

Cannot reproduce. Here is the test statement:
SELECT * FROM QTEST2;
TRUNCATE QTEST2 immediate;

Try with:
SELECT * FROM QTEMP1;
TRUNCATE QTEMP1;
INSERT INTO QTEMP1 VALUES ('Key1');
TRUNCATE QTEMP2;
INSERT INTO QTEMP2 VALUES ('Key1');
Actually the same happen with 'Execute SQL Statements' as described in thi issue
https://github.com/dbeaver/dbeaver/issues/10425

Works as expected in my case. Please see. What we do differently?

and

When I click on 'Execute SQL Script' The queries should run in order, but the start all at once.

Please write a video

Should be fix as part of https://github.com/dbeaver/dbeaver/issues/10280. You can test EA version https://dbeaver.io/files/ea/

Fixed in version 7.3.1


upload button?

hey, there used to be an upload option when you right clicked on a file, is that gone? how can we upload images and other media through this plugin? thanks

I'm on Atom 1.18.0-beta0 and I too can no longer find the upload option within the context menu.

Downloaded Atom (ver 1.17.1 x64) & Remote-ftp (0.10.7) today for the first time. No apparent way to upload file from context menus. :(
Download is there :)
Should we assume it's coming back? (Based on the assumption it was there in the first place)

Hello
To fix the problem, go to (.atom/packages/remote-ftp/menus) and open remote-ftp.cson
Then replace line 3:   '.tree-view.full-menu': [   by   'atom-text-editor, .tool-panel.tree-view .file':[
line 8:   '.tree-view.multi-select': [   by     '.tool-panel.tree-view .header.list-item':[
Then just restart Atom.

Thanks, Ekrnox!
updating the remote-ftp.cson worked for me :D

Ah! I found that file yesterday, and was trying to work out what was wrong with it. I thought the reference may have been wrong.
Thanks for the fix :)

Hey guys, unfortunately @Ekrynox 's workaround did not work for me. I got Atom 1.17.2 ia32 (Win7-64) and remote ftp 0.10.7. I just downloaded the actual git package (oddly enough 0.10.2) and switched the content of "remote-ftp.cson". Line No. 3 would probably have been enough, but I am on schedule and try it later.

...Ekrynox 's workaround did not work for me...

The Error btw is described here: https://github.com/mgrenier/remote-ftp/issues/677

@ParkerD13 The updated, working plugin can be downloaded from this repo in the current master branch. Just download the zip here, and replace your .atom/packages/Remote-FTP file with the zip you downloaded and it should be good.
See https://github.com/mgrenier/remote-ftp/issues/796#issuecomment-303288019. Sounds like it should be updated in atom relatively soon as well.

@ParkerD13
Just for reference, I tried the above and it worked. But I should point out that where he's used the word "by", he meant the word "to":
line 3:
Change
'.tree-view.full-menu': [
to
'atom-text-editor, .tool-panel.tree-view .file':[
line 8:
Change
'.tree-view.multi-select': [
to
'.tool-panel.tree-view .header.list-item':[
Give that a shot if you're still stuck.


fix: upgrade to version 3.1.261

from: https://github.com/jenkins-x/jx-cli

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign daveconde
You can assign the PR to them by writing /assign @daveconde in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
1396bfd0b9e5e2caf8c01230a822adbf74696e7c
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest


Failing URL list download can result in infinite loop and may stall the entire pipeline

Two weeks ago, I was playing around with alternatives for the lately very unstable transfer.sh and launched job 5ivs1btcd49uxizyj3nll0azt. Turns out that the pipeline did not like this at all:
Exception raised in DownloadUrlFile: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:720)

I haven't looked into what causes this exactly, but I assume it's an incompatibility in the SSL/TLS protocol versions supported by the pipeline and the server. But that would be another issue...
The pipeline has no limit on the number of retries, and because this is not a temporary error, it has been looping since two weeks now. This is blocking a pipeline slot, though that isn't that bad in this case because it's luckily an ao-only pipeline.
But today, things got worse. The entire pipeline suddenly stalled (13:15 UTC), and with it all jobs on it (last activity of each job between 13:24 and 13:27 UTC). As it turned out, the SSL connection on that broken job got stuck (possibly related to the stall issues in wpull, pointing to a more general issue in Python's ssl module rather than a bug in wpull?). The jobs seem to have gotten stuck due to log shipping issues. Here's a GDB traceback on the pipeline process 11 hours after everything stopped responding.
Fortunately, I was able to get things back running (for now) by killing the stuck SSL connection with my kill-wpull-connections script (which isn't actually limited to wpull when using the -p option). However, this really shouldn't be possible.
There are two things here that I think need to be fixed:

Limit the number of retries on DownloadUrlFile. Fail the job if the download still didn't succeed.
Move the download to a separate thread or even a separate process so it can't block the entire pipeline and all its wpull processes.

There's a separate issue already for the infinite loop: #207


fail generating if config.source is './'

If config is the following json, documentation generating is fail.
{
  "source": "./",
  "destination": "./doc"
}

https://github.com/esdoc/esdoc/issues/52


packaging: add a VERSION file

this is helpful during specfile creation, and it's done like that
in Portus as well
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>

Note: When creating rpm versions, I've found that the best method for creating VERSION files is the following:

Before doing a release, make the version old_version+dev -- rpm recognises this as meaning "newer than old version".
After doing a release, make the version new_version for a single commit then new_version+dev.
When doing rc releases use new_version~rcN which is recognised by rpm as meaning "older than new_version".

And of course, new_version~rcN+dev is handled correctly.

Using "-" confuses rpm, better follow cyphar scheme. I am creating a PR


Remove unneeded values from EventStatus enumerated type to clarify the real-time intent of a WZDx feed

Background
This issue was "discovered" following discussion about how to represent "recurrent events" in a WZDx feed. Based on several rounds of discussion culminating in a focused meeting on recurrent events in late July 2021, the group came to the consensus that a "recurrent event", that is, a work zone that occurs in a similar fashion multiple days or on a fixed schedule, should be represented with a unique WZDx road event for each occurrence of work. The start and end date time of each road event should reflect the start/end of that occurrence of work.
In addition, recent discussion with many new members has shown that often individuals don't find WZDx's use case clearly apparent. It is another to do item to update the main project description to clarify the use of a WZDx feed is for making current or upcoming, real time (or as "real time" as possible), work zone information available to the public.
Proposal
Because of the above discussions, the EventStatus enumerated type was examined. We determined three of the values—pending, completed, and canceled—should likely be removed. The reasons are as follows:

completed has no utility because completed road events/work zones should not be included in a WZDx feed—a WZDx feed should include real-time information for the traveling public about current and planned road events
canceled does not have utility becuase if a work zone road event is known to be canceled and will no longer occur, it should not be included in a WZDx feed.
pending has a similar functionality to planned—they are describing the same concept but the distinction between both is not needed and the descriptions are unnecessarily precise.

EventStatus enumerated type after the above changes

Value
Description

planned
Indicates the road event is planned to occur in the future. All road events with a start date in the future should have this status. A road event with a date time range encompassing the current date and an event_status of planned indicates to the consumer that there is likely less accuracy in the road event data or that the work represented by the event hasn't begun yet.

active
Indicates that the road event is currently in place and work activity is occurring. It does not signify that there are workers present (see workers_present property on the RoadEvent for that information).

Makes sense

More thoughts for discussion on this issue after talking with Wisconsin DOT team about how to set EventStatus:

It is not clear when to set active and what the active status implies
Should active mean that work is confirmed to be occurring? If so should the value be named confirmed instead, and what it means to be confirmed is up to the producer (e.g. through a status_confirmation_method, like location_verify_method?

As for how event status should is set:

active/confirmed could be set automatically when the current datetime matches the road event's start_date (lower accuracy that work is actually occurring—this is how Iowa and MassDOT are doing it now)
active/confirmed could be set based on deployed ITS equipment (e.g. start/end marker or arrowboard, automatically)
active/confirmed could be set on from manual trigger from viewing a camera image or on-site personnel confirmation

In discussion of this issue with the Spec. Update co-chairs today, I think we may want to add to the active description:  "work activity is occurring or temporary traffic control is in place" for example
And it also may be worth adding a also maybe a caveat about confirmation, referencing the "start_date_verification" field as the source for whether the start date has been confirmed from the field. This allows the flexibility for agencies to set a work zone to active based on any of the criteria Jacob mentioned above

After further discussion by the WZDx Specification Update Subgroup Co-chairs, we arrived at a new proposal: remove the event_status property.
It is easier to determine if work within an event is actively occurring using other existing required properties of the event, specifically, start_date, end_date, start_date_accuracy and end_date_accuracy (event_status is currently optional). Since in all production WZDx feeds that we know of, event_status is set based on the scheduled dates, the event_status is not adding any value, just the potential for confusing scenarios.
Hard to determine scenarios that are currently allowed:
Below are examples of (partial) road event core details that are currently allowed where it is difficult for a producer to determine if the road event has work actively occurring, given the conflict between event_status, the current date, and the event's date properties.
Assume for both examples the current date is "2022-01-01 12:00:00" (Jan 1, 2022 at noon).
Example 1. road event is in the future but has a status of active.
{
  "event_status": "active",
  "start_date": "2022-01-15T08:00:00Z",
  "end_date": "2022-01-15T17:00:00Z",
  "start_date_accuracy": "estimated",
  "end_date_accuracy": "estimated"
}

Example 2. current date is within road event dates and dates are verified but the status is planned
{
  "event_status": "planned",
  "start_date": "2022-01-01T08:00:00Z",
  "end_date": "2022-01-01T17:00:00Z",
  "start_date_accuracy": "verified",
  "end_date_accuracy": "verified"
}

I think as part of this change that the TimeVerification values should be revisited and the descriptions enhanced to clarify that the TimeVerification can be used to determine if work is actively occurring.

Resolved in #294.


Test improvements

removed duplicate keys in MODEL_AND_MODULE_NAMES dict and added dino models to the test test suite

Codecov Report
Patch coverage has no change and project coverage change: +0.30% :tada:

Comparison is base (62a80b7) 74.24% compared to head (04f232b) 74.54%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   74.24%   74.54%   +0.30%
==========================================
  Files          28       28
  Lines        1324     1324
  Branches      194      194
==========================================
+ Hits          983      987       +4
+ Misses        280      278       -2
+ Partials       61       59       -2

Flag
Coverage Δ

unittests
74.54% <ø> (+0.30%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update appveyor.yml

:white_check_mark: Build ViaCEP 4.1.148 completed (commit https://github.com/guibranco/ViaCEP/commit/9ede754eb8 by @guibranco)


Green odd block in Sprites (Incorrect color)

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'Sprites'
Click on 'See Animations section'

Expected behavior
Add anim frame block is green
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Edge

@abchatra removed the block


Add child function support to Link

In my project, I'm using React Bootstrap for style/UI components. In my header, I use the NavItem component. But, that component is not aware of the Next.js router, which results in a server roundtrip for every click.
To fix this, I borrowed a concept from React Router and added support for child functions to Link. Here is how I use it in my project:
<Link href='/'>{ ({href, onClick}) =>
  <NavItem eventKey={1} href={href} onClick={onClick}>Index</NavItem>
}</Link>

This allows me to inject the onClick from my router-aware Link to my non-router-aware NavItem.
Hope it's helpful.

Thanks for the PR.
We wanted to make the built in Link API pretty simple as possible we can.
I think this is something you could do in the user land and release independently to NPM.
Anyway, I didn't understand the real problem behind here. Could you send us a sample repo with the original issue?

Thanks for the PR.
We wanted to make the built in Link API pretty simple as possible we can.
I think this is something you could do in the user land and release independently to NPM.
Anyway, I didn't understand the real problem behind here. Could you send us a sample repo with the original issue?

Have you also looked into the imperative routing API?

Have you also looked into the imperative routing API?

Here is the simplest sample repo I could cook up with the original issue.
I'm just trying to use React-Bootstrap's Navbar component, and it does not play nice with Next.js out of the box.
I had a similar problem with React Router, but was able to work around it by using a child function. That's why I thought it'd be handy to add to Next.js.
If there is a better way to achieve my simple goal, ignore my pull request.

@rauchg Thanks for pointing me to imperative routing API. This code works:
<NavItem eventKey={1} onClick={() => Router.push('/')}>Index</NavItem>
<NavItem eventKey={2} onClick={() => Router.push('/secret')}>Secret</NavItem>

Awesome @jkhoffman. We strive to keep parity between "manual" imperative APIs and their declarative JSX shorthand.

I think I found a solution that allows the use of react-bootstrap components with NextJS. I use <Link/> from next-routes but I believe this should also work with next-router.
First create a component for passing the props around <Link/>:
import React from 'react'
import { Link } from '../routes'

// passes props from react-strap around <Link> to <a> to prevent errors :)
const NextLink = ({ children, href, passHref, ...rest }) => (
  <Link href={ href } passHref={ passHref }><a {...rest}>{ children }</a></Link>
)

export default NextLink

Then in your navbar use <NavItem componentClass={ NextLink } href="/yourpath">


validate all inputs before save

    SubmittingMixing.reopen({
      submit: function(event) {
        log("submit");
        log(this);
        this.$("input").blur();//triggers validations
        this._super(event);
      },
      _eventHandler: function(type){
        //hack to send the right method to the controller (destroy is already used): 'this' is undefined in destroyHandler
        //https://github.com/sir-dunxalot/ember-easy-form-extensions/issues/18
        if (type==="destroy") {type="destroyModel";}
        this._super(type);
      },
    });

So, if I'm correct in understanding, there are two issues here:

destroy is now a method on Ember.Controller
this is undefined in the view's destroy handler

Sorry, yes I added ```_eventHandler`` here but this more a hack to solve https://github.com/sir-dunxalot/ember-easy-form-extensions/issues/18#issuecomment-95507098.
Here I just added this.$("input").blur(); to force the validation of input fields before submitting: if I dont do this my form would'nt save but I don't see any error on the form (which is a form for a new model instance). I thought it may be useful to include the blur() line by default in ember-easy-form-extensions

Ok, cool. I think there's a bigger issue here to do with the latest Ember release. This addon should show the error message on submit already (see source here). I think something has changed in the view layer or similar that's causing all these issue to combine.
I'll look into everything this weekend - keep sending the issues my way! Thanks.

I've recreated this issue in another app. I think your solution is nice and simple. Another option is to refactor the Submitting mixin to work on the {{form-wrapper}} component - that whole set up needs a rethink. I am planning on rewriting a lot within the next couple of weeks.

This is fixed with the major upgrade for Ember 1.11+ currently in prerelease. You can test the prerelease here. Please note the API for inputs has changed slightly from the original Easy Form syntax.

Feedback for the new setup and options will be very much appreciated.

This will be fixed by #37


User authentication

Coverage decreased (-7.2%) to 89.076% when pulling 8ae9e652249b3f317f2936ae5d98ea896f28bcb3 on dev into 29c1ef0f1f60748dc437c19bc0a8cb0ec46c9f30 on master.


Document the minimal number of validators required to run the chain

I find that the runtime would panic if there are too little number of validators on chain. It would be great if we can document what the number actually is.

Can you be more specific as to what the unhandled exception is?
Closing in favour of #1091 since this is a special case of that issue.


Batch 2: SEO H1 headings

FREELANCERS: Please do NOT merge as per @pebaum.

  Caution: Large pull request
This public repo applies limits on the number of files that can be merged in a single pull request (PR):

Warning Warning message and ability to unblock PR using the Merge large pull request* label - 30
Block Block message and PR is blocked - 100

This pull request will change 32 files, which exceeds the warning limit of 32.
Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.
The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.
To merge this pull request
If you have determined that the changes in this pull request are correct, add the Merge large pull request* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request*.

To reject this pull request
If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.
* You must have write or triage access to this repo to add labels.


🐞 - Tab Title Font is different when exporting

Which @codeimage/* package(s) are the source of the bug?
codeimage
Please provide a screenshot or a video to a minimal reproduction of the bug
No response
Description
Currently you use Inter as UI font for the app! It also applies on Tab Bar but when exporting the image or opening it in a new tab the font changes to the default OS font! which kinda look ugly especially on windows (Segoe UI). So, did you leave it as it is intentionally?? If yes, then change it to Inter cause Segoe UI spoils the mood.

Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[x] Windows
[ ] Linux
[ ] iOS
[ ] Android

Hi, thanks for reaching me 😀 No, this was not intentional then it will be fixed for the next update

Available with 1.5.0


*time.Time of struct is nil , but sqlite3 don't ignore when insert into db

`
create table city_model (
id integer primary key autoincrement,
city_id integer,
city_name char(255),
dt date,
create_time timestamp default current_timestamp
);
type CityModel struct {
Id int gorm:"column:id;type:int"
CityId int gorm:"column:city_id;type:int"
CityName string gorm:"column:city_name;type:varchar(255)",
Dt time.Time gorm:"colum:dt;type:date",
CreateTime *time.Time gorm:"column:create_time;type:timestamp" }
Sqlite3 was linked with Gorm, but create_Time was not assigned during the Insert, causing the database Create_Time to become nil.
i think if the field is ptr and value of the field is nil, create_time should be current_timestamp

SQLite itself does not work the way you want, partially because of how gorm apparently behaves.
If you explicitly tell SQLite to insert NULL then it will do so. It will not choose to insert the default value instead. If you want to use the default then you need to omit the column in question.
It seems gorm lacks a mechanism akin to omitempty, so it is always sending an explicit NULL to the INSERT.
Regardless, as per the gorm docs I think you are looking for the autoCreateTime field tag. https://gorm.io/docs/models.html#Fields-Tags


Update timeout for .github/workflows/changelog-validation.yml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/changelog-validation.yml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing in favor of https://github.com/Kong/kong/pull/12566.


[FEATURE REQUEST] Overriding default error page

Is your feature request related to a problem? Please describe.
If an error happens I see as a client the error. This should be only shown in the development environment
Describe the solution you'd like
Idk something like Internal Server Error like in Apache / Nginx
Describe alternatives you've considered
I am unsure that's possible to catch

Additional context

Hey @shyim. Yep, we did such override in the RR1 by separating RR errors and application errors. I agree with you. I will plan this update for the next sprint.

ref: https://github.com/spiral/roadrunner/discussions/689


node exporter: could not get power_supply class info

node exporter that's deployed by our prometheus-operator component with the default config seems to be looking for a non-existent file at /host/sys/class/power_supply.
From the node exporter logs:
monitoring/prometheus-operator-prometheus-node-exporter-g5pfv[node-exporter]: level=error ts=2020-10-21T11:47:26.991Z caller=collector.go:161 msg="collector failed" name=mdadm duration_seconds=5.7176e-05 err="error parsing mdstatus: error parsing mdstat /host/proc/mdstat: open /host/proc/mdstat: no such file or directory"
monitoring/prometheus-operator-prometheus-node-exporter-g5pfv[node-exporter]: level=error ts=2020-10-21T11:47:26.995Z caller=collector.go:161 msg="collector failed" name=powersupplyclass duration_seconds=3.8628e-05 err="could not get power_supply class info: error obtaining power_supply class info: failed to list power supplies at \"/host/sys/class/power_supply\": open /host/sys/class/power_supply: no such file or directory"

Setting --no-collector.powersupplyclass under prometheus-node-exporter.extraArgs in the component's values.yaml disables the relevant check:
prometheus-node-exporter:
  namespaceOverride: ""
  podLabels:
    ## Add the 'node-exporter' label to be used by serviceMonitor to match standard common usage in rules and grafana dashboard
s
    ##
    jobLabel: node-exporter
  extraArgs:
    - --collector.filesystem.ignored-mount-points=^/(dev|proc|sys|var/lib/docker/.+)($|/)
    - --collector.filesystem.ignored-fs-types=^(autofs|binfmt_misc|cgroup|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|mq
ueue|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|sysfs|tracefs)$
    - --no-collector.powersupplyclass

We should figure out if it makes sense to hardcode this change in values.yaml or if we want to expose it to the user. I'm leaning towards disabling this check since it won't work on Flatcar at the moment.

Maybe we should figure why it doesn't work on Flatcar?

Created an issue in Flatcar flatcar-linux/Flatcar/issues/215

As explained in https://github.com/kinvolk/lokomotive/pull/1111#issuecomment-714570980, updating node_exporter done in 85fd269059b27b762fb96965d1b45e35f0592b43 fixed it.


feat(align-requires): add align-requires rule

What
Add the align-requires rule which enforces that all variable declarations involving require or Factory.build. This is (loosely) based on the key-spacing rule which aligns colons in object declarations. This rule makes this valid:
let a   = require('a');
let ab  = require('ab');
let abc = require('abc');

let b  = Factory.build('b');
let bc = Factory.build('c');

let x = 1;
let xy = 2;
let xyz = 3;

And this invalid (only shown with requires, but also applied to Factory.builds):
let a  = require('a'); // error
let ab  = require('ab');
let abc = require('abc');

let b  = require('b'); // error

let c= require('c'); // error

let d =require('d'); // error

let e =  require('e'); // error

let f  = require('f'); // error
let g  = require('g'); // error

Details
The main premise of this rule is relying on a cache of expected locations of equal signs (expectedEqualsLocations). If there's ever a line that isn't in the cache, it goes through and calculates the expected position based on the "variable declaration block" (on lines 73-75). For example, as it parses each of the following lines, you can see what expectedEqualsLocations looks like after parsing the line:
1: // expectedEqualsLocations = []
2: let a = require('a'); // expectedEqualsLocations = [undefined, 8, 8, 8]
3: let ab = require('ab'); // expectedEqualsLocations = [undefined, 8, 8, 8]
4: let abc = require('abc'); // expectedEqualsLocations = [undefined, 8, 8, 8]
5:
6: let b = require('b'); // expectedEqualsLocations = [undefined, 8, 8, 8, undefined, 6, 6]
7: let c = require('c'); // expectedEqualsLocations = [undefined, 8, 8, 8, undefined, 6, 6]

So the "computation" of where the equal sign should be only happens once per block. I also didn't want to iterate of an array at any time to search for previously determined blocks, so that ruled out:
expectedEqualsLocations = [{
  start: 2,
  end: 4,
  location: 8
}, {
  start: 6,
  end: 7,
  location: 6
}]

Because this structure would require iteration and comparing with each cached block which would be slower than a direct array lookup.
Knowing this, the rest should be pretty straight forward, but if anything it's clear, just let me know!
@mgartner

Awesome. LGTM


Ionic 2 : No splashscreen/ Black splashscreen if Background geolocation is enabled

Your Environment

Plugin version: 2.2.5

Platform: Android (ios not tested)

OS version: win 10

Device manufacturer and model: One plus 3

Cordova version (cordova -v): 6.3.1

Cordova platform version (cordova platform ls):android 5.2.2

Plugin configuration options:

Ionic Framework Version: 2.0.0-rc.3-201611302233

Ionic CLI Version: 2.1.8

Ionic App Lib Version: 2.1.4

Ionic App Scripts Version: 0.0.45

                  {
                        desiredAccuracy: 0,
                        stationaryRadius: 5,
                        distanceFilter: 5,
                        debug: false,
                        stopOnTerminate: false,
                        locationProvider: 1,
                        interval: 30000,
                        fastestInterval: 5000,
                        activitiesInterval: 30000,
                        stopOnStillActivity:false
                };

Context

No splashscreen/ Black splashscreen if Background geolocation is enabled

## Expected Behavior

Splashcreen to appear on app start even if background service is on.

Actual Behavior

If background geolocation service is running  and app is terminated , on opening app black screen appears for few seconds  followed by white.
I have a toggle in app to switch the service on/off.
So , if i turn off the background service and termintae app then splashscreen appears correctly.
Steps to Reproduce

Start ionic 2 app
configure background plugin with ioni-native
enable background service
4.terminate app
start app !

Debug logs

app log when app starts with background geo on (Splashscreen does not work)

app log when app starts with no background geo (Splashscreen works)

Maybe this issue is not related to this plugin , but posting issue here because switching the background geo is directly affecting the splashscreen.
Thanks !

Just so you know, there nothing is logged in relation to background plugin on app start

Solved it by adding  <preference name="SplashShowOnlyFirstTime" value="false" /> .
But , I still dont understand why running service should affect splashscreen.


Ability for Deterministic Models to return Jacobians

James Parkins realized that Jacobians can speed up numerical integration of ODE's by 10x or more in certain cases [his case is modelling spatial organization as CRNs on a grid coupled with diffusion]. So, bioscrape should be able to compute the jacobian of the underlying CRN.
TODO:

Add a return derivative species function to each propensity.
Add a compute Jacobian function to the CSIM interface class. Think about how this can be done efficiently for sparse Jacobians.
Add options to deterministic simulation so methods requiring a Jacobian can be used via simulation calls if desired.

Moved to: https://github.com/biocircuits/bioscrape/issues/10


Set discriminator key at construction time instead of after save

Kind of a minor issue, but there are times when it would be nice if the discriminator key was available immediately after the model was constructed, rather than waiting until after a Save has been performed.

+1  This might solve an issue that I have when constructing documents and working with them before they actually get saved.

I will check it, but it may be hard to fix, it will take some time.


Github-bot marks people are not in the organization

Occasionally we receive an email that says:

Hello,
The following people are not collaborators in the repository wildfly/wildfly, however they were requested to review Pull Request number #number
#name

Last time it was yersan and rhusar for PR #18178

@xjusko


Add ability to serialise DNSRecord as json

It would be useful to be able to support the Google JSON API for DoH but would be quite a bit of work (would have to update the parse/pack methods for all record types). I'd be happy to accept a pull-request (including tests) but realistically am unlikely to have the time to do this.


ci/release: Fix changelog sync

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@phlax needs conflict resolve


Update to the code for Microsoft Monitoring Agent for Azure Operation…

…al Insights
If you don't use the protectedSettings for the Workspace Key it will be get exposed to the deployment logs etc. You don't want that!
Example: http://www.danielstechblog.de/azure-azure-stack-iaas-vm-arm-mma-operational-insights-template-integration/

Hi @neumanndaniel, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@neumanndaniel Thank you for this contribution.  I'll have the author review.
@KundanaP  Would you please review this contribution and let me know if I should merge it?  Thank you.

@deneha @KundanaP It is a bit disappointing to see that nothing has happened the last 18 days on that topic.

@neumanndaniel @deneha  -  I'm very sorry that I missed this notification. The article looks great! Thanks for writing. There seems to be a minor typo in this sentence " I assume that you have a ready to use IaaS VM ARM template". Rest looks great.

@neumanndaniel If you can make that one change @KundanaP suggested and fix the merge conflict on this request, I'll get this merged for you right away.

@deneha @KundanaP My article was only for explaining why I have done the code change for the setting workspaceKey. It is enough for me when you merge my code change.

Ok. I just checked the documentation website. The code change has been done already.

And you are using the wrong settings:
It is "workspaceId" instead of "workspace_name".
It is "workspaceKey" instead of "workspace_key".

@KundanaP Additional feedback here - please check

Thanks for pointing out that the field names are incorrect. You are totally right - it should be workspaceId and workspaceKey.
BTW, thanks for writing your blog post - I know it helped to resolve at least one customer issue.


hugo: 0.111.1 -> 0.111.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gohugoio/hugo/releases.
meta.description for hugo is: A fast and modern static website engine
meta.homepage for hugo is: https://gohugo.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.111.2 in filename of file in /nix/store/8ii8c5m9bdi68mkwswvjalsjhkfa2wva-hugo-0.111.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
hugo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8ii8c5m9bdi68mkwswvjalsjhkfa2wva-hugo-0.111.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hugo https://github.com/r-ryantm/nixpkgs/archive/ae3b83c809f5ef9140c597b3d18896c02a5dcd25.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8ii8c5m9bdi68mkwswvjalsjhkfa2wva-hugo-0.111.2
ls -la /nix/store/8ii8c5m9bdi68mkwswvjalsjhkfa2wva-hugo-0.111.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

hugo

Maintainer pings
cc @schneefux @Br1ght0ne @Frostman for testing.

nix-shell -p nixpkgs-review --run "nixpkgs-review pr 219978"
...
1 package updated:
hugo (0.111.1 → 0.111.2)
...
1 package built:
hugo

./results/hugo/bin/hugo -h
hugo is the main command, used to build your Hugo site.


Create table from the resulting metadata from a SQL query

This feature was in version 2.7.4 but has been removed from version 2.8.  It allows you to create a table from the metadata that results from an SQL query.

Fixed in 2.9.0.


Add API Key to PHP Translate Quick Start guide

My code snippet didn't work first time, so I added these lines and my code snippet worked

Did you try setting the environment variable APPLICATION_DEFAULT_CREDENTIALS to a file containing your service account credentials? I've added this to the README in #849 which should fix your issue.


Hugo version

hi.. i was converting my big wordpress blog to Jekyll+Minimal-mistakes... but too slow (with 500 posts it takes too much even with -incremental)
then tried Hugo.. and how damn fast it is. ok i'll lose the GitHub pages, but Netfly integration is easy and also free for basic sites.
so since i really like this jekyll theme, and your support for it is awesome, and there aren't really as good themes for Hugo... i was thinking about a Hugo version of Minimal Mistakes theme!
hasn't anybody already started it? what do you think?
if we release it with the same MIT license there shouldn't be any problem, right?

Feel free to fork and port over to Hugo. A couple of my other theme's I believe have been ported.
You might want to search GitHub as I've gotten a couple of inquires like yours. It's possible others have already started converting MM to Hugo.

https://github.com/mikeymop/minimal-mistakes-hugo

https://github.com/mikeymop/minimal-mistakes-hugo

There is no any documentation about how to use it, I completely have not idea how to make it work.

@jcyrss You’ll want to ask how to use the Hugo theme on the repo linked above. I have tie to it nor do I use Hugo myself.
This repo is for the Jekyll version only.

In case someone comes by this issue: the repository linked seems like the start of a project to make a hugo version; it's in now way finished or usable (which, quite honestly, is a shame....). For now for those wanting to use minimal mistakes on Hugo, you're out of luck!


Backport Python features to v1.0.x

Are we doing that whole squash-everything dealio yet? Or can I use the argument that these are cherry-picks and a single update commit so we probably don't want to do that?

cc @thunderboltsid

Forgot to update tests.json. Will update 'n squash.

... and amend the author...


After 7 days the app is installed i get the rating popup everytime

After 7 days the app is installed i get the rating popup everytime i switch page/open the app
This is my init Code
RateMyApp(
        minDays: 7,
        minLaunches: 10,
        remindDays: 7,
        remindLaunches: 10,
      ));

This is the way i open the popup:
_rateMyApp.init().then((_) {
      if (_rateMyApp.shouldOpenDialog) {
        _rateMyApp.showStarRateDialog(
          context,
          title: ToTLocalizations.of(context).rateAppTitle,
          message: ToTLocalizations.of(context).rateAppContent,
          ignoreIOS: false,
          starRatingOptions: StarRatingOptions(),
          onRatingChanged: (stars) {
            return [
              RaisedButton(
                padding: EdgeInsets.all(10.0),
...

The expected behavior is that if i click "later" the "baseLaunchDate" should be set to today, and the popup opened again in 7 (remind days) days
I'm running it on IOS 12.4 simulator
The native popup is opened, but as far i can understand there is no management in the plugin for the native form callback up to the dart code and shared preferences.

Thanks for the answer. Something is not clear to me tho.
My use case is:
IOs: native dialog
Android: startRatingDialog
I could use the Platform object, and in case of android do a call to you starRatingDialog plugin and that is great.
But then how could i handle the native rating dialog in ios, using the same configuration (minDays, minLaunces ecc...)? Would be great if your plugin interfaced the callbacks of that popup and integrate it into the same logic (maybe it does but i'm missing it).
Thanks!
David

showStarRateDialog can't integrate the same logic because it's not the plugin who are creating user buttons. It's you (based on the rating). But what you can do in showStarRateDialog is to return those buttons (in onRatingChanged of course) :
[
  FlatButton(
    child: Text('RATE'),
    onPressed: () {
      _rateMyApp.doNotOpenAgain = true;
      _rateMyApp.save().then((v) {
        Navigator.pop(context);
        // Call _rateMyApp.launchStore(); or whatever you want.
      });
    },
  ),
  FlatButton(
    child: Text('LATER'),
    onPressed: () {
      _rateMyApp.baseLaunchDate = _rateMyApp.baseLaunchDate.add(Duration(
        days: _rateMyApp.remindDays,
      ));
      _rateMyApp.launches -= _rateMyApp.remindLaunches;
      _rateMyApp.save().then((v) => Navigator.pop(context));
    },
  ),
  FlatButton(
    child: Text('NO'),
    onPressed: () {
      _rateMyApp.doNotOpenAgain = true;
      _rateMyApp.save().then((v) => Navigator.pop(context));
    },
  ),
]

Yeah the part managed by flutter and dart is clear, but i wanted to keep the native dialog for IOs (as far as i know there is no native for android) and be able to managed it's result thought a method channel future, containing the result of the native popup (true for rate, and false of "later" or click outside), Don't even know if that's possible, but it would create a seamless integration covering all cases with a single implementation.
This is the part of code that opens the native popup, but there is no await for the result of the call, maybe it's possible/easy to add it?
if (!ignoreIOS && Platform.isIOS && await _CHANNEL.invokeMethod('canRequestReview')) {
      return _CHANNEL.invokeMethod('requestReview');
    }

This is the oBjc code
if ([call.method isEqualToString:@"requestReview"]) {
    [SKStoreReviewController requestReview];
    result(nil);
  }
'''

Nevermind, i just saw athat SKStoreReviewController.requestReview() return null, so there is no way to intercept it :/

Yeah the part managed by flutter and dart is clear, but i wanted to keep the native dialog for IOs (as far as i know there is no native for android) and be able to managed it's result thought a method channel future, containing the result of the native popup (true for rate, and false of "later" or click outside), Don't even know if that's possible, but it would create a seamless integration covering all cases with a single implementation.

Ow okay ! But as you said above, it's not possible because of how Apple designed their dialog.

I'll probably go for full plugin management then !
Thanks for your help!!


Python 3.11 compatibility/availability?

Just checked other branches, and it seems the other branches are not for dev.
Just wondering what the latest would be on updates.
Also, wanted to put this interesting + recent tidypandas to attention. I thought you might like their solution to the col('NAME') situation. https://www.youtube.com/watch?v=AMJEnkA0YrE though I'm assuming because it's Python dictionary, perhaps it would suffer on performance?

2nd this

Long update times for tidypolars make it difficult for me to rely on polars.

Long update times for tidypolars make it difficult for me to rely on polars.

polars has been implementing changes (and breaking changes) faster than I can keep up with. Changing reverse to descending in .sort() was one of them. It's good that polars is constantly improving, but the API instability makes it a bit hard to build a package that depends on it unfortunately.
There are probably a lot more fixes necessary to get tidypolars back to a good state. I'll try to get to them at some point, but between a newborn and a new job I'm bit behind on keeping this package up to date. I've only had enough time lately to keep updates to R's tidytable and dtplyr.

Hey @markfairbanks, double congrats! :)
Thanks for keeping us in the loop. No worries about it for now.

I understand, that makes sense. Congrats on the kid! Hopefully, polars matures soon and the changes start coming slower. You've done a great job on your package.

From: Mark Fairbanks @.>
Sent: Sunday, July 2, 2023 2:18:06 PM
To: markfairbanks/tidypolars @.>
Cc: hmhensen @.>; Comment @.>
Subject: Re: [markfairbanks/tidypolars] Python 3.11 compatibility/availability? (Issue #230)
Long update times for tidypolars make it difficult for me to rely on polars.
polars has been implementing changes (and breaking changes) faster than I can keep up with. Changing reverse to descending in .sort() was one of them. It's good that polars is constantly improving, but the API instability makes it a bit hard to build a package that depends on it unfortunately.
There are probably a lot more fixes necessary to get tidypolars back to a good state. I'll try to get to them at some point, but between a newborn and a new job I'm bit behind on keeping this package up to date. I've only had enough time lately to keep updates to R's tidytable and dtplyr.
—
Reply to this email directly, view it on GitHubhttps://github.com/markfairbanks/tidypolars/issues/230#issuecomment-1616821235, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG2KZ7LMK3LBWWO47NW7433XOHQQ5ANCNFSM6AAAAAAYJKNS6A.
You are receiving this because you commented.Message ID: @.***>

:tada: :tada:


Readme.md

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: RagniGarg97
To complete the pull request process, please assign mkumatag after the PR has been reviewed.
You can assign the PR to them by writing /assign @mkumatag in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: RagniGarg97
To complete the pull request process, please assign mkumatag after the PR has been reviewed.
You can assign the PR to them by writing /assign @mkumatag in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Not here! you need to make changes to the repo - https://github.com/ppc64le-cloud/build-bot

Not here! you need to make changes to the repo - https://github.com/ppc64le-cloud/build-bot


[WIP] [v0.13.x] Allow resource configuration for APIServer

Changes

Allows resource configuration for pod deployment.
Allows configuration for targetRamMb to limit size of watch cache.

Codecov Report

Merging #1745 into v0.13.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           v0.13.x    #1745   +/-   ##
========================================
  Coverage    25.28%   25.28%
========================================
  Files           98       98
  Lines         5087     5087
========================================
  Hits          1286     1286
  Misses        3659     3659
  Partials       142      142

Continue to review full report at Codecov.

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

/lgtm


feat: add CardVerificationCodeElement types

Description

Add types for new CardVerificationCodeElement

Testing required outside of automated testing?

[X] Not Applicable

Screenshots (if appropriate):

[X] Not Applicable

Rollback / Rollforward Procedure

[X] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.30.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Link to documentation broken

Hi,
I've been testing out this tool and ran a few playbooks after getting the CSV.
I noticed that the documentation link leads nowhere. Are there any other features or things that are important to know with this tool that's not mentioned on GitHub?
Link:

Hi @Lodewyk-Git apologies for the late reply. You are correct, the documentation has not yet been developed! I've been drowning in day time work and haven't had time to do it. However, it is coming soon so stay tuned.
I wouldn't say there are "hidden" things in the tool, if you know how to use the Powershell switches for the main two modules.


bugs when use attach database

when I attach another database file, it usually wrong when operating tables in the attach database.
For example, I use this command to attach a db:
attach database 'database/test4.db' as 'test4'
Then query from tables:
select * from test4.app_users
I restart my program a lot times to test. Sometimes I got error: no such table: test4.app_user. But sometimes it works!
I wonder if there some bugs with this sqlite3 driver about attach database.

Can you provide a test which will reproduce this.

I have same problem

Can you provide a func main() with a test to reproduce so we can run some tests as well to research this. Thanks I'm advance.

I fixed it with the following hook:
sql.Register("sqlite3_hooked",
			&sqlite3.SQLiteDriver{
				ConnectHook: func(conn *sqlite3.SQLiteConn) error {
					conn.Exec("ATTACH DATABASE '"+db2+"' AS 'db2';", nil)
					return nil
				},
			})
db1, err := sql.Open("sqlite3_hooked", db1Path+"?mode=memory&cache=shared&mode=rwc")

I guess this issue is related to above.
If sql.Rows is not closed before next query then driver returns no such table on next query.
Issue exists only for in-memory storage, same test for file backed db runs fine.
go-sqlite3:  3.23.1 3023001 2018-04-10 17:39:29
go        :  go1.10.2 linux/amd64

package model

import (
	"database/sql"
	sq3 "github.com/mattn/go-sqlite3"
	"testing"
)

func TestIt(t *testing.T) {
	t.Log(sq3.Version())

	db, err := sql.Open("sqlite3", ":memory:")
	if err != nil {
		t.Fatal(err)
	}
	defer db.Close()
	_, err = db.Exec(`
		CREATE TABLE foo (id integer PRIMARY KEY, name text NOT NULL);
		`)
	if err != nil {
		t.Fatal(err)
	}
	if _, err = db.Exec("INSERT INTO foo (name) VALUES (?)", "bar"); err != nil {
		t.Fatal(err)
	}
	rows, err := db.Query("SELECT * FROM foo LIMIT 1")
	if err != nil {
		t.Fatal(err)
	}
	if rows.Next() {
		var id int64
		var name string
		rows.Scan(&id, &name)
		t.Log(id, name)
	}

	// this one throws "no such table: foo"
	// problem can be solved by previously calling
	// > rows.Close()
	// or indirectly
	// > for rows.Next(){...}
	rows, err = db.Query("SELECT * FROM foo")
	if err != nil {
		t.Fatal(err)
	}
}

@kac- Is this something we should investigate or should this be filled under programmers error ?

@GJRTimmer I think that this inconsistency in behaviour for memory and file storage can be misleading. It took me more than hour to catch it in my simple code (I was investigating custom ~DAO most of time and searched for some typo). Example codes have defer rows.Close() in most places "saying" "you should close it somewhere" and it's not true because you should close it immediately. The best would be to return an error explicitly pointing to programmers fault, if it's not too obstructive for drivers code/performance ofc.
I have to check how other sql drivers handle this case.

@GJRTimmer looking at it from a perspective I think it should be filled under programmers fault.
Issue is covered under https://github.com/mattn/go-sqlite3#faq but beside Why is it racy if I use a sql.Open("sqlite3", ":memory:") database? I think it would be really nice to have something like Why I'm getting "no such table" error?.

@kac- will update README

@kac- THANK YOU SO MUCH! I've found a part of code where I had forgotten to do rows.Close(), fixed that and now it works with no issues!

Another solution, at least for my use case, appears to be:
db.SetMaxOpenConns(1)


QueryParamDecoder instance for http4s

FUUIDVar from fuuid-http4s provides support for extracting path params, but there's no support for extracting query params.
It would essentially be something like
implicit val fuuidQueryParamDecoder: QueryParamDecoder[FUUID] =
  QueryParamDecoder.fromUnsafeCast(v => FUUID.fromString(v.value).right.get)("FUUID")

and use
object UserIdQueryParamMatcher extends QueryParamDecoderMatcher[FUUID]("userId")

val routes: HttpRoutes[F] = HttpRoutes.of[F]({
  case req @ GET -> Root / "get" :? UserIdQueryParamMatcher(userId) =>
    for {
      result <- controller.get(userId)
      res <- result.map(Ok(_)).getOrElse(NotFound())
    } yield res
})

@ChristopherDavenport if you agree this is useful, I can send a PR.

Works for me! 😄


[Android N] Notification Enhancements

Direct reply and bundled notifications http://developer.android.com/preview/features/notification-updates.html


Fix build with latest flatbuffers

See https://github.com/tensorflow/tensorflow/pull/27504
Motivation of this pull-request is to be possible to make tensorflow-lite with newest flatbuffers and fp16.

Can one of the admins verify this patch?

@mattn Could you please check reviewer comments and keep us posted. Thanks!

They generally pin to stable releases only,

It mean farmhash is too?

Can you give some description of why the newest farmhash commit is better than the old one? What does it bring for the PR

The description of this pull-request is to be possible to build tensorflow lite with latest flatbuffers. (hopefuly, want to build on Windows) Recently, flatbuffers seems to be included many improvement for performance. So I want to use tensorflow lite with latest flatbuffers.
One another my motivation is that we will be able to build tensorflow lite using mingw compiler without any patches. But the version of farmhash that is used in tensorflow is bits older than I want.
https://github.com/google/farmhash/commit/6193375f121f1e2288f0d9282c4d9be1547e2c0f

This commit of farmhash make be possible to build tensorflow lite with mingw compiler.

Thank you, now it's clearer.
It will take some time before we can upgrade the flatbuffers dependency, but I'll come back to this PR once that's done. Sorry for the delay

@mihaimaruseac Any update on this PR, please.

I think we need to wait for 2 other internal changes to land first but they keep getting delayed.
In the meanwhile, we need to fix the conflicts

Any update on this PR?
I'm running into exactly the same issue where flatbuffers fetch fails.
`
Please specify the location of python. [Default is C:\Python37\python.exe]:
Found possible Python library paths:
C:\Python37\lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Python37\lib\site-packages]
Do you wish to build TensorFlow with XLA JIT support? [y/N]: n
No XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]: n
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: n
No CUDA support will be enabled for TensorFlow.
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:
Would you like to override eigen strong inline for some C++ compilation to reduce the compilation time? [Y/n]: y
Eigen strong inline overridden.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
--config=mkl            # Build with MKL support.
--config=monolithic     # Config for mostly static monolithic build.
--config=ngraph         # Build with Intel nGraph support.
--config=numa           # Build with NUMA support.
--config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.
--config=v2             # Build TensorFlow 2.x instead of 1.x.
Preconfigured Bazel build configs to DISABLE default on features:
--config=noaws          # Disable AWS S3 filesystem support.
--config=nogcp          # Disable GCP support.
--config=nohdfs         # Disable HDFS support.
--config=nonccl         # Disable NVIDIA NCCL support.
Configuration finished
PS C:\Users\alisy\OneDrive\Documents\Tensorflow\tensorflow> bazel build -c opt --cxxopt=--std=c++11 --config=android_arm //tensorflow/lite/c:tensorflowlite_c
Starting local Bazel server and connecting to it...
INFO: Writing tracer profile to 'C:/users/alisy/_bazel_alisy/wlnshcl6/command.profile.gz'
INFO: Options provided by the client:
Inherited 'common' options: --isatty=1 --terminal_columns=135
INFO: Options provided by the client:
'build' options: --python_path=C:/Python37/python.exe
INFO: Reading rc options for 'build' from c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc:
'build' options: --apple_platform_type=macos --define framework_shared_object=true --define open_source_build=true --java_toolchain=//third_party/toolchains/java:tf_java_toolchain --host_java_toolchain=//third_party/toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --config=v2
INFO: Reading rc options for 'build' from c:\users\alisy\onedrive\documents\tensorflow\tensorflow.tf_configure.bazelrc:
'build' options: --action_env PYTHON_BIN_PATH=C:/Python37/python.exe --action_env PYTHON_LIB_PATH=C:/Python37/lib/site-packages --python_path=C:/Python37/python.exe --define=override_eigen_strong_inline=true --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:v2 in file c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:android_arm in file c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc: --config=android --cpu=armeabi-v7a --fat_apk_cpu=armeabi-v7a
INFO: Found applicable config definition build:android in file c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc: --crosstool_top=//external:android/crosstool --host_crosstool_top=@bazel_tools//tools/cpp:toolchain
INFO: Found applicable config definition build:windows in file c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc: --copt=/w --copt=/D_USE_MATH_DEFINES --cxxopt=/std:c++14 --host_cxxopt=/std:c++14 --config=monolithic --copt=-DWIN32_LEAN_AND_MEAN --host_copt=-DWIN32_LEAN_AND_MEAN --copt=-DNOGDI --host_copt=-DNOGDI --linkopt=/DEBUG --host_linkopt=/DEBUG --linkopt=/OPT:REF --host_linkopt=/OPT:REF --linkopt=/OPT:ICF --host_linkopt=/OPT:ICF --experimental_strict_action_env=true --incompatible_windows_native_test_wrapper --verbose_failures --distinct_host_configuration=false
INFO: Found applicable config definition build:monolithic in file c:\users\alisy\onedrive\documents\tensorflow\tensorflow.bazelrc: --define framework_shared_object=false
INFO: Call stack for the definition of repository 'flatbuffers' which is a third_party_http_archive (rule definition at C:/users/alisy/onedrive/documents/tensorflow/tensorflow/third_party/repo.bzl:206:28):

C:/users/alisy/onedrive/documents/tensorflow/tensorflow/third_party/flatbuffers/workspace.bzl:6:5
C:/users/alisy/onedrive/documents/tensorflow/tensorflow/tensorflow/workspace.bzl:49:5
C:/users/alisy/onedrive/documents/tensorflow/tensorflow/tensorflow/workspace.bzl:92:5
C:/users/alisy/onedrive/documents/tensorflow/tensorflow/WORKSPACE:19:1
INFO: Repository 'flatbuffers' used the following cache hits instead of downloading the corresponding file.

Hash '3f4a286642094f45b1b77228656fbd7ea123964f19502f9ecfd29933fd23a50b' for https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/flatbuffers/archive/v1.11.0.tar.gz
If the definition of 'flatbuffers' was updated, verify that the hashes were also updated.
ERROR: An error occurred during the fetch of repository 'flatbuffers':
java.io.IOException: Could not create symlink from C:/users/alisy/onedrive/documents/tensorflow/tensorflow/third_party/flatbuffers/build_defs.bzl to C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl: C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl (File exists)
ERROR: Skipping '//tensorflow/lite/c:tensorflowlite_c': no such package '@flatbuffers//': java.io.IOException: Could not create symlink from C:/users/alisy/onedrive/documents/tensorflow/tensorflow/third_party/flatbuffers/build_defs.bzl to C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl: C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl (File exists)
WARNING: Target pattern parsing failed.
ERROR: no such package '@flatbuffers//': java.io.IOException: Could not create symlink from C:/users/alisy/onedrive/documents/tensorflow/tensorflow/third_party/flatbuffers/build_defs.bzl to C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl: C:/users/alisy/_bazel_alisy/wlnshcl6/external/flatbuffers/build_defs.bzl (File exists)
INFO: Elapsed time: 9.720s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
currently loading: tensorflow/lite/c `


Remove redundant support query

The documentation about .sticky-top is incorrect & the I doubt the @support query is really necessary.

IE11 and IE10 will render position: sticky as position: relative.

Nope, it won't. It 'll render as it's initial position value, probably static.

As such, we wrap the styles in a @supports query, limiting the stickiness to only browsers that can render it properly.

If it's not supported, there's not really any difference in using the @support query or not, unless the position is explicitly set to anything else than static. IMO we can remove the support query, it's feels a bit inconsistent to only check for it on that place.

I specifically remember running into multiple issues in my Windows installs and this was the only solution to those within our docs layout. Can you put together some test cases, or at least explore how this affects the docs (bare in mind, docs might have custom CSS, can’t recall)?

And use BrowseStack to test this on real browsers :)

I tested on IE11.

It 'll render as it's initial position value, probably static.

Right, but the .navbar sets position: relative.
I'm afraid we can't rule out the possibility that the position: relative may cause some unintended problems by top and z-index. but, I could not find the problem in the scope of the documents and the examples.

Closing per @ysds' comment


frontend: Add init and ephemeral containers logs

Extend Pod Details View with Init Container Log/Exec Selection
Fixes issue #1450
Description
This PR enhances the Pod Details View by allowing logs and exec commands to be selected by container type. Users can now choose between standard containers, init containers, and ephemeral containers (if present) for more granular access to logs and exec functionality.
Changes

[x] Implemented log/exec selection for standard containers in Pod Details.
[x] Added log/exec selection capability for init containers.
[x] Enabled log/exec selection for ephemeral containers when they exist.

Verification

Manual testing was conducted to ensure that logs and exec commands can be selected and are functioning for each container type within the Pod Details View.

Images

Looks good for init container logs!


Unsupported Transport for gstreamer rtspclientsink

Which version are you using?
v0.16.0
Which operating system are you using?

OS

[x] Linux
[ ] Windows
[ ] macOS

Architecture

[ ] amd64
[ ] arm64
[ ] arm7
[x] arm6 (running on an NVIDIA Jetson Xavier)

Describe the issue
I want to use gstreamer to publish an rtsp stream through a cv2 videoWriter (python). My gstreamer pipeline and code look as follows:
gst_out = "appsrc ! video/x-raw, width=(int)1280, height=(int)720, format=BGR ! videoconvert ! x264enc !" \
             "rtspclientsink location=rtsp://localhost:8554/mystream "
out = cv2.VideoWriter(gst_out, cv2.CAP_GSTREAMER, 0, float(fps), (int(w), int(h)))
while True:
    frame = gen_frame()
    out.write(frame)

The RTSPSimple server registers the pipeline, but crashes instantly. The rtsp server logs are as follows:
2021/05/19 15:54:29 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [c->s] OPTIONS rtsp://localhost:8554/mystream RTSP/1.0
CSeq: 1
Date: Wed, 19 May 2021 15:54:29 GMT
User-Agent: GStreamer/1.14.5

2021/05/19 15:54:29 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [s->c] RTSP/1.0 200 OK
CSeq: 1
Public: DESCRIBE, ANNOUNCE, SETUP, PLAY, RECORD, PAUSE, GET_PARAMETER, TEARDOWN
Server: gortsplib

2021/05/19 15:54:33 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [c->s] ANNOUNCE rtsp://localhost:8554/mystream RTSP/1.0
CSeq: 2
Content-Length: 394
Content-Type: application/sdp
Date: Wed, 19 May 2021 15:54:33 GMT
User-Agent: GStreamer/1.14.5

v=0
o=-<PHONE_NUMBER> 1 IN IP4 <IP_ADDRESS>
s=Session streamed with GStreamer
i=rtspclientsink
t=0 0
a=tool:GStreamer
m=video 0 RTP/AVP 96
c=IN IP4 <IP_ADDRESS>
b=AS:2097
a=rtpmap:96 H264/90000
a=framerate:15
a=fmtp:96 packetization-mode=1;profile-level-id=f4001f;sprop-parameter-sets=Z/QAH5GbKAoAt2AtQEBAUAAAAwAQAAADAejxgxlg,aOvsRIA=
a=control:stream=0
a=ts-refclk:local
a=mediaclk:sender

2021/05/19 15:54:33 I [0/0] [RTSP] [session<PHONE_NUMBER>] opened by <IP_ADDRESS>:53898
2021/05/19 15:54:33 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [s->c] RTSP/1.0 200 OK
CSeq: 2
Server: gortsplib
Session:<PHONE_NUMBER>

2021/05/19 15:54:33 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [c->s] SETUP rtsp://localhost:8554/mystream/stream=0 RTSP/1.0
CSeq: 3
Date: Wed, 19 May 2021 15:54:33 GMT
Session:<PHONE_NUMBER>
Transport: RTP/AVP/UDP;unicast;client_port=42382-42383;mode=RECORD
User-Agent: GStreamer/1.14.5

2021/05/19 15:54:33 D [0/0] [RTSP] [conn <IP_ADDRESS>:53898] [s->c] RTSP/1.0 461 Unsupported Transport
CSeq: 3
Server: gortsplib

2021/05/19 15:54:33 I [0/0] [RTSP] [session<PHONE_NUMBER>] closed
2021/05/19 15:54:33 I [0/0] [RTSP] [conn <IP_ADDRESS>:53898] closed

Looks like something is wrong with the transport mode, but I can't really figure out what.
Am I doing something wrong or is this something going wrong on the server side? Might this be related to: https://github.com/aler9/rtsp-simple-server/issues/40#issuecomment-660101391 ?

Hello, are you sure that the UDP protocol is enabled? what's the configuration of the server?

No, I want to use TCP in my case.
My run command is
docker run --rm -it -e RTSP_PROTOCOLS=tcp -e RTSP_LOGLEVEL=debug -p 8554:8554 -p 1935:1935 aler9/rtsp-simple-server


Can't type into an HtmlTimeInput?

I'm using a sendKeys() call in Selenium to type a time into an HTML Time input, but HtmlTypeInput doesn't override doType(), so the incoming keystrokes are ignored. (Additionally, HtmlTypeInput is missing from a few blocks of instanceof checks that decide whether to fire an input JS event, but first things first.)

Have done a look at this and some refactoring already.
But this requires a major update of the current HtmlInput implementation. Will try to make this step by step during the next days and inform about the progress.

No worries, thanks for the update!

Please check with version 3.0.0

Works great, thank you!


Jquery missing on some page

Bug description
Jquery is missing on some pages, like "/add_findings". Notifications dropdown gives error: "Cannot read property 'trim' of undefined"
Steps to reproduce
Steps to reproduce the behavior:

Go to '"/add_findings/{number}
Click on notifications dropdown.
Notification dropdown won't load.

Environment information

Operating System: [Ubuntu 18.04]
DefectDojo version: Dev

I wanted to fix this issue. but I can't seem to repeat it from my end.
I can't find any endpoint called /add_findings/{number} on my instance.
can you point out any other page you have this issue.

@propersam  https://github.com/DefectDojo/django-DefectDojo/blob/e5a884296b3fefa48a48602b58f9884b762b2f6f/dojo/templates/dojo/add_findings.html
Page doesn't have <script type="application/javascript" src="{% static "chosen/chosen.jquery.min.js" %}"> like https://github.com/DefectDojo/django-DefectDojo/blob/e5a884296b3fefa48a48602b58f9884b762b2f6f/dojo/templates/dojo/add_related.html

Oh.
I will like to understand clearly. Are you asking that all jquery include files be added equally to every page.

Yes, some pages are missing the Jquery script and throw errors because of that.

alright, will do just that..

@aaronweaver what do u say about this.
Are some of the jquery files ignored for special reasons ?

with the upgrade to python3 and other upgraded packages.. I think this should now be stable...
any jquery not added on a page now ..should be because it's not needed on that page.
@Maffooch what do you say?

@propersam I don't know very much about jQuery. I can guess that upgrading to python3 and other packages has no relation to jQuery. I would say do whatever it takes to resolve the bug. In this case, make sure 'Notifications dropdown gives error: "Cannot read property 'trim' of undefined"' does not happen.

It was probably not on every template, no reason it's can't be on every page.

my problem now is  I cant seem to repeat the error y'all talking about but on my local instance and heroku instance.
I should have fixed this a long time ago...
Is there any clear nd direct steps to trigger this error on screen while clicking through the app??


Add early vote sites

Pivotal Card 1
Pivotal Card 2
Early Vote Sites page now loads as well as individual error pages.

LG. TM.


Update template & generate new one for devhub

Working on https://github.com/substrate-developer-hub/substrate-docs/issues/132
I wanted to make sure we have the template updated for the launch of the new docs :grin:  https://github.com/substrate-developer-hub/frontier-node-template/issues/10
I see that the node is floating on some master commit of substrate... and I know that is what is required for now. Is there any changes that should be made before I generate a new template from the master branch here? Is there anything pending or a different branch I should pull from @sorpaas ?

Related FYI. I'm going to use the monthly-2021-10 release for my workshop at Sub0.
My plan is this:

Up date frontier to the tip of Substrate master
Prepare my material for a dry run of the Workshop this Friday
When the release is tagged, Make a PR to this repo that updates frontier to use the commit that got tagged (but don't point directly to the tag)
Make my own branch that points directly to the tagged dependency and use it as the starting point for the workshop.

I think this will play nicely with your plans @NukeManDan right?

Is there any changes that should be made before I generate a new template from the master branch here? Is there anything pending or a different branch I should pull from?

I'm not aware any changes for Frontier master. It should be the same.
There will indeed be changes if you try to update to Substrate master now. This is notably due to the introduction of scale-info -- we have some dependent crates that do not support it yet. But from what I can see we control all those crates, so this is just going to take a little effort.

I've got a good start on this today. I have PRs open in parity-common, ethereum, evm, and frontier repos. The frontier one is https://github.com/paritytech/frontier/pull/485 I could use a little help on it at this point.

Tooling has been launched for the node template and parachain template now, https://github.com/substrate-developer-hub/substrate-node-template/pull/366
Perhaps Mal can get this going for frontier as well?


Adding LWP and IWP to default_spec.yml

Adding LWP and IWP to default_spec.yml, with unit as g/m2.
This is tested on WFIP3 (WRF runs) UPP output. It should also work for HRRR.
Example plots as below:

Thanks @cshartsough !
The high end of the range does look saturated. The current colorbar range is per the users' (the local wfip team) request, so it should be good for a while;
Removed the extra whitespace at the end of the new kg-to-g conversion;
The last commit is to add lwp and iwp to wfip image lists.


connect two or more views

Hi! Is it possible to connect two or more calendars with each other with drag and drop capabilities? I need it for some timetable software for a local festival with multiple stages.

This should just work out the box with no extra configuration, the only thing you'll need to do is when dropping on one calendar with the on-event-times-changed hook, check if the event is in the other calendar and remove it from that calendars events array. Here's an example that's kind of similar to what you need:
http://mattlewis92.github.io/angular-bootstrap-calendar/#?example=draggable-external-events

Thanks a lot!
Just another question, if I'm right you can only change the events label on the day view globally in the CalendarConfig, could you add an eventsLabel tag to the directive itself?
Thanks!


Update cass-operator

This PR updates has the following changes:

Update cass-operator to 1.6.0
Update CassandraDatacenter manifest to be consistent with latest in k8ssandra
Update medusa.ini for s3

I see only test updates, should this update the go.mod also to use 1.6.0 ?


Rare NPE if presenter used in onActivityResult

implementation "com.arello-mobile:moxy:1.5.5"
implementation "com.arello-mobile:moxy-android:1.5.5"
kapt "com.arello-mobile:moxy-compiler:1.5.5"

This is pretty rare crash and i could not reproduce it on my devices.
Crashlytics reports — http://crashes.to/s/4a9639b6eba, http://crashes.to/s/a2bb8339d24
Crashlytics report sample — com.mirrorai.app_issue_1947_crash_5C115CBA03CC000111718A8B503A537C_DNE_0_v2.txt
I have several fragments that receives results via onActivityResult. Let's take photo gallery for example:
class TakingPhotoFragment : MirrorFragment(), TakingPhotoView {

    @InjectPresenter
    lateinit var presenter: TakingPhotoPresenter

    @ProvidePresenter
    fun providePresenter() = TakingPhotoPresenter()

and a bit later in this class
    override fun takePhotoFromGallery() {
        val intent = Intent()
        intent.type = "image/*"
        intent.action = Intent.ACTION_GET_CONTENT

        startActivityForResult(Intent.createChooser(intent, "Select Picture"), REQUEST_CODE_PICK_IMAGE)
    }

    override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
        if (requestCode == REQUEST_CODE_PICK_IMAGE) {
            if (resultCode == Activity.RESULT_OK) {
                if (data != null) {
                    presenter.uploadPhotoFromGallery(data)
                }
            }
        }
    }

presenter in uploadPhotoFromGallery sometimes (rarely but noticeable) is null and causes NPE.
I use custom base fragment MvpAndroidXFragment that is just Kotlin clone of MvpAppCompatFragment for AndroidX — https://gist.github.com/asfdfdfd/87552746c9182f6b7311f3d9ce6272a6.
But this issue has appeared before migrating to Android X.

It seems that onActivityResult called before onCreate. But this shouldn't. Could you debug please, that onCreate called before onActivityResult or not?

Okay. I'll add logs to the onCreate and onActivityResult of base fragment.

It will be something like this.
abstract class MirrorFragment : MvpAndroidXFragment(), OnBackPressedListener {

    private var isOnCreateCalledBeforeSuper = false
    private var isOnCreateCalledAfterSuper = false

    override fun onCreate(savedInstanceState: Bundle?) {
        isOnCreateCalledBeforeSuper = true

        super.onCreate(savedInstanceState)

        isOnCreateCalledAfterSuper = true
    }

    override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
        if (!isOnCreateCalledBeforeSuper || !isOnCreateCalledAfterSuper) {
            Timber.e("onCreate is not called: %b, %b.", isOnCreateCalledBeforeSuper, isOnCreateCalledAfterSuper)
        }

        super.onActivityResult(requestCode, resultCode, data)
    }
}

This code was in production for a while and i never had logs in Crashlytics about "onCreate is not called". So at least in this case onCreate is seems to be called.
I could check other things if you have any ideas.


Allow grads to be scaled by tensors in tf.contrib.layers.optimize_loss()

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.8
Python version: 2.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory: TitanX Pascal
Exact command to reproduce:

Describe the problem
tf.contrib.layers.optimize_loss() currently allows gradient multipliers by passing a gradient_multipliers dictionary of {variable_name: multiplier} where multiplier is a python float. It would be useful to allow multiplier to be tensor so that gradient scaling could be, for example, tied to global_step.
It seems like this could easily be implemented  by not pushing the multiplier to a constant in _multiply_gradients function at https://github.com/tensorflow/tensorflow/blob/e37baff90ed84faef679bbf1e785e6790fd2739d/tensorflow/contrib/layers/python/layers/optimizers.py#L436-L437
Is there a reason why the dict shouldn't contain tensors that I'm overlooking?

Added a PR #22350 for tensor support.

thank you!


Gitea Authentication no longer working with NGINX Proxies

Gitea version: 1.11.0+dev-34-gd151503d3
Operating system: Ubuntu 18.04
Database:

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist for Docker log, Docker-Compose and NGINX proxy: https://gist.github.com/a20eac1d/925d72a3ad6f0d1f8d9d5bd1240d6156

Description
I recently updated my Gitea Docker container to the latest version and it seems like one of the last Gitea updates broke compatibility with NGINX web proxies.
After setting up the Gitea instance and creating an account I will be immediately logged in without entering any credentials. When switching devices or computers, I still dont have to login with my password. My account is automatically logged in WORLDWIDE on EVERY device.
The "Logout" button does nothing and simply redirects me to my dashboard.

Hi! It's difficult to know what the causative change is as this is highly configuration dependent on your proxy and I'm not sure how to go about setting up a test environment for this - any test harness would be highly complex.
Could you tell us what the last known working version was?
Are you able to do a git bisect from a known working version and the latest?
The code that handles this is as follows and the majority of it is 3 years old with 10 months being the youngest:
https://github.com/go-gitea/gitea/blob/6ddd3b0b470d16dfe62caf5fff21011cfff44a76/modules/auth/auth.go#L134-L169
As you can see if the X-WEBAUTH-USER header is set then the user will be logged in automatically as the appropriate user.
To log out from this you would need to log out from both Gitea - removing the session from gitea and log out from the WEBAUTH host - meaning that it no longer sends the X-WEBAUTH-USER.
Hmm... we did change some more upstream auth bits but I'm not sure that these would account for this.

Oh wow, it is the auto-login caused by logging in to HTTP Basic-Auth.
When the login details for both HTTP Basic-Auth and Gitea are the same, it will login automatically.
What a strange feature.
Is there any chance that you could disable it by default? Those two login systems should definitely be seperate. It makes no sense to have it turned on automatically and I'm sure it will cause confusion in the future.

I tried to disable the feature using: https://docs.gitea.io/en-us/config-cheat-sheet/
ENABLE_REVERSE_PROXY_AUTHENTICATION
Setting it to false does not seem to have any impact on the issue. Am I using it wrong?
[service] DISABLE_REGISTRATION              = true REQUIRE_SIGNIN_VIEW               = true REGISTER_EMAIL_CONFIRM            = false ENABLE_NOTIFY_MAIL                = false ALLOW_ONLY_EXTERNAL_REGISTRATION  = false ENABLE_CAPTCHA                    = false DEFAULT_KEEP_EMAIL_PRIVATE        = false DEFAULT_ALLOW_CREATE_ORGANIZATION = true DEFAULT_ENABLE_TIMETRACKING       = true NO_REPLY_ADDRESS                  = noreply.example.org ENABLE_REVERSE_PROXY_AUTHENTICATION = false ENABLE_REVERSE_PROXY_AUTO_REGISTRATION = false ENABLE_REVERSE_PROXY_EMAIL = false

Those default values are already false.

He's looking for a way to disable basic authentication in Gitea - I don't think we have that.

Those default values are already false.

Those default values weren't in the "app.ini" created by Gitea, I had to add them.
But even now, they don't do anything. Setting them to true/false does nothing.

@a20eac1d those settings are for a different type of login - in that case the proxy server is setting a X-WEBAUTH-USER header. Basic authentication is set using the AUTHORIZATION header with type basic.
We have no setting to turn that mode of authentication off at present - it's used in the API, predominantly for controlling tokens. I think it would be possible to add a simple config switch to disallow this method of authentication though.


The converastion State is not persistent for the proactive notification

I create a chatbot that is able to send a proactive notification but when I publish the bot again it loses its conversation reference
There are not enough resources/example for the same to maintain the conversation refrence

@kandy99 - Okay so how would you like us to help you? You haven't included a question in your post, so it's unclear if you want us to fix your bot for you or if you want us to make a new sample, etc.

it will be good if there is a proper sample for this problem

Closing due to issue microsoft/BotBuilder-Samples#2825, please follow that one for updates. Thank you!


Support for non-valid UTF-8 strings

Extend code to support non-valid UTF-8 strings in filenames, paths and arguments:

Use OsStr and OsString.
Follow OsStr pattern API extension in Rust repository.
Check issues with current crates: clap, regex, walkdir and ansi_term

Right now it is not possible to convert OsStr(ing) to &[u8] on Windows to be used in regex::bytes::Regex::replace without losing information. For example, ripgrep uses a to_string_lossy conversion to obtain a &[u8] in Windows.

Yeah, this is something I've always wondered about. So far, I haven't had anyone complain about cases where information is lost, i.e., when there's an invalid UTF-16 file path on Windows. One presumes that this might be so infrequent that it may not be a blocking problem in practice.
Getting a real fix for this is tricky. One possibility is to use the underlying representation of an OsStr (which is WTF-8), but this is not part of the public API. Another possibility is to re-create WTF-8 decoding outside of std using the Windows version of the OsStrExt trait. But this incurs a second WTF-8 decoding step, however, it's no worse than the lossy UTF-8 decoding that I'm already doing.


refactor: simplify arbitrary logic

Current dependencies on/for this PR:

main

PR #29   👈

This comment was auto-generated by Graphite.


Update dsact algorithm:

Add moving average clip bound and  critic updating weight.

Update dsac-t algorithm