Always use window.analytics

Explicitly use window.analytics in assets/analytics
Related conversation: https://artsy.slack.com/archives/C02BC3HEJ/p1596460574246500

There was another bug related to this -- we require analytics once, but it isn't fully initialized at this point.


made some edits to improve readability

I made some minor edits to improve the readability of the text. The text read like a telegram or a non-native speaker had typed it. No offense to non-native English speakers intended.

Thanks for the grammar check! Merged.


[FEATURE] Ingame description what actually team rank gives

Is your feature request related to a problem? Please describe.
I looked for in-game info what current team level gives for team, and what next team level could give for team. And generally I tried to find with /team help, but I didn'f found something like this. /team info and /team rank doesn't show such things either.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
I mean info what actually team level gives, for example, how many chests you can have, how many warps you can set, how many people you can invite.
Example output of /team rank (or other command) I'm looking to:
Team rank: 5 ($ 10800 needed for next rankup)
Max team members: 5 (9 at next rank)
Max team chests: 1 (1 at next rank)
Max team warps: 3 (4 at next rank)
...

And so on, if more parameters are possible to set to upgrade with team rankup :)
Currently /team rank gives only first line of this example.
Additional context
It could be like 'wildcard'/free to define per team rank, where designer of team ranks could put whatever he likes into /team rank
Because for now, there is no in-game way to obtain info what team provide for you and what gives next rank...
For example:
levels:
  l1:
    teamLimit: 3
    maxChests: 0
    maxWarps: 1
    rankLore:
      - "&6Max team members:&3 3&7 (5 at next rank)"
      - "&6Max team chests:&3 0&7 (1 at next rank)"
      - "&6Max team warps:&3 1 &7(2 at next rank)"
      - "&6Daily team minor owner reward!"
  l2:
    teamLimit: 5
    maxChests: 1
    price: 1000m
    maxWarps: 2
    rankLore:
      ...

It would cover almost any needed additional description despite features you'll add in future :)
Just a free idea of 'end user usage', use it or drop it however you like ^^

This feature has been implemented and will be included in the next update. Thank you for the suggestion.


Request: Add GPT-4 Turbo with vision

Add GPT-4 Turbo with vision to use it like in the Official ChatGPT app.

This issue will be closed as it duplicates issue #34.


[WIP PR] Assessments

Pull Request Test Coverage Report for Build 191

0 of 252 (0.0%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-52.7%) to 33.656%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/cadet/assessments/submission_status.ex
0
1
0.0%

lib/cadet/assessments/problem_type.ex
0
1
0.0%

lib/cadet/assessments/mission.ex
0
1
0.0%

lib/cadet/assessments/submission.ex
0
8
0.0%

lib/cadet/assessments/Question.ex
0
9
0.0%

lib/cadet/assessments/answer.ex
0
9
0.0%

lib/cadet_web/controllers/question_controller.ex
0
10
0.0%

lib/cadet_web/controllers/assessments_controller.ex
0
20
0.0%

lib/cadet/context_helper.ex
0
23
0.0%

lib/cadet/assessments.ex
0
170
0.0%

Totals

Change from base Build 146:
-52.7%

Covered Lines:
139

Relevant Lines:
413

💛  - Coveralls

@sreycodes I think we should separate the controller PR from the model PR -- this PR is already very large.

@tuesmiddt I feel this should be ready to merge, but since I made the edits, I think it's good that you have a lookthrough. If everything is alright, I'll merge this tomorrow.


Make class DeleteResult namespaced PSR-0 compatible

1. Why is this change necessary?
The class \Shopware\Recovery\Update\DeleteResult is placed in a subfolder of the "Update" folder which means it isn't PSR-0 compatible. This is compensated by composer autoloading optimisation but still not a good practice.
2. What does this change do, exactly?
Change FQN class to \Shopware\Recovery\Update\Results\DeleteResult
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hi @pascalheidman-bedarf, thank you for your contribution! 👍 💙


linux-micro automount module

In larger systems we have a set of tools to handle automount, such as udev and blkid to detect and flag devices that are later handled by udisks, that will mount them.
Linux-micro should provide module that is not as capable, but will at least mount media from mmc/usb. Since linux-micro is basically a single-user system, all we need to do is the shared mode that mounts /run/media/MOUNTPOINT. If we're linked with libblkid we can get more information about the device and keep a stable mount point. Otherwise we should use heuristics such as try to mount ext4/ext3/vfat and use the device name as mount point.
Devices can be discovered using netlink messages that expose new devices, likely to be shared with #676. Eventually we should do this as a generic sol_udev API that uses libudev when platform is systemd and direct handling in the other cases -- or always force libudev, need to check if it requires udevd (daemon) and the amount of code it brings in to libsoletta.so.
If possible try to mount using the mount(2) syscall, if it does not work then fallback to mount(1) binary.
(This is not a blocker for v1)

implemented on b039721b81ba46dbea889b603cdc054cc3ac4ef8


SHIBEURO isn't triggering sell grid

Running Version:
v0.0.83
(366761b)
Latest Version:
v0.0.83
The action for SHIBEURO is locked and no sell orders being placed although it should be triggered
also it doesn't trigger manually and in the log it is showing that it is trying to
Expected Behaviours
place stop sell order

Hi @bassel-desoky
In the logs, you can click the data icon to view the parameters.
Can you provide that? So I can test it out?

@bassel-desoky Since I didn't get more information from you, I will close the issue.
Please open a new issue if you have the same issue. And provide me with exported logs.


When I go to rename the name of some File Files UWP - Preview it closes automatically appearing this error to me saying this print screen correct this please so I can rename the name of all Files

Describe the bug
A clear and concise description of what the bug is and why it is more urgent than other issue reports. Can't answer this? Please return to the previous page and file a regular bug/feature report.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 10 1903 18362.175]
App version: [v0.11.0]

Additional context
Add any other context about the problem here. For instance, are you building from source or using a precompiled build/snapshot?
Log file
Please post the log file here so that we can understand your problem better. You can access it from Settings->About->Open log location.

When I go to rename the name of some File Files UWP - Preview it closes automatically appearing this error to me saying this print screen correct this please so I can rename the name of all Files

@AngelZeur Can you try updating to v0.15 and let us know if you still see this issue?


API changes for user/:id/campaigns

Placeholder for upcoming API changes for retrieving a User's campaign activity.
Refs https://github.com/DoSomething/northstar/issues/237#issuecomment-179448015
This endpoint may end up getting deprecated altogether in favor of a signups endpoint.

Per https://github.com/DoSomething/northstar/pull/273 we'll be querying the Phoenix signups endpoint. We'll also need to store a User's phoenix ID to filter the Signups uid.

https://github.com/DoSomething/northstar/pull/278 makes changes so we don't have to pass the phoenix ID anymore (which actually also currently breaks develop with the changes made in #827)

When rendering the User's Doing campaigns, we'll only want to pay attention to Signups where campaign_run.current = true - per https://github.com/DoSomething/phoenix/pull/6165


Export C bindings

Related:

https://github.com/Jarred-Sumner/bun/issues/202

Another reference: Zig FFI

https://github.com/oven-sh/bun/issues/591#issuecomment-1378027682
https://github.com/kassane/zFFI/issues/2 (progress report - cbindgen-fork)


Clean up metadata Sample model object saving logic in Project::get_samples

Context

Inside Project::load_data, once metadata has been parsed, collected and combined, Project::get_samples is called to create Sample objects which will soon be saved to the database.
Project::get_samples also edits the following 4 fields on each sample:

demux_cell_count_estimate
multiplexed_with
seq_units
technologies

Problem or idea

There's no reason why these 4 sample fields should be edited here and not when the other fields are being edited earlier on.
Additionally, the naming isn't clear - samples are not retrieved here, as the name get_samples seems to be indicate, but rather objects are created in memory in order to be saved soon to the database.
Solution or next step

Extract all field editing logic from this method and handle it in the normal flow of metadata parsing (or move into its own method).
Rename method to generate_sample_objects or create_sample_objects.

Another point connected to this issue is that after the sample objects are created, they should be immediately saved to the database.
Currently these sample objects are stored in a list and are saved to the db during sample file computation, as follows ^1:
for sample in Sample.objects.bulk_create(samples):

This seems like needless coupling. Better would be to save the sample objects when they're created, and then to query for them from the database when the time comes to begin file computation, as follows:
for sample in Sample.objects.filter(project__scpca_id=kwargs["scpca_project_id"])`

Should I wait until the multiplex refactor before tackling this one?

Issue addressed in PR https://github.com/AlexsLemonade/scpca-portal/pull/697


DRILL-4596: Drill should do version check among drillbits

So how is the version actually set? Is it just the bit to register with Drill? Is there a config setting that we can set in drill-override that sets the cluster version?  Where is the "master" version stored, and how do we move away from that?
Thanks

Drill version is defined from build manifest file [1].
There is no config setting to override it. Though if you want to change version in "master", you'll have to update version property in pom.xml files. (1.7.0-SNAPSHOT)
[1] https://github.com/apache/drill/blob/master/common/src/main/java/org/apache/drill/common/util/DrillVersionInfo.java

Updated PR.
New implementation approach:

we allow to register any drillbit (disregarding the version).
instead of getting available endpoints from coordinator, we'll be receiving compatible endpoints. Version compatibility will be defined using main application version (major.minor (+ 1). For example, drillbit with version 1.8 can work with 1.8 and 1.9. Drillbit with version 1.9 can work with 1.9 and 2.0 and so on. Even during rolling upgrades, compatible endpoints will be able to work together.

Should it be +-1, not just +1 ? Otherwise in your scheme 1.9 can work with
2.0, but can not with 1.8, while 1.8 can work with 1.9.
On Mon, Apr 11, 2016 at 9:08 AM, arina-ielchiieva<EMAIL_ADDRESS>wrote:

Updated PR.
New implementation approach:

we allow to register any drillbit (disregarding the version).
instead of getting available endpoints from coordinator, we'll be
receiving compatible endpoints. Version compatibility will be defined using
main application version (major.minor (+ 1). For example, drillbit with
version 1.8 can work with 1.8 and 1.9. Drillbit with version 1.9 can work
with 1.9 and 2.0 and so on. Even during rolling upgrades, compatible
endpoints will be able to work together.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/apache/drill/pull/474#issuecomment-208428822

I thought it's hard to maintain backward compatibility. Quoting Parth comment from Jira:
"Drill needs to be able to run queries that depend only on features that are in the oldest version of Drill in the cluster. Say for example, most drillbits are at version N and some are at version N+1. You added support for a new type foo in version N+1. Any queries not using or depending on type foo should run successfully. Queries depending on foo can only run successfully after all the drillbits are upgraded to N+1."

Not sure how that comment contradicts with what I said. Adding new feature in the next version should not break previous version.

On Apr 11, 2016, at 12:41 PM, arina-ielchiieva<EMAIL_ADDRESS>wrote:
I thought it's hard to maintain backward compatibility. Quoting Parth comment from Jira:
"Drill needs to be able to run queries that depend only on features that are in the oldest version of Drill in the cluster. Say for example, most drillbits are at version N and some are at version N+1. You added support for a new type foo in version N+1. Any queries not using or depending on type foo should run successfully. Queries depending on foo can only run successfully after all the drillbits are upgraded to N+1."
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

If we add new type to version 1.7, it can't work with  version 1.6 where this type is absent, that's why I am adding support only for +1 version. At this point in my implementation, 1.6 can work with 1.6 and 1.7. 1.7 can work with 1.7 and 1.8.

Hi All. Version compatibility is a complex issue. Do we have a design document that explains our goals and policy? Is the goal to allow rolling updates of clients? (Drill server at, say 1.8, rolling upgrade of client from 1.7 to 1.8, old clients work)? Or, is it to allow rolling upgrades of servers? Both?
MapR customers receive even releases: 1.4, 1.6, 1.8. Would the +/-1 policy benefit them?
As I understand it, each Drill bit is to work with another of +/-1 version. But, what I bring up Drill 1.6, Drill 1.5 and Drill 1.4. The 1.5 is happy to work with both 1.6 and 1.4. But, the 1.6 and 1.4 versions will fail only when they communicate with one another. When will this communication occur? At startup? Or, only later when, say, 1.6 tries to send a query to 1.4?
Does this mean that Drillbits should advertise their version in ZooKeeper so that we fail fast and can provide a clear error message?
Dremio proposes a new 2.0 release that breaks compatibility. Will Drill 1.9 (say) be compatible with the incompatile Drill 2.0? Should it be?
As others have said, we need to consider wire protocol and semantics. The usual solution is protocol negotiation. If a 1.6 client connects to a 1.7 server, they agree to "speak" 1.6. If a 1.7 client connects to a 1.6 server, they also agree to "speak" 1.6. Such as solution has impact on our messaging layer. It increases testing requirements.
Drill-on-YARN will provide another way to do server upgrades (ramp up a new cluster while ramping down an old one.) Otherwise, YARN will need some way to run the same cluster, replacing version X drillbits with version X+1 (while still running the version X Application Master).
Are all these issues spelled out in a design doc?
IMHO: let's not try to bug fix our way to success here; let's step back and work out a complete design.

Some other design issues. The idea of a rollling upgrade presupposes that we can shut down a Drillbit, bring up a new one, and the cluster keeps running. But, today, bringing down a Drillbit causes all in-flight queries on that node to fail. There is no way to mark a node as "quiescent" (up, but not accepting new work.) So, a rolling upgrade today would entail a long series of query failures as we replace each of, say, 20 or 50 nodes.  (See DRILL-4286.)
Back on testing: testing is essential. A feature that allow +/-1 feature compatibility is not helpful unless someone (other than the user) can certify that it works. If the user gets to do the checking, then it is not very helpful: safer just to do a full upgrade.
To emphasize an earlier point: there are two distinct issues. One is a managed cluster upgrade (the admin can do it with the help of a management tool.) The other are the many Drill clients spread across desktops: that is a classic desktop software upgrade. Some might be on planes, others locked in desks while someone is on vacation. Let's think about how to upgrade JDBC drivers and the like given this reality.
Is the compatiblity policy number or time based? As an admin, can I expect to have a three-month window for upgrades? Or, will it sometimes be one month, others four months, depending on who changes what? Should we have a time-based policy?

In general, I'm against version number checking. We did that in the code early on but we should be moving towards a capabilities flag approach.
Also agree with Paul in his mention of DRILL-4286, don't think worrying about rolling upgrade makes sense until we resolve the issues around decommissioning.


How to hide column using && and false variable

I've made component with reusable table.
Now I want to show/hide few columns with passed props value, for example.
I've tried this:

And got an error Uncaught TypeError: Cannot read property 'props' of null

I found hidden property, but it hides column just visually.
Do you have any suggestions how to fix it?

@Kolyasya, for this case, we don't support this usage, you may need to do it like following
const columns = your_columns_meta.map(column => {
    if (column.showColumn) { // some condition for displaying column or not
        return (
            <TableHeaderColumn ......>
        );
    }
});

<BootstrapTable>
    { columns }
</BootstrapTable>


Helm install support

Hi,
I checked out your plugin, is it possible to execute "helm upgrade" or "helm install" or can I really only publish, manage and build charts?

Hi! Yes, this is just not documented yet ;-)
Also please note this is all still work in progress, so it might still be buggy.
First, there's tasks for all of the common remote operations, so you can use the HelmInstall or HelmUpgrade task type directly. There's also a HelmInstallOrUpgrade task which does either helm upgrade --install or helm install --replace depending on a replace flag. All of these tasks are very similar in configuration though.
task installOrUpgradeFoo(type: HelmInstallOrUpgrade) {
    chart = 'stable/mariadb'
    releaseName = 'mariadb'
    version = '5.1.1'
    values = [ 'rootUser.password': 'secret' ] // like --set command line flag
    valueFiles = files('mariadb.yaml')      // like -f command line flag
}

Alternatively (and preferred), there is also a separate plugin for this which builds on the base Helm plugin. It allows you to declare your releases using a DSL, and the tasks will be auto-generated. You can also reference charts that were built by other Helm tasks before.
plugins {
    id 'org.unbroken-dome.helm-releases' version '0.2.1'
}

helm {
    releases {
        mariadb {
            from 'stable/mariadb'
            version = '5.1.1'
            values = [ 'rootUser.password': 'secret' ] // like --set command line flag
            valueFiles = files('mariadb.yaml')      // like -f command line flag
        }
    }
}

This should automatically give you tasks helmInstallMariadb and helmDeleteMariadb.
For the target Kubernetes cluster you can configure most properties inside the helm or helm.tiller block. It is also possible to use project properties (they map pretty much directly e.g. helm.kubeConfig) so you can put these in your gradle.properties, or call it like this:
./gradlew helmInstallMariadb -Phelm.kubeConfig=... -Phelm.kubeContext=...

Thanks for the quick reply! Will test all of this :)


chore(renovate): add automerge settings

Add automerge to devDependencies in Renovate configuration.
However, the package related to rollup was excluded because of the influence on the bundle.

:tada: This PR is included in version 1.8.0-beta.1 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.1 :tada:
The release is available on:

GitHub release
npm package (@alpha dist-tag)

Your semantic-release bot :package::rocket:

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Fix release process

The real build is done in releasebuild, so that's where we need to process the build log.

(The CI will take ages on this, but will be irrelevant - so don't wait for that :)


Add note about memory usage during build.

@juliusv @brian-brazil Do you remember the exact threshold we have seen?

:+1:
Would splitting the files into 1kB chunks help?


fix: handle errors in background jobs nicely

closes #447
/deploy

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 90.477%

Files with Coverage Reduction
New Missed Lines
%

components/renku_data_services/base_api/misc.py
1
98.41%

components/renku_data_services/users/db.py
1
94.01%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
9586

Relevant Lines:
10595

💛  - Coveralls

Tearing down the temporary RenkuLab deplyoment for this PR.


Column group top-left header cell draws unnecessary border

When using column groups, top-left header cell renders additional border, which is barely unnoticeable on demo:

but after some theme customization it becomes really visible:

Thank you for the report, will fix

Fixed in main, look for it in 5.1.3


Return Test Does Not Match Instructions

Challenge Waypoint: Delete Properties from a JavaScript Object has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var ourDog = {
  "name": "Camper",
  "legs": 4,
  "tails": 1,
  "friends": ["everything!"],
  "bark": "bow-wow"
};

delete ourDog.bark;

var myDog = {
  "name": "Happy Coder",
  "legs": 4,
  "tails": 1,
  "friends": ["Free Code Camp Campers"],
  "bark": "woof"
};

// Only change code below this line.

delete myDog.tails;

// Only change code above this line.

(function(z){return z;})(myDog);

The instructions state: "Let's delete the "tails" property from myDog." with example of how to do this as "delete myDog.bark;"
To complete the challenge the user must use the example instead of the instructions. This mismatch should be addressed.

This has been closed by PR #3967 and is pending deployment to the website.
Closing as resolved.
Thanks and happy coding!

Thanks!


Code editor doesn't support my keyboard layout

Environment

Elixir & Erlang/OTP versions (elixir --version):

Erlang/OTP 23 [erts-<IP_ADDRESS>] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe]
Elixir 1.12.0 (compiled with Erlang/OTP 23)

Operating system: macOS Big Sur 11.4

Livebook version: 0.1.2

How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): MIX_ENV=prod mix phx.server

Browsers that reproduce this bug (the more the merrier):

Chrome 91.0.4472.106
Safari 14.1.1 (166<IP_ADDRESS>.4)

Spanish ISO Keyboard Layout

Include what is logged in the browser console: nothing of interest.

Include what is logged to the server console: nothing of interest.

Current behavior
While in Firefox 89.0 it works fine, I can't get the bracket characters like { and } in the code editor when working in Chrome or Safari. I have a Spanish ISO Keyboard layout. This seems an issue or misconfiguration with Monaco Editor.

Expected behavior
I'd like to be able to include all characters in my keyboard layout! :)

I think that Tailwind Play also uses Monaco Editor - brackets work fine there in Chrome.

Thanks @jaimeiniesta! Quick question: if you are running from master, can you please share your commit?

Yes, I just downloaded it today, commit is https://github.com/elixir-nx/livebook/commit/2b2d6c9d509b02d64d428f93844598168bb65e60

@jaimeiniesta is it the case only for Elixir cells, or for Markdown cells as well? Also, does it work on the Monaco homepage?

@jonatanklosko it happens both on Elixir and Mardown cells.
It works fine on the editor in Monaco homepage, and on Tailwind Play.

There's a recent issue that looks relevant (https://github.com/microsoft/monaco-editor/issues/2533) and it a has been addressed in monaco 0.25.2. I've just updated to this version in e49aaa62d2250f837ffd4b8b5ed582621377bcfb, please let me know if this helps :)

Yay! It works great now, thanks!

Verified in Chrome, Safari and Firefox.

Thanks for verifying! :cat:


[BUG] Deletion rules ignore non-trigger characters in rule

Plugin Version: 3.0.0
Plugin Version: 0.15.9
I have this rule:
'[|]' -x '|'

but this deletion rule triggers when I have '[|', and deletes whatever character is after.
For example, when I have '[|[' and when I delete it, it removes both of the [, when the rule shouldn't even trigger at all.

I have reproduced this promblem, I will fix soon, thank you

this is fixed in https://github.com/aptend/typing-transformer-obsidian/commit/afe08c8ff4edc24e806d4f5bd3313a231b8bd54f, after #46 is merged, I will a patch 0.3.1


Make script/lsmon more readable

Running script/lsmon gives you a dump of all monitoring resources available on the current account, mostly by using their native string representations. It's complete, but it's also very difficult to read. This removes the RAX_REGION environment variable (which is unnecessary because Cloud Monitoring is regionless) and changes the output format to be less complete, but more readable, by grouping Checks and Alarms beneath their associated Entities.
Here's a sample of the new output:
-- DFW_entity_staging (id=en7Fovi5Km)

  CHECK http_check_sdk : (type=remote.http,id=ch0f4Wun0P)

  CHECK http_check_blog : (type=remote.http,id=chDkxCbnW2)

  CHECK http_check_index : (type=remote.http,id=chEaJIBIuh)

  CHECK http_check_redirect : (type=remote.http,id=chYsEgAQHv)

  ALARM DFW_staging_index_is_down : (id=al4clQ3O9j)
    check=chEaJIBIuh
    notification_plan=npPEeaxqJp
    criteria:
      :set consecutiveCount=2
      if (metric['code'] != "200") {
        return new AlarmStatus(CRITICAL, "Non-200 status code #{code} returned.");
      } if (metric['body_match'] == "") {
        return new AlarmStatus(CRITICAL, "Expected page content not found.");
      } if (metric['cert_end_in'] < 5184000) {
        return new AlarmStatus(WARNING, "SSL certificate will expire in less than 60 days.");
      } return new AlarmStatus(OK);

  ALARM DFW_staging_sdk_is_down : (id=albe86uhrV)
    check=ch0f4Wun0P
    notification_plan=npPEeaxqJp
    criteria:
      :set consecutiveCount=2
      if (metric['code'] != "200") {
        return new AlarmStatus(CRITICAL, "Non-200 status code #{code} returned.");
      } if (metric['body_match'] == "") {
        return new AlarmStatus(CRITICAL, "Expected page content not found.");
      } if (metric['cert_end_in'] < 5184000) {
        return new AlarmStatus(WARNING, "SSL certificate will expire in less than 60 days.");
      } return new AlarmStatus(OK);

  ALARM DFW_staging_redirection : (id=alfHO3HAoS)
    check=chYsEgAQHv
    notification_plan=npPEeaxqJp
    criteria:
      :set consecutiveCount=2
      if (metric['code'] != "301") {
        return new AlarmStatus(CRITICAL, "Non-301 status code #{code} returned.");
      } return new AlarmStatus(OK);

  ALARM DFW_staging_blog_is_down : (id=allxL9nT4S)
    check=chDkxCbnW2
    notification_plan=npPEeaxqJp
    criteria:
      :set consecutiveCount=2
      if (metric['code'] != "200") {
        return new AlarmStatus(CRITICAL, "Non-200 status code #{code} returned.");
      } if (metric['body_match'] == "") {
        return new AlarmStatus(CRITICAL, "Expected page content not found.");
      } if (metric['cert_end_in'] < 5184000) {
        return new AlarmStatus(WARNING, "SSL certificate will expire in less than 60 days.");
      } return new AlarmStatus(OK);

Notifications and Notification Plans are summarized above.

Self-merging because this would be very handy.


Arc april updates

Does the azdata extension version need to be increased?

@bergeron Not for typing-only changes (those are build/compile time only)
(and FYI I'm fixing the compile errors now)

Pull Request Test Coverage Report for Build 786651784

2 of 131 (1.53%)  changed or added relevant lines in 6 files are covered.
35 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.2%) to 43.406%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/arc/src/models/miaaModel.ts
0
2
0.0%

extensions/arc/src/models/postgresModel.ts
2
5
40.0%

extensions/arc/src/ui/dashboards/miaa/miaaConnectionStringsPage.ts
0
3
0.0%

extensions/arc/src/ui/dashboards/miaa/miaaComputeAndStoragePage.ts
0
4
0.0%

extensions/arc/src/ui/dashboards/miaa/miaaDashboardOverviewPage.ts
0
5
0.0%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
0
112
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/arc/src/ui/dashboards/miaa/miaaDashboardOverviewPage.ts
1
3.28%

extensions/arc/src/ui/dashboards/postgres/postgresComputeAndStoragePage.ts
2
0.83%

extensions/schema-compare/src/dialogs/schemaCompareDialog.ts
32
50.13%

Totals

Change from base Build 779361176:
-0.2%

Covered Lines:
26266

Relevant Lines:
55061

💛  - Coveralls


export-metadata v2 design

The independent export-metadata workflow which use a gce image as source. the output is a metadata.file in gcs.
Update:

Use linux_common to retrieve metadata and upload file.
Remove project level variable
make some variable as not required.

Testing:
Debian:
https://pantheon.corp.google.com/storage/browser/_details/hanga-testing-daisy-bkt/daisy/hanga/daisy-export-metadata-20201001-22:34:06-1qb9x/logs/inst-exporter-export-metadata-1qb9x-serial-port1.log?organizationId=433637338589&project=hanga-testing
RHEL:
https://pantheon.corp.google.com/storage/browser/_details/hanga-testing-daisy-bkt/daisy/hanga/daisy-export-metadata-20201001-22:34:06-1qb9x/logs/inst-exporter-export-metadata-1qb9x-serial-port1.log?organizationId=433637338589&project=hanga-testing
Daisy Output.
[export-metadata.wait]: 2020-10-01T22:34:26Z WaitForInstancesSignal: Instance "inst-exporter-export-metadata-1qb9x": StatusMatch found: "ExportStatus: Package metadata is gce-disk-expand"
[export-metadata.wait]: 2020-10-01T22:34:26Z WaitForInstancesSignal: Instance "inst-exporter-export-metadata-1qb9x": StatusMatch found: "ExportStatus: Uploading image metadata."
[export-metadata.wait]: 2020-10-01T22:34:26Z WaitForInstancesSignal: Instance "inst-exporter-export-metadata-1qb9x": StatusMatch found: "ExportStatus: ExportSuccess: Export metadata was successful!"
[export-metadata.wait]: 2020-10-01T22:34:26Z WaitForInstancesSignal: Instance "inst-exporter-export-metadata-1qb9x": SuccessMatch found "ExportSuccess: Export metadata was successful!"
[export-metadata]: 2020-10-01T22:34:26Z Step "wait" (WaitForInstancesSignal) successfully finished.
[export-metadata]: 2020-10-01T22:34:26Z Running step "delete-inst" (DeleteResources)
[export-metadata.delete-inst]: 2020-10-01T22:34:26Z DeleteResources: Deleting instance "inst-exporter".
[export-metadata.delete-inst]: 2020-10-01T22:34:42Z DeleteResources: Deleting disk "source-disk".
[export-metadata.delete-inst]: 2020-10-01T22:34:42Z DeleteResources: Deleting disk "disk-exporterprep".
[export-metadata]: 2020-10-01T22:34:43Z Step "delete-inst" (DeleteResources) successfully finished.
[export-metadata]: 2020-10-01T22:34:43Z Workflow "export-metadata" cleaning up (this may take up to 2 minutes).
[export-metadata]: 2020-10-01T22:34:47Z Workflow "export-metadata" finished cleanup.
[Daisy] Workflow "export-metadata" finished
[Daisy] All workflows completed successfully.

/lgtm


feat: delay on opening preview (also fix lags on fast scroll)

The main reason of adding it is lags when you fast scroll list of files with preview toggled on. I've tested with preview off, and there is no lags. So I think a small delay would fix it.

Is the lag a new issue from the last commit? I just enabled instant syntax highlighting on the preview window which may have caused this issue.

No, I was at dca31060e21a367234e8f2a6fabc3051ab85fe9c and lags already exist. But now I also checked out your last commit with "instant syntax highlighting" and see that lags  increased heavily.

Also, done some research and found that "first" lags started at commit 28f3bcac27b6dbab37102336a22a38b81a6c4089 (disable preview for binary files)

Try the latest commit https://github.com/ibhagwan/fzf-lua/commit/29ae04d73f7289fc17d99c08649b58f46a87bdce, it adds a default 60ms delay, solved fast scrolling for me, you can see the preview stays empty until you release the down arrow, you can change the delay (or disable it) by setting previewers.builtin.delay.
Let me know if that works better?

Also, done some research and found that "first" lags started at commit 28f3bca (disable preview for binary files)

I have to find a better method to detecting binary files anyways, I don't know why but file --dereference --mime thinks some of my .lua files are binary...

Works good. Now it fast as if preview completely disabled. Thank you!

Works good. Now it fast as if preview completely disabled. Thank you!

Just found a small issue with the logic, incoming commit a few minutes to make it even faster.

https://github.com/ibhagwan/fzf-lua/commit/9454bcbad98654d8a4dc88a06d15985bd53acd1f changes the logic of the skip to be faster (not a string compare), and also increases the delay to 100ms to match how the native fzf preview works which  according to this uses a 100ms delay

Thank you! 100ms delay looks better. Should I test/check anything else?

Thank you! 100ms delay looks better. Should I test/check anything else?

Not ATM, I'm currently working on fixing the binary test, if you want I'll alert you here so you can test if after.

https://github.com/ibhagwan/fzf-lua/commit/510aca8658a954e152bd5e97cdad4fd6b09b7ea7 restores binary test for the preview, shouldn't affect performance at all but you're welcome to test and let me know if it does :-)

Hmmmm... With delay = 100, of course, there is no performance affect, but i tried with delay = 0 to test real performance, and... Found that enabling binary checking have huge performance affect (I'm comparing commits 9454bcbad98654d8a4dc88a06d15985bd53acd1f and 510aca8658a954e152bd5e97cdad4fd6b09b7ea7). I tried to disable syntax highlighting by only commenting this lines https://github.com/ibhagwan/fzf-lua/blob/510aca8658a954e152bd5e97cdad4fd6b09b7ea7/lua/fzf-lua/previewer/builtin.lua#L280-L289 (not sure how it clear), and tried to test again: disabled binary checking vs new binary checking (perl -B). My conclusion is that with enabled syntax highlighting, binary checking have huge performance affect, but with disabled syntax highlighting I can't say that I see difference between disabled and enabled binary checking.
About preview rotation: can't imagine when it can be used, but I'm not fan of beauty, so maybe for someone it can be useful:D.
P.S. now i go to sleep, so please don't wait me for answer :D. Sorry

Hmmmm... With delay = 100, of course, there is no performance affect, but i tried with delay = 0 to test real performance, and... Found that enabling binary checking have huge performance affect (I'm comparing commits 9454bcb and 510aca8). I tried to disable syntax highlighting by only commenting this lines

You didn't need to comment any lines to disable syntax highlighting, you can set previewers.builtin.syntax = false.

disabled binary checking vs new binary checking (perl -B). My conclusion is that with enabled syntax highlighting, binary checking have huge performance affect, but with disabled syntax highlighting I can't say that I see difference between disabled and enabled binary checking.

I'll try and check why there's a connection when I have more time, in any event I don't see this as an issue as I don't see any practical use to disabling the delay, given that it works fine with the 100ms delay it's safe to leave this issue for now.

P.S. now i go to sleep, so please don't wait me for answer :D. Sorry

Good night!


README: Add TMA section

This PR introduces a brief section describing TMA files added after merging with download.01.org/perfmon.
https://github.com/intel/perfmon/issues/17

Merging since we reviewed this change ahead of time. Thanks.


Convert copyright symbols to Unicode

Closes #313
This changes the encoding of the copyright symbol from ISO-8859 (aka Latin-1) to Unicode UTF-8. This is generally the only high-ASCII symbol used in the source files, and hence the only symbol with a distinct binary encoding between ISO-8859 and UTF-8.

I assume that's the only problem symbol. I'm not quite sure of a way to check.


Why is updates updating all records?

I'm doing:
db.Model(&user).Updates(map[string]interface{}{"name": "hello", "age": 18, "actived": false})
and it seems to be updating all the records instead of only one, completely ignoring the primary key in the user struct.
Why is this doing this? Bug maybe? And how do I resolve this?

@jinzhu

Made another issue to be more specific on my particular issue. https://github.com/jinzhu/gorm/issues/1661


Broken cursor on roles endpoint

When querying a hotspot's roles endpoint, the cursor doesn't advance. For example, I'm querying /hotspots/:address/roles?filter_types=assert_location_v2, getting empty data and a cursor, using the cursor, and getting the same response with the same cursor. This seems to happen if the transaction in question was awhile ago. It works if querying a hotspot with a recent assert location txn, but querying one with assert locations in the past produces this cursor bug.

@allenan have an example of a hotspot that exhibits this, please?

bump @allenan

Think I dm’d one to you

On Apr 19, 2022, at 8:48 PM, Marc Nijdam @.***> wrote:

bump @allenan
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Think I dm’d one to you
…

ah yeah thanks for the reminder


Refactor cache invalidation after form completion to use generic event bus

Describe the feature request.
A generic event bus implementation has been added as part of ticket #2265.
The purposed of this ticket is to refactor the current implementation that handles invalidation of cache after form completion to use the generic event bus.
Acceptance criteria

[x] When a family is removed, it should not appear on the household register
[x]  When a patient is removed, it should not appear on the patient register

Area path

Navigate to HouseHold register
Click on one family
Click on Remove Family on the household profile overflow menu
Fill out and save the Remove Family questionnaire
Navigate back to the HouseHold register
The removed family should not appear on the register

Implementation plan (For Engineers)

[x]  Add a QuestionnaireSubmission event in the Appevent class
[x]  Check whether questionnaireConfig.refreshContent is true in AppMainActivity.onSubmitQuestionnaire. Trigger a QuestionnaireSubmission event using the event bus.
[x]  Subcribe to the event SharedFlow provided by the EventBus and filter events of type RefreshCache in RegisterFragment.onViewCreated
[x]  When the RefreshCache event is received invoke registerViewModel.retrieveRegisterUiState with a clearCache value of true

Following discussions with @ellykits @f-odhiambo, we saw the need for refactoring AppMainActivity.onSubmitQuestionnaire into 2 events instead of the existing livedata components which are questionnaireSubmissionLiveData and dataRefreshLivedata.
This tickets handles the refactor for dataRefreshLivedata.

One of the use-cases for event management as outlined in the event management discussion is Redirecting to different screens.  An example of this would be redirecting the user to the family register after a family has been removed. The current implementation redirects the user to the household profile.
@ellykits @dubdabasoduba it would be prudent to have a discussion about the different use cases that would need to be handled in addition to how configurability would be approached

Following discussions with @ellykits @f-odhiambo, we saw the need for refactoring AppMainActivity.onSubmitQuestionnaire into 2 events instead of the existing livedata components which are questionnaireSubmissionLiveData and dataRefreshLivedata. This tickets handles the refactor for dataRefreshLivedata.
A ticket for the questionnaireSubmissionLiveData refactor will be added here

The ticket for the questionnaireSubmissionLiveData refactor has been added here


allow phpunit ^5.0

I made a similar PR for PHPUnit-5 support before I looked to see if a previous one existed.
https://github.com/php-mock/php-mock-phpunit/pull/2
You will need PHP v5.6 for PHPUnit-5

Guys thank you for your PRs. I'm currently waiting to get an internet
connection
into my new apartment. As soon as that's set up, I'll have a look into
that.
Markus

Thank you very much for this PR. Although this PR is older I'll go for PR#2 as it is more comprehensive.


Update text

👷 Deploy Preview for fancy-puffpuff-df775f processing.

Name
Link

🔨 Latest commit
15c6ecbaa8b5af6604c921f16bcc197d3f140a27

🔍 Latest deploy log
https://app.netlify.com/sites/fancy-puffpuff-df775f/deploys/64cecb21acd47000088fed18


UI error: sollet.io implies private key requirement on logout where no private key was presented/saved and is not required during restore/login

I have currently lost all tokens stored in sollet wallet. Partial funds appear during restore process but only the first account is presented on login. I have tried a few UI combinations trying to reaccess the wallet and I notice that on logging out the following message appears.
Delete Mnemonic & Log Out
You will not be able to recover the current accounts without the seed phrase, and the account private key. This action will delete all current accounts from your browser.

To prevent loss of funds, please ensure you have the seed phrase and the private key for all current accounts. You can view it by selecting "Export Mnemonic" in the user menu.

I never stored a private key and I dont have one only a seed phrase. When I log out and log back in only a seed phrase is asked for and no private key. Is this change of functionality possibly responsible or linked to my loss of tokens?

Instructions here imply that I can completely restore a wallet and its accounts from the seed phrase. This conflicts with the advice given on logout which implies i need account keys.
https://frontierprotocols.com/beginners-guide-to-sollet-wallet/#How-to-restore-an-existing-Sollet-Wallet


Does this framework support SFT?

Hi! MegaBlocks isn't a standalone training framework, but it's relatively easy to use from any framework. We use Megatron-LM and have a fork of it with MegaBlocks support. You could also use MegaBlocks from another framework like HuggingFace, for example.

Do you have SFT scripts? And Hyperparameters that you used to fine-tune the instruct version of your model? It would mean the world for the OS community!


Assign the name gzclient to the gazebo_ros client node

Fixes #187
Tested multiple start/stop viz scenarios. Ensured that simulated robots respond to auto/manual mode and that  they still collect cubes with/without viz.

This issue has been resolved in BCLab-UNM/SwarmBaseCode-ROS#189https://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/189.
On Jul 11, 2018, at 4:01 PM, Will Vining <notifications<EMAIL_ADDRESS>wrote:
@wfvininghttps://github.com/wfvining requested your review on: BCLab-UNM/SwarmBaseCode-ROS#189https://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/189 Assign the name gzclient to the gazebo_ros client node.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://github.com/BCLab-UNM/SwarmBaseCode-ROS/pull/189#event-1729030810, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADw5EybU6oDZ8xE4WP3IOPcOrEvLH3ooks5uFnWugaJpZM4VL6f-.


Updates for EOmaps v6.0

require matplotlib instead of matplotlib-base since QT is now an integral part

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


More network info

Issue Type

[ ] Bug
[x] Feature Request
[ ] Question

Problem and possible solution
Any chance the other details from here could be added to the output of networkInterfaces?
root@Devon:/mnt/user/code/api# ethtool bond0
Settings for bond0:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes
root@Devon:/mnt/user/code/api# dmesg | grep bond0
[   34.442583] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[   34.442585] 8021q: adding VLAN 0 to HW filter on device bond0
[   34.508774] bond0: Enslaving eth0 as a backup interface with a down link
[   34.559816] bond0: Enslaving eth1 as a backup interface with a down link
[   34.609775] bond0: Enslaving eth2 as a backup interface with a down link
[   34.659764] bond0: Enslaving eth3 as a backup interface with a down link
[   34.696179] device bond0 entered promiscuous mode
[   34.696201] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[   34.696203] 8021q: adding VLAN 0 to HW filter on device bond0
[   34.696231] br0: port 1(bond0) entered blocking state
[   34.696233] br0: port 1(bond0) entered disabled state
[   38.335111] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
[   38.335115] bond0: making interface eth0 the new active one
[   38.335204] bond0: first active interface up!
[   38.335238] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex
[   38.335249] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[   38.335293] br0: port 1(bond0) entered blocking state
[   38.335295] br0: port 1(bond0) entered forwarding state
[   38.439165] bond0: link status definitely up for interface eth2, 1000 Mbps full duplex
[   38.439184] bond0: link status definitely up for interface eth3, 1000 Mbps full duplex
root@Devon:/mnt/user/code/api# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: bc:30:5b:d3:b7:44
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: bc:30:5b:d3:b7:46
Slave queue ID: 0

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: bc:30:5b:d3:b7:48
Slave queue ID: 0

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: bc:30:5b:d3:b7:4a
Slave queue ID: 0

Currently this is all that's returned on that same machine.
> [ { iface: 'lo',
    ip4: '<IP_ADDRESS>',
    ip6: '::1',
    mac: '',
    internal: true },
  { iface: 'br0',
    ip4: '<IP_ADDRESS>',
    ip6: 'fe80::9c1a:22ff:feb7:887f',
    mac: 'bc:30:5b:d3:b7:44',
    internal: false },
  { iface: 'bond0',
    ip4: '',
    ip6: 'fe80::be30:5bff:fed3:b744',
    mac: 'bc:30:5b:d3:b7:44',
    internal: false },
  { iface: 'vnet0',
    ip4: '',
    ip6: 'fe80::fc54:ff:fef8:2c23',
    mac: 'fe:54:00:f8:2c:23',
    internal: false } ]

Will start to work on this tomorrow.

@OmgImAlexis : i will add the following information to networkInterfaces() (linux):

operstate
type (wireless / wired / virtual connection)
duplex
mtu
speed
carrierChanges (# changes operstate since startup)

Anything else you would like to see?

@sebhildebrandt I can't think of anything else, those all look good. 👍

Should work now. Version 4.0.0 published


Feature/aws nuke doc gen

Proposed changes
Created tool and added to make documentation target to refresh documentation of what services are supported by the Optum fork of AWS Nuke that is being used. See the tools/awsnukedocgen/README.md for details.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (changes to code, which do not change application behavior)

Checklist

[x] I have filled out this PR template
[x] I have read the CONTRIBUTING doc
[x] I have added automated tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (README.md, inline comments, etc.)
[ ] I have updated the CHANGELOG.md under a ## next release, with a short summary of my changes

Relevant Links

Further comments

I was able to run make documentation and generate the docs successfully 👍


php artisan migrate Error

Getting an error with the php artisan migrate command after the lastest update

Application In Production!     *

Do you really wish to run this command? y
PHP Parse error:  syntax error, unexpected 'return' (T_RETURN), expecting function (T_FUNCTION) in /var/www/TechnicSolder/app/libraries/MinecraftUtils.php on line 84
Not sure what to do here.

Running the command with sudo returns this:
PHP Parse error:  syntax error, unexpected 'return' (T_RETURN), expecting function (T_FUNCTION) in /var/www/TechnicSolder/app/libraries/MinecraftUtils.php on line 84
<!doctype html>

Error 500 - Internal Server Error


✨[Feature Request]: Want to enhance hover effect of social icons in login/signup

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add colors of respective logos when they are hovered
Before :
https://github.com/Anishkagupta04/RAPIDOC-HEALTHCARE-WEBSITE-/assets/162733812/1cc7ade3-6a62-4468-82c0-cdc078a1089f
I want to make it like this:
https://github.com/Anishkagupta04/RAPIDOC-HEALTHCARE-WEBSITE-/assets/162733812/60ce2fab-6d00-48ad-90be-3eca8992c13e
Use Case
It will help in improving UI of website
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04 I want to work on this issue , Please assign it to me

As I see , someone has already done it , I am sorry for being late on creating my PR , I am closing it


Fatal error: Call to unimplemented native function newrelic_notice_error_intern

Fatal error: Call to unimplemented native function newrelic_notice_error_intern()
After installation with:
HipHop VM 3.5.0
hhvm-newrelic-ext on master (commit https://github.com/chregu/hhvm-newrelic-ext/commit/c8ac2767fdd729d78e8f96519fe69c6842b9cef0)

upgrading to VM 3.6.1 does the trick


[tables] A field in the metadata table tables stored by fe is incorrect. Procedure

Feature request
Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

alter table add columb a int;
but , update_time is null or no change and after input data update_time is update

i hope can be when alter  table and update_time is latest


Bugbear extend-immutable-calls with import alias does not work

from fastapi.openapi.models import OAuthFlows as OAuthFlowsModel

def okay_alias(model=OAuthFlowsModel()):
    ...

[tool.ruff]
select = ["B008"]

[tool.ruff.flake8-bugbear]
extend-immutable-calls = ["fastapi.openapi.models.OAuthFlows"]

Thanks for the fix.


fix(docs): correction document description

Signed-off-by: coolmian<EMAIL_ADDRESS>Goals:

...
...
[ ] check and update documentation, if required. See guide

#834

Codecov Report
Base: 59.97% // Head: 30.75% // Decreases project coverage by -29.21% :warning:

Coverage data is based on head (c5c201b) compared to base (7ddbb87).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #834       +/-   ##
===========================================
- Coverage   59.97%   30.75%   -29.22%
===========================================
  Files         138      138
  Lines        7040     7040
===========================================
- Hits         4222     2165     -2057
- Misses       2818     4875     +2057

Flag
Coverage Δ

docarray
30.75% <ø> (-29.22%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

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

Thanks for you contribution !


reload dots

I am using the next functions:
func dotMarker(colorOnDayView dayView: CVCalendarDayView) -> [UIColor]
func dotMarker(shouldMoveOnHighlightingOnDayView dayView: CVCalendarDayView) -> Bool
func dotMarker(shouldShowOnDayView dayView: CVCalendarDayView) -> Bool
those functions are calling when the calendar show up. is it possible to calling it again like a restart or refresh?
Best!

yes u can by adding dayView.setupDotMarker() in method
public func refreshPresentedMonth() {
for weekV in presentedMonthView.weekViews {
for dayView in weekV.dayViews {
removeCircleLabel(dayView)
removeDotViews(dayView)
dayView.preliminarySetup()
dayView.supplementarySetup()
dayView.setupDotMarker()
}
}
}

Please see the referenced PR for further reference.


Executions stored in Database

I've created a database to store all executions. For now it is a leveldb database but this can be changed in the future if needed. The purpose of this PR is really to not store any execution state in memory to avoid huge memory consumption.

this one has some conflicts that needs to be resolved

I've done some update like splitting the database part (and put it in the database package) and also have the execution package that only manage the business logic related to the execution object. The responsibility to save this execution is done directly in the api package.
Waiting more feedbacks on that

I changed slightly the current implementation, now the hash is not calculated on the execution date but based on an eventID, executions should always be executed based on an event and every events should have an unique identifier. For now we generate the unique Id only based on an UUID but with decentralized services this should be the ID of the event (like the transaction hash on ethereum for example)

I changed slightly the current implementation, now the hash is not calculated on the execution date but based on an eventID, executions should always be executed based on an event and every events should have an unique identifier. For now we generate the unique Id only based on an UUID but with decentralized services this should be the ID of the event (like the transaction hash on ethereum for example)

I don't get these changes. Why are we complicating unique id generation? To me, we can create and set execution.Execution.ID with a randomly generated uuid inside execution.New() or execution.Save(). Why do we need to generate a hash over execution.Execution data structure? We're not looking for uniqueness of executions. The only thing needed is a random unique id for identifying each execution.

We actually need "uniqueness of executions". When we have the distributed version of MESG, the execution will be created by one node but all other nodes should be able to reproduce the same id based on the same data to ensure that they are verifying/executing the exact same execution. For now it's not mandatory to use a hash but it will be and it doesn't add much complexity, we already have the exact same principle for services for the same reason.


Separate user-specific holographic remoting settings to avoid polluting VCS'

Describe the bug
On OpenXR and Unity 2020, holographic remoting settings seem to be stored in Assets/XR/Settings/Open XR Package Settings.asset. This includes the IP address under m_remoteHostName, and whether it is enabled or not. By nature, these settings are user-specific, meaning that in a team with multiple developers with different local networks, local changes will keep showing up in Git, but also overwrite settings unless special care is taken.
Because this file seems to contain other important settings as well, it doesn't seem possible to ignore it entirely.
To reproduce

Use the MRTK with Unity 2020, OpenXR, and Git.
Modify the OpenXR remoting settings in Unity.
Observe them being changed in Assets/XR/Settings/Open XR Package Settings.asset.
Observe Git changes being logged.

Expected behavior
These specific settings are either in a separate file that can be fully ignored, or, preferably, somewhere in the new UserSettings top-level Unity folder, which can be ignored as a whole and contains settings specific to the user.
Your setup (please complete the following information)

Unity Version: 2020.3.11f1
MRTK Version 2.7.0

Target platform (please complete the following information)

HoloLens 2

This is a great callout! I'll bring this back to our Mixed Reality OpenXR Plugin workstream and figure it out.

This has been updated in the Mixed Reality OpenXR Plugin but hasn't yet been released. I'll update this thread when the next release comes out.

@NoTuxNoBux Sorry for not updating sooner: this shipped September 7th in the 1.0.3 release. Thanks for the suggestion!


Unable to Login with AAD w/MFA anymore!

Issue Type: Bug
I am suddenly unable to login to my azure sql databases using Azure Active Directory with MFA. I cannot add an account, It tells me I need to search for azure cloud in settings - I've tried that and it does not exist. I've tried to remove my MFA account but I don't see how I can. I would clear my cache but I don't know where this is cached. Would like to reset azure data studio settings and start clean but whenever I uninstall and install, it remembers everything... not working!
Azure Data Studio version: azuredatastudio 1.33.1 (0b9ef714c823d662815f441aec4a94eaa21940f8, 2021-11-04T17:45:15.872Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 1805)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.73GB (23.27GB free)

Process Argv

Screen Reader
no

VM
67%

Extensions: none

I was also experiencing this issue. However, I was able to resolve it by explicitly removing my account then adding it again. In order to remove the account @SashaRisner, you need to click on the person icon above the settings wheel which will bring up your linked accounts. Then just click on the X next to the account. I hope this helps!

@SashaRisner please try the suggestion that @slaymaker1907 has provided, and if it still doesn't work, please let us know.

Appreciate the suggestion but it did not work. I tried everything in the UI to delete my account but it kept 'remembering' the configuration. I ended up physically deleting the folder azuredatastudio under %userprofile%\AppData\Roaming\ and that finally fixed it.


Initiate French Localization Team

This issue is to initiate a new l10n Team
Please only use this template for submitting a new l10n team initiation requests.
See https://github.com/cncf/glossary/blob/main/LOCALIZATION.md for basic requirements for a new l10n team.

(1) The language and language code for l10n
Find localization's two-letter language code from ISO 639-1 standard.

Language name : French
Language two-letter code : fr

(2) List of volunteers
Name and GitHub Username for each l10n volunteer. Add [A] to make them approvers.

[A]  Christophe Sauthier (@huats )
[A] Flavien Hardy ( @fydrah )
[A] Ludovic Logiou ( @Krast76 )

(Note) Next actions from maintainers

Create a new development branch for the l10n. (ex: dev-ko)
Update codeowners to add l10n contents approvers.
Add a new label for the language.

Hi @huats
I created #glossary-localization-french channel in the CNCF Slack.
Please join and invite volunteers :)

Regarding dev-fr development branch,
I can create dev-fr branch immediately. But, since we expect a lot of changes in main branch soon, we'd better to postpone create dev-fr until #922 . So, please wait :)
In the meantime, you can discuss how to operate French localization team :)

lang/fr is the label for French ! ;)
https://github.com/cncf/glossary/labels/lang%2Ffr

Terrific. Thanks a lot for your help and actions.
We will then wait for the creation of the  dev-fr branch.

Hi @huats I created #glossary-localization-french channel in the CNCF Slack. Please join and invite volunteers :)

Good evening Natives :)
I would love to join the (glossary) French translation team as a first step into CNCF projects t9n path... Would you please send me an invitation for the Slack channel?
Looking forward to discussing and hopefully collaborating with the team :)

Hi @silopolis,
You do not need to be invited, you have to register there : https://communityinviter.com/apps/cloud-native/cncf (I hope this is the right link)

Hey @Krast76 🙂
I can't create an account because gmail.com is not in the list of allowed domains 😢

You do not need to be invited, you have to register there :
https://communityinviter.com/apps/cloud-native/cncf (I hope this is the
right link)

Yey, that's one!
Invitation request sent...
Thanks a lot @Krast76 👍🙏


Simple way to handle/create required promises internally

Instead of create an object and then filter by avalable options from
object keys, we can use an array and resolve a promise for limit: 0
option

Released in v5.0.1

There was something wrong with this commit, or perhaps #89 that caused v5.0.1 to break.  Perhaps you can look at #73 and #97


ctx.StrokePolygon consumes all memory until killed by OS

I've found a  bug related to #388  (I think).  This time lineDash is not zero.
import pixie

let image = newImage(200, 200)
image.fill(rgba(255, 255, 255, 255))

let ctx = newContext(image)

<EMAIL_ADDRESS>ctx.strokePolygon(vec2(0.0, 0.0), 0.0, 0)

This has exactly the same behaviour as in #388: consumes memory until killed by the OS.  I've looked at the code for context.StrokePolygon and paths.strokePolygon and I can't see why it happens.  The code looks right to me; with sides == 0 nothing should be added to the path.

This ctx.strokePolygon(vec2(0.0, 0.0), 0.0, 0) produces a degenerate / invalid path (a polygon with 0 sides does not exist). I'll add a check + exception for this.

Added the check in tagged release 4.0.2


Added pt_BR translation

Created pt_BR.ts locale file
Added ptBR as an language option

Created pt_BR.ts locale file
Added ptBR as an language option

Coverage increased (+0.1%) to 28.011% when pulling 880e431acb93e2e6571528839415ab2be00ec43b on arthuraraujo:Translation-pt_BR into 79334d67a2ffb60996c7100ef05720f4bdb4a128 on react-component:master.


Change ProjectionIndex for ref_tail_addr to UINT_MAX.

This is necessary to disambiguate the tail elements from
ref_element_addr field zero.
In preparation for adding the AccessPath utility.

@swift-ci test

@swift-ci benchmark

Performance: -O
Code size: -O
Performance: -Osize
Code size: -Osize
Performance: -Onone
Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB

Build failed
Swift Test Linux Platform
Git Sha - eae677b75132b6404998906995858102531f88b6

Can you add a specific SIL example to the commit of where this would cause a problem?

in the commit message.

Folding this into a larger PR


wit-bindgen: 0.13.0 -> 0.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/wit-bindgen/versions.
meta.description for wit-bindgen is: A language binding generator for WebAssembly interface types
meta.homepage for wit-bindgen is: https://github.com/bytecodealliance/wit-bindgen
Updates performed

Rust version 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.14.0 with grep in /nix/store/nnm42wlpr3j26ai002w5h2pxzc7wphrz-wit-bindgen-0.14.0
found 0.14.0 in filename of file in /nix/store/nnm42wlpr3j26ai002w5h2pxzc7wphrz-wit-bindgen-0.14.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
wit-bindgen

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nnm42wlpr3j26ai002w5h2pxzc7wphrz-wit-bindgen-0.14.0 \
  --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 wit-bindgen https://github.com/r-ryantm/nixpkgs/archive/23c92a19a342ce5203569e59997a66f0436c2968.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/23c92a19a342ce5203569e59997a66f0436c2968#wit-bindgen

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nnm42wlpr3j26ai002w5h2pxzc7wphrz-wit-bindgen-0.14.0
ls -la /nix/store/nnm42wlpr3j26ai002w5h2pxzc7wphrz-wit-bindgen-0.14.0/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:

wit-bindgen

Maintainer pings
cc @xrelkd for testing.

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

1 package built:

wit-bindgen


Dougservicequotas

this commit has several new legos around redshift queries and the AWS secret manager
There is also one edit to an existing lego as it was missing a library

A few things that were repetitive-

@beartype is added at runtime so we can remove it from the actual code , this just makes the code cleaner i guess
the jsonx file is a bug I think so since we don't need it in our lego's folder

The logic seems okay to me. Thanks


iOS11 cannot launch VMs (UTM 2.0+)

Describe the issue
iOS11 cannot launch VMs by using UTM 2.0+. It works by using earlier versions.
Configuration

UTM Version: UTM2.0+
OS Version: iOS11.1.1
Device Model: iPad2017 (A9)
Is it jailbroken (name jailbreak used)?  unc0ver
How did you install UTM?  Developer ID

https://user-images.githubusercontent.com/61855011/128636933-3c4df1e5-db23-4fa2-92fd-c423daa6c43a.mov

@ty-yqs is this v2.0 or v2.2.0? Also please attach a crash log.

My bad. It is working now (I restarted my device)


The components was not imported in demo code.

Added an importation for use the alert controller on line 52.
Short description of what this resolves:
The example code did not include an import statement for use the component.
Changes proposed in this pull request:

Add an import statement.

Ionic Version: 2.x
Fixes: #11567

Thanks :)


Simple profiling infractructure

Allow integration test to collect profiling information
Add an analysis script kavm/src/profiling/__main__.py
Update README with a profiling example

@geo2a @tothtamas28
Just happen to browsing this PR list. Wanted to add a note of info in case it wasn't well known. We have a gh runner with a label called performance -- if you would like to have a workflow that runs on this runner to create a baseline for performance/profiling please feel free to use. Let me know if you need any help setting up with it.


$channel->members remains empty in text-channels

Environment

PHP Version:

7.4.11

DiscordPHP Version:

dev-master

Describe the bug
$channel->members remains empty in text-channels
To Reproduce
Steps to reproduce the behavior:
$discord->on('message', function ($message) {
    $message->reply('This channel has '.$message->channel->members->count().' members.');
});

Expected behavior
Show a number higher then 0
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
We kinda fixed this for voice channels that had the same issue before.

looks like $channel->members only applies to VOICE Channels as per DM discussion with david, closing


Fix 193 and other things

Resolve #193

Codecov Report
Patch coverage: 70.00% and project coverage change: -0.13% :warning:

Comparison is base (ede3d9d) 80.90% compared to head (1bee3d7) 80.78%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #197      +/-   ##
==========================================
- Coverage   80.90%   80.78%   -0.13%
==========================================
  Files          13       13
  Lines        1011     1020       +9
==========================================
+ Hits          818      824       +6
- Misses        193      196       +3

Files Changed
Coverage Δ

lightshow/database.py
88.38% <62.50%> (-1.48%)
:arrow_down:

lightshow/pymatgen_utils.py
100.00% <100.00%> (ø)

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

@FCMeng Oh my god the fix worked. I'm gonna merge and prep for a new release 😁


control.defaults function in UMD builds

Describe the bug
We are still using the UMD build rather than ES modules, and it seems that in recent builds, the ol.control.defaults() function is wrapped into an additional defaults object - i.e., ol.control.defaults.defaults()
To Reproduce

Build from the source using npm run build-full
Load the resulting build/full/ol.js file from a script
ol.control.defaults is an object containing a single defaults() function

Expected behavior
In previous versions, the defaults() function was available from ol.control

See See https://github.com/openlayers/openlayers/issues/14020


Redmi Tab - FaceUnlock didnt work properly

After investigation, we found that "manager's" part like isFaceFeatureSupport or hasEnrolledFaces  work properly, but service binding are broken on Redmi Tab/AOS14
Investigation required, cause it seems like general mechanism remains, but Service implementation was changed

Redmi Tab/AOS 14 support FaceUnlock and hardware/enrollment detection works as expected, but binding to the miui.service.FaceService fails. Fix applied to prevent false positive detection on such devices

Unexpectedly, FaceUnlock back to work on Redmi Tab.
Probably need to implement some "temporary unavailable" state machine for this device


[Brackets auto-update Windows] Once the product is installed, the finish dialogue does not comes up.

Description
Once the product is installed, the finish dialogue does not comes up.
Steps to Reproduce

Run brackets installer for 1.13.
Once the installation is complete, installer dialogue disappears. There is no finish dialogue.

Expected behavior: Finish dialogue should come once the installation is done.
Actual behavior: Once the product is installed, the finish dialogue does not comes up.
Versions
Windows 10 64 Bit
Release 1.13 build 1.13.0-17624

I noticed when I installed Brackets a couple weeks ago that the finish dialogue did come up, but it was nearly pushed off of the left side of my screen. Perhaps it is a positioning issue? I am unsure if that is helpful to you while testing. I am also running the Windows 64-bit 1.13 release.

@Shieke I guess you are running brackets 1.12.
Could you please confirm ?

Please validate this with the latest changes and builds. Also, this issue should be assigned to RE as it is an installer change. @ayushrathi15 Please assign accordingly.

@ayushrathi15 I'm unable to repro this in 1.13.0-17665, which is the latest autoupdate build.
Could you please check this build?

Verified on Build 1.13.0-17674.


Add '--all-targets' and '--all-features' params to Clippy

Codecov Report

Merging #218 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #218   +/-   ##
=======================================
  Coverage   84.31%   84.31%
=======================================
  Files          12       12
  Lines         542      542
=======================================
  Hits          457      457
  Misses         85       85

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 b6e69f0...374ce58. Read the comment docs.


Add Simplified Chinese translation.

Contribution Type: new plugin
Link to Intent to Implement:
Link to Bug:
This pull request affects the following areas:

[ ] Front-End
[ ] Builder
[ ] Build Plugins

In raising this pull request, I confirm the following (please check boxes):

[x] I have read and understood the contributing guidelines?
[x] I have checked that another pull request for this purpose does not exist.
[x] I have considered, and confirmed that this submission will be valuable to others.
[x] I have created or updated the relevant documentation for this change on the PHPCI Wiki.
[ ] Do the PHPCI tests pass?

Detailed description of change:
Add Simplified Chinese translation.

I've just merged another pull request w/ a Chinese translation. If you could please look at and make tweaks to that translation it would be much appreciated!


Multiple machine cluster

At the moment Legion provisions k8s on a single AWS machine which is a problem from many perspectives:

Master must not be collocated with pods for reliability reasons
Build and runtime must not be collocated due reliability and security reasons

We need to adjust our provisioning scripts to use at least 3 machine groups: masters, build, and runtimes.

Assigning @alexander-semenets as he is working on kops based deployment implementation.


patch-package doesn't work with pnpm

What's going on?
patch-package doesn't work with pnpm.

Steps to reproduce

ignite a new project
patch a node_module
run patch-package

Result:
**ERROR** No package-lock.json, npm-shrinkwrap.json, or yarn.lock file.

You must use either npm@>=5, yarn, or npm-shrinkwrap to manage this project's
dependencies.

npx ignite-cli doctor results:
System
  platform           win32

  arch               x64

  cpu                12 cores       Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  directory          WeavixMobile   C:\git\WeavixMobile

JavaScript (and globally-installed packages)
  node                  16.13.1                                   C:\Program Files\nodejs\node.EXE
  npm                   8.1.2                                     C:\Program Files\nodejs\npm.CMD
    @angular/cli        13.1.2

    @vue/cli            5.0.1

    corepack            0.10.0

    mongodb-realm-cli   2.4.1

    node-gyp            8.4.1

    npm                 8.1.2

    pnpm                6.32.4

    yarn                1.22.17

  yarn                  1.22.17                                   C:\Program Files\nodejs\yarn.CMD
    node-gyp            8.4.1

$
                        <no pnpm global package info available>
$

Ignite
  ignite-cli         7.10.8       C:\Users\wades\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\.bin\ignite.CMD
  ignite src         build        C:\Users\wades\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\ignite-cli\build

Android
  java               17.0.1       C:\Program Files\Common Files\Oracle\Java\javapath\java.EXE
  android home       -            C:\Users\wades\AppData\Local\Android\Sdk

@boldwade thank you very much for logging this issue. This seems to be an issue with patch-package rather than Ignite. Please keep an eye out on their repo for the fix (I found this issue logged recently) and we will be sure to have Ignite updated to support it. Thanks again!


mux: ending readLoop packetio.Buffer error the agent is closed

I set up broadcast-box on a public server in a docker container using the provided docker-compose.yaml.
Ports 80 and 443 are exposed so that the web server obtains a certificate.
It works as expected and the web site shows the broadcast box banner.
However, publishing a stream to the broadcast box from OBS fails.
The log of the broadcast-box docker container reads:
2024/04/20 20:48:32 Loading `.env.production`
NETWORK_TEST_ON_START is enabled. If the test fails Broadcast Box will exit.
See the README for how to debug or disable NETWORK_TEST_ON_START
2024/04/20 20:48:32 Running HTTP Server at `:8080`
Network Test passed.
Have fun using Broadcast Box.
mux ERROR: 2024/04/20 20:48:37 mux: ending readLoop packetio.Buffer error the agent is closed

Hey @rosch100

Does this happen even if you broadcast from web?
What platform are you running the server on?
Can you try running with PION_LOG_TRACE=all and putting the logs in a gist?

Also if you get a chance we have a discord and happy to help on that also!

Hi @rosch100
Thanks for filing this. If this is still an issue I am here to help

Sorry for the delay. Here is the requested info:
The error shows a few seconds after starting the docker container. It is not possible to broadcast from web, since the server stops too soon.
The server runs on docker in MS Azure on a Ubuntu 24 server. I also tried using another provider (Ionos in Germany) with the same problem.
broadcast-box runs behind a nginx reverse proxy for HTTP traffic and has UPD 8080 exposed. The nginx proxy also takes care of HTTPS encryption.
2024/07/08 14:18:34 Loading `.env.production` 2024/07/08 14:18:34 Running HTTP Server at `:8080` NETWORK_TEST_ON_START is enabled. If the test fails Broadcast Box will exit. See the README for how to debug or disable NETWORK_TEST_ON_START ice TRACE: 14:18:39.981988 agent.go:443: Unset selected candidate pair pc INFO: 2024/07/08 14:18:39 signaling state changed to have-local-offer pc INFO: 2024/07/08 14:18:39 signaling state changed to have-remote-offer ice TRACE: 14:18:39.986374 agent.go:443: Unset selected candidate pair pc INFO: 2024/07/08 14:18:39 signaling state changed to stable ice DEBUG: 14:18:39.986597 agent.go:320: Started agent: isControlling? false, remoteUfrag: "kexFMlwenwlWqOXm", remotePwd: "jJDVFPIPMsBjPgovBPMiccbmYYZTLnFW" ice INFO: 2024/07/08 14:18:39 Setting new connection state: Checking pc INFO: 2024/07/08 14:18:39 ICE connection state changed: checking pc INFO: 2024/07/08 14:18:39 peer connection state changed: connecting ice TRACE: 14:18:39.986649 agent.go:461: Pinging all candidates ice WARNING: 2024/07/08 14:18:39 Failed to ping without candidate pairs. Connection is not possible yet. ice TRACE: 14:18:39.986709 agent.go:461: Pinging all candidates ice WARNING: 2024/07/08 14:18:39 Failed to ping without candidate pairs. Connection is not possible yet. pc INFO: 2024/07/08 14:18:39 signaling state changed to stable ice DEBUG: 14:18:39.988963 agent.go:320: Started agent: isControlling? true, remoteUfrag: "QetKVJmSeVsfGfrA", remotePwd: "SHuKrdpILYUJRVqUTCDLUZFzhloyChlS" ice INFO: 2024/07/08 14:18:39 Setting new connection state: Checking pc INFO: 2024/07/08 14:18:39 ICE connection state changed: checking pc INFO: 2024/07/08 14:18:39 peer connection state changed: connecting ice TRACE: 14:18:39.989324 agent.go:461: Pinging all candidates ice TRACE: 14:18:39.989845 agent.go:895: Ping STUN from udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.990710 agent.go:1010: Inbound STUN (Request) from my.public.ip:47052 to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080), useCandidate: false ice DEBUG: 14:18:39.990897 agent.go:1043: Adding a new peer-reflexive candidate: my.public.ip:47052 ice DEBUG: 14:18:39.990975 udp_mux.go:268: Registered ::ffff:my.public.ip for QetKVJmSeVsfGfrA ice TRACE: 14:18:39.991098 agent.go:895: Ping STUN from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) ice TRACE: 14:18:39.991259 agent.go:461: Pinging all candidates ice TRACE: 14:18:39.991531 agent.go:895: Ping STUN from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) ice TRACE: 14:18:39.991492 selection.go:138: Inbound STUN (SuccessResponse) from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) ice TRACE: 14:18:39.991874 selection.go:148: Found valid candidate pair: prio<PHONE_NUMBER>652587007 (local, prio<PHONE_NUMBER>) udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) <-> udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: false, nominateOnBindingSuccess: false ice TRACE: 14:18:39.991986 agent.go:1010: Inbound STUN (Request) from my.public.ip:8080 to udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052), useCandidate: false ice TRACE: 14:18:39.992162 selection.go:109: The candidate (udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052), udp4 host my.public.ip:8080 (resolved: my.public.ip:8080)) is the best candidate available, marking it as nominated ice TRACE: 14:18:39.992407 selection.go:90: Ping STUN (nominate candidate pair) from udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.992346 selection.go:229: Inbound STUN (SuccessResponse) from udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.992525 selection.go:239: Found valid candidate pair: prio<PHONE_NUMBER>314175487 (local, prio<PHONE_NUMBER>) udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) <-> udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: false, nominateOnBindingSuccess: false ice TRACE: 14:18:39.992649 agent.go:895: Ping STUN from udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.992878 agent.go:1010: Inbound STUN (Request) from my.public.ip:8080 to udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052), useCandidate: false ice TRACE: 14:18:39.993381 agent.go:1010: Inbound STUN (Request) from my.public.ip:47052 to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080), useCandidate: true ice TRACE: 14:18:39.993402 agent.go:449: Set selected candidate pair: prio<PHONE_NUMBER>314175487 (local, prio<PHONE_NUMBER>) udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) <-> udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: true, nominateOnBindingSuccess: false ice INFO: 2024/07/08 14:18:39 Setting new connection state: Connected ice TRACE: 14:18:39.993484 agent.go:895: Ping STUN from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) pc INFO: 2024/07/08 14:18:39 ICE connection state changed: connected dtls TRACE: 14:18:39.993595 handshaker.go:176: [handshake:client] Flight 1: Preparing dtls TRACE: 14:18:39.993615 handshaker.go:176: [handshake:client] Flight 1: Sending dtls TRACE: 14:18:39.993626 conn.go:416: [handshake:client] -> ClientHello (epoch: 0, seq: 0) dtls TRACE: 14:18:39.993672 handshaker.go:176: [handshake:client] Flight 1: Waiting ice TRACE: 14:18:39.993797 selection.go:138: Inbound STUN (SuccessResponse) from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) ice TRACE: 14:18:39.993964 selection.go:148: Found valid candidate pair: prio<PHONE_NUMBER>652587007 (local, prio<PHONE_NUMBER>) udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) <-> udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: false, nominateOnBindingSuccess: false ice TRACE: 14:18:39.994014 agent.go:449: Set selected candidate pair: prio<PHONE_NUMBER>652587007 (local, prio<PHONE_NUMBER>) udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052) <-> udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: true, nominateOnBindingSuccess: false ice INFO: 2024/07/08 14:18:39 Setting new connection state: Connected ice TRACE: 14:18:39.994138 agent.go:1010: Inbound STUN (Request) from my.public.ip:8080 to udp4 host <IP_ADDRESS>:47052 (resolved: <IP_ADDRESS>:47052), useCandidate: false ice TRACE: 14:18:39.993936 selection.go:229: Inbound STUN (SuccessResponse) from udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.994306 selection.go:239: Found valid candidate pair: prio<PHONE_NUMBER>314175487 (local, prio<PHONE_NUMBER>) udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) <-> udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: true, nominateOnBindingSuccess: false pc INFO: 2024/07/08 14:18:39 ICE connection state changed: connected ice INFO: 2024/07/08 14:18:39 Setting new connection state: Closed pc INFO: 2024/07/08 14:18:39 peer connection state changed: closed Network Test passed. Have fun using Broadcast Box. pc WARNING: 2024/07/08 14:18:39 Failed to start manager: InvalidStateError: attempted to start DTLSTransport that is not in new state: closed pc WARNING: 2024/07/08 14:18:39 undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet pc INFO: 2024/07/08 14:18:39 ICE connection state changed: closed mux ERROR: 2024/07/08 14:18:39 mux: ending readLoop packetio.Buffer error the agent is closed pc WARNING: 2024/07/08 14:18:39 undeclaredMediaProcessor failed to open SrtpSession: the DTLS transport has not started yet ice TRACE: 14:18:39.996221 selection.go:229: Inbound STUN (SuccessResponse) from udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) to udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) ice TRACE: 14:18:39.996240 selection.go:239: Found valid candidate pair: prio<PHONE_NUMBER>314175487 (local, prio<PHONE_NUMBER>) udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) <-> udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) (remote, prio<PHONE_NUMBER>), state: succeeded, nominated: true, nominateOnBindingSuccess: false ice TRACE: 14:18:40.193189 selection.go:181: Checking keepalive sender_interceptor WARNING: 2024/07/08 14:18:40 failed sending: the DTLS transport has not started yet sender_interceptor WARNING: 2024/07/08 14:18:40 failed sending: the DTLS transport has not started yet dtls TRACE: 14:18:40.993938 handshaker.go:176: [handshake:client] Flight 1: Sending dtls TRACE: 14:18:40.994094 conn.go:416: [handshake:client] -> ClientHello (epoch: 0, seq: 0) dtls TRACE: 14:18:40.994433 handshaker.go:176: [handshake:client] Flight 1: Waiting sender_interceptor WARNING: 2024/07/08 14:18:41 failed sending: the DTLS transport has not started yet sender_interceptor WARNING: 2024/07/08 14:18:41 failed sending: the DTLS transport has not started yet dtls TRACE: 14:18:41.995099 handshaker.go:176: [handshake:client] Flight 1: Sending dtls TRACE: 14:18:41.995130 conn.go:416: [handshake:client] -> ClientHello (epoch: 0, seq: 0) dtls TRACE: 14:18:41.995311 handshaker.go:176: [handshake:client] Flight 1: Waiting ice TRACE: 14:18:42.193968 selection.go:181: Checking keepalive ice TRACE: 14:18:42.194022 agent.go:895: Ping STUN from udp4 host my.public.ip:8080 (resolved: my.public.ip:8080) to udp4 prflx my.public.ip:47052 related :0 (resolved: my.public.ip:47052) sender_interceptor WARNING: 2024/07/08 14:18:42 failed sending: the DTLS transport has not started yet sender_interceptor WARNING: 2024/07/08 14:18:42 failed sending: the DTLS transport has not started yet dtls TRACE: 14:18:42.995618 handshaker.go:176: [handshake:client] Flight 1: Sending dtls TRACE: 14:18:42.995651 conn.go:416: [handshake:client] -> ClientHello (epoch: 0, seq: 0) dtls TRACE: 14:18:42.995763 handshaker.go:176: [handshake:client] Flight 1: Waiting sender_interceptor WARNING: 2024/07/08 14:18:43 failed sending: the DTLS transport has not started yet sender_interceptor WARNING: 2024/07/08 14:18:43 failed sending: the DTLS transport has not started yet : : ice TRACE: 14:19:10.205047 agent.go:443: Unset selected candidate pair ice INFO: 2024/07/08 14:19:10 Setting new connection state: Failed ice TRACE: 14:19:10.205087 selection.go:181: Checking keepalive pc INFO: 2024/07/08 14:19:10 ICE connection state changed: failed dtls TRACE: 14:19:10.205175 conn.go:936: handshake timeouts - closing underline connection pc INFO: 2024/07/08 14:19:10 Closing PeerConnection from DTLS CloseNotify pc INFO: 2024/07/08 14:19:10 peer connection state changed: closed pc WARNING: 2024/07/08 14:19:10 Failed to start manager: handshake error: context deadline exceeded pc WARNING: 2024/07/08 14:19:10 undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet pc WARNING: 2024/07/08 14:19:10 undeclaredMediaProcessor failed to open SrtpSession: the DTLS transport has not started yet ice INFO: 2024/07/08 14:19:10 Setting new connection state: Closed pc INFO: 2024/07/08 14:19:10 ICE connection state changed: closed


branch/tag field is inaccessible after issue creation

Gitea version (or commit ref): 1.9.5
Git version: 2.17.1
Operating system: Ubuntu 18.04
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

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

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

Log gist:

Description
Hi,
when I create a new issue and didn't choose a branch/tag, but want to add it afterwards, the field is deactivated. All other fields are accessible.
Is this by purpose?
Thanks,
Maarten

Duplicate of #5476


I want a solution to fix the package if possible because my project is stuck

I installed the package, but it shows me a problem and asks me to communicate with those who maintain the package to solve the problem because I could not connect to the database, export and send information
......
warn Package react-native-sqlite-storage contains invalid configuration: "dependency.platforms.ios.project" is not allowed. Please verify it's properly linked using "react-native config" command and contact the package maintainers about this.

it looks like the project is dead

The package is fine for me. ignore the warning and search previous Issue before creating a new one.
#527 and #522
comment at there and please close this.

I installed the package, but it shows me a problem and asks me to communicate with those who maintain the package to solve the problem because I could not connect to the database, export and send information
...... warn Package react-native-sqlite-storage contains invalid configuration: "dependency.platforms.ios.project" is not allowed. Please verify it's properly linked using "react-native config" command and contact the package maintainers about this.

I'm getting the same error warning and react sqlite is not working is showing me the object null issue error


clean up before unmounting

will I need to destroy the dragula instance - before unmounting.
thanks

How did you do that?


Help with Koppen Geiger calculation

Hi pastclim team,
I am new to the pastclim package, and keen to try and use it to calculate palaeo Koppen Geiger classifications using the package and data from the CHELSA-TraCE21K data repository.
In the pastclim example, I see you use call in the data 'Temp', and 'Prec' as three dimentional arrays. I am interested in looking at particular periods, for example 5-4.5ka (as an example), is it simplest for me to produce new raster files for each monthly average, and then group them as a 12-layer raster stack, which I then call into the function. Would this work?
Also I know that the precip value refers to averange monthly precipitation, but what metric is Temp? Is it average monthly temp, min or max? I cannot see Mean Monthly Temp available on CHELSA-TraCE21K - only max and min.
Many thanks,
Catherine

Yes, you can use the function on SpatRaster objects, so what you suggest should work.
For mean temperature, you can simply use (tmin+tmax)/2; that's what was used in the original publication to compute bio1, which is the mean annual temperature.

@CatherineBuckland is this issue resolved?


refactor: remove _ prefix from public functions

Obsolete as work on this project is discontinued. Will reopen this PR if needed.


Create classes to encapsulate every kind of NFO XML node

Create classes to encapsulate every kind of NFO XML node

Copied the Kodi wiki contents into Google Sheets and leveraged spreadsheet formulas to generate XML, which I then autoconverted to XML serializable c# classes.

Copied the Kodi wiki contents into Google Sheets and leveraged spreadsheet formulas to generate XML, which I then autoconverted to XML serializable c# classes.


[Business Rules Manager] [Web Component] Progress bar keeps on running after server error has occurred

Description:
When loading a page, if the server goes down, no suitable error message is given. The progress bar keeps on loading.
Suggested Labels:
Type/Bug
Suggested Assignees:
@senthuran16
Affected Product Version:
wso2sp-4.2.0-alpha
Steps to reproduce:

Start dashboard run time and go  to the Business Rules Manager
Login using admin & admin ontinue until selecting a template group
Stop the server
Click on the home button
The progress circle will keep showing, even though server is down

Closing ths issue, since fixed in https://github.com/wso2/carbon-analytics/pull/1285


Vite re-optimizes dependencies although they did not change

Describe the bug
When releasing an application with semantic versioning and without changing its dependencies, the version property of one of the lock file formats (case spotted for package-lock.json) gets updated, causing the generated _metadata.json to mismatch, and thus trigger an unnecessary dependency rebuild.
Reproduction
Just follow these steps:

npm init @vitejs/app
npm install
npm version major
vite --clearScreen false
npm version minor
vite --clearScreen false should display Pre-bundling dependencies

System Info
Not needed.

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

diff the whole .lock file for just compare  whether the project version is the only thing changed seems unworthy
the  trade off between the version compare(parse .lock file) and just let esbuild take his advantage to bundle 👀
I want to listen from the member

I don't think it's worth adding a parsing step just for this edge case.
It makes this particular case fast but would slow everything else down.

Indeed, I should provide some stats. We are comparing milliseconds (parse and compare single file in current process) to seconds (spawn process, parse and compile several files).

I also don't think it's worth an extra parsing step for this edge case. There are multiple lock file formats besides package-lock.json, like yarn's and pnpm's. It would be hard to get it right. I think this is an ok tradeoff for now. Closing due to lack of discussion too.