NPCLib Console Spam and extreme server lag with 20+ players.

Describe the bug
The console gets spammed and the server lags to nearly a halt with 30+ players.
This gets spammed around 20 times in 1 single second.
[20:21:58 ERROR]: NPCLib Error in onPacketInAsync(). java.lang.NullPointerException
NPCLib usage option
3
NPCLib JAR name
Shaded: 2.7.2-SNAPSHOT
Server version
CraftBukkit version git-TacoSpigot-"95870a93" (MC: 1.8.8) (Implementing API version 1.8.8-R0.2-SNAPSHOT)
To Reproduce
Steps to reproduce the behavior:

Place some NPC's with NPCHitEvent etc, then let 30+ people on the server and the console should be spammed.

Expected behavior
NO lag, and errors.
Screenshots
https://imgur.com/a/K6DvBaI
Additional context
We want to make a server using NPC's and the NPCLib(rary) and as of now this is not possible if we have more than 25/30 players.

Hi, thanks for creating this issue ticket!
Can you try to track down the full stack trace? This is something I can't reproduce on my development server. The fact that something is null doesn't help me at all, I need a little bit more information.
You can get the full stack trace to print when the error is printed less often (also when the error just started printing).

We get the same as https://github.com/MinecraftLibraries/NPCLib/issues/89, we are running 2.7.2 which had a fix for that issue but it came back.

Ah, well in that case. This issue is a duplicate of #89. Closing issue.
I'd like to continue this conversation in issue #89.


Does not seem to work with Python3?

Collecting shippo==1.2.2 (from -r requirements.txt (line 38))
  Using cached shippo-1.2.2.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/z_/t4j3gq21121d0sj_wd4wqbn80000gn/T/pip-build-baoixqds/shippo/setup.py", line 5, in <module>
        from version import VERSION
    ImportError: No module named 'version'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/z_/t4j3gq21121d0sj_wd4wqbn80000gn/T/pip-build-baoixqds/shippo/

There also doesn't seem to be a Python3 binary on pypa.

Same thing just happened to me.

#25 should fix it. Someone please accept the PR.

Thanks for merging @simonkreuz! If you can make a release that'd be awesome.

Thanks for the pull request, @danqing. We've pushed a new release.


Fix a typo in README.md

Just a typo fix.
Hope you're having a great day! :)

You'll make it into the authors file next time one of us pushes a PR


README: Add dark/light mode compatibility

Checklist

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[ ] I've added relevant tests for my contribution
[ ] I've updated the documentation and/or added correct docstrings
[x] I've assigned a reviewer
[ ] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Description

Currently, our logo appeared terrible for users with the dark mode setting,
eg
Light mode (OLD)

Dark mode (OLD)

With this PR, the logo will alternate between two PNGs (with transparent backgrounds) for light/dark mode, the only difference between the two being the text color (black/white).
Light mode (NEW)

Dark mode (NEW)

I also replaced the U-net figure with a new napari GUI GIF we introduced in our RTD in a recent PR (#850)
Linked issues

Resolves #480

coverage: 93.854%. remained the same
when pulling ce27802dcc11b11f6e1529a665f76d5114f40c3a on mb/480
into 4a5fc6c9898437c98287d1797c8d0d084fac1b00 on master.


Are Flows and PowerApps which are not connected to CDS affected during the upgrade?

Will Flows (and PowerApps) not connected to CDS continue to run normally during the migration?
If non-CDS Flows do not run during the migration, will they be triggered after migration is complete, or will those runs be missed?

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

ID: 08497d1c-0527-bd2a-3500-d2df3b5b9736
Version Independent ID: 08cb8ab9-9610-fdcd-ae24-c40b3fc1e484
Content: Upgrade and verify your apps and flows
Content Source: common-data-service/upgradecds/upgrade-verify-apps-flows.md
Service: commondataservice
GitHub Login: @JimDaly
Microsoft Alias: jdaly

Flows and PowerApps (now called canvas apps) not connected to the previous version of CDS will not be affected during the upgrade. They should continue to run uninterrupted during the migration.


Bug in DataViewer filter for numbers

Environment data

VS Code version: 1.39.1
Extension version: 2019.10.41019 (8 October 2019)
Python version: Anaconda for Python 3.7.3 64-bit

Expected behaviour
Entering e.g. "3" in colum filter for integer numpy array should result in e.g. rows with -3, -3, 3, 13, 23.
Actual behaviour
Displayed are the rows e. g. -3, -3, 0, 0, 3, 13, 23. This is a bug since zeros should be filtered. With floating point arrays the filtering seem not to work at all when expecting string pattern matching. All rows are filtered for any digits.
Screenshot

Another remark on the screenshot: It would be nice, if the sorting would be stable. For several identical lines the other lines should stay in the order of the last sorted column (here the last sorted column was the line index which is now disordered for equal elements in column 1)

Thanks for the bug.
Do you have an example of the floating point arrays not working? I think your saying it's just doing a string filter (which is what I'd expect from anything other than a number)

It would be nice, if the sorting would be stable
Multiple column sorting will probably be done by the user picking columns while holding down the control key.

The problem with the 3 matching is weird. That only happens on a column that isn't identified as a number (which it looks like you have based on the left justification)
But the zero isn't actually a value in the data as far as I can tell. It must be matching null.

It seems there is value matching for float columns and pattern matching for integers (except the zero). Here are figures for float tables:

It should be rather the opposite. I would more prefer pattern matching (i.e. sub-pattern matching) for both types. In case numbers should be treated by their values it would make sense if you could enter intervals like "3.1 - 5.5".

It's only pattern matching for integers if your data doesn't specify the column type. Value matching should be the default for everything we think is a number.
You can also use > and < signs for value matching. We have yet to do ranges, but that's a good suggestion.

That's a usefull feature with > and <. I didn't know. In this case I am fine with value matching for floats.
Floats then do not have any bug. Especially zeros do not match with every pattern. That's only a problem for integers.


Update 743-Network-Delay-Time.py

t = max(t, w1) was a redundant check since we're already updating the weights while pushing to the minHeap. Solution has been verified and runs perfectly on LeetCode.

File(s) Modified: 743. Network Delay Time
Language(s) Used: Python
Submission URL: _https://leetcode.com/submissions/detail/807466104/_

Thanks, @palashsharma891!


Named arguments: Strip '_' from parameter name.

This change is

Decided not to do this (at least not right now).


Reduce shape for per group weight calibration

Hello!
Am I right that when we quantize weights with some group size, we expect calibration stats (min and max) to be the same within each group? If so, why the reduce_shape is set to -1 here:
https://github.com/OpenGVLab/OmniQuant/blob/main/quantize/quantizer.py#L130C28-L130C28
x = x.reshape(-1,self.group_size)

# some code omitted

reduce_shape = [-1]
xmin = x.amin(reduce_shape, keepdim=True)
xmax =  x.amax(reduce_shape, keepdim=True)

Should not the reduce_shape param be equal to 0 if x is a weight matrix? if, on the other hand, x is an input tensor, than reduce_shape should indeed be -1?
P.S. If some kind of fix is really needed, I would be happy to try make a pull request :slightly_smiling_face:

Ah, okay! It appears I did not quite understand the meaning of "group_size". I thought that it means the size in terms of groups (i.e. number of groups), not the size of one group. Then everything is indeed alright. Sorry for disturbance)


fix(mlx-lm): apply lora layer doesn't update the lora weights

@awni, I found this while working on the moe model stuff. I noticed that the lora weight doesn't apply to the gate and the weight distribution is almost identical to uniform. So, I dug a bit into the mlx-lm lora code and found out that we only replace the linear layer but never update the lora weight from adapters.

So this means fuse was broken right? I should do a patch release probably

So this means fuse was broken right? I should do a patch release probably

Yeah, I believe it breaks the current fuse in mlx-lm. However, I don't think many people are using mlx-lm lora yet. so not sure if we need an urgent patch release or not.

Thanks! This helped me.


Performance and correctness fixes for Arrays

Makes arrays Int-sized. This significantly improves iteration performance.
New implementation of copy with bounds checks
Adds fromArray and toArray to convert from and to scala.Array.
Adds clone method
More tests

:+1:


Release 0.4.0

Might make sense to release 0.4.0 by now, it's been a long time since 0.3.0 with more than 100 commits since then.

Funny you, specifically, should mention it, because I've got a fix for your https://github.com/lightbend/migration-manager/issues/201 cooking. 😄

Much appreciated :) So, maybe now would be a good time for a new release? ;)

How about now? :-D

I'd be happy to look into this but I don't have write access here it seems

Thanks, @raboof.  Admin access granted.  Let me know if you need anything else or need me to do anything.
Sorry I've left this pending for so long.

Done!


Mismatch between reported and reproduced ACC and SIM in Formality dataset

Hi :)
I am currently working on a paper in style transfer and was trying to reproduce the scores reported in Table 1 of your paper. I am getting roughly the same scores, except for ACC and SIM in the GYAFC Entertainment_Music split.
The following is the reported scores - reproduced scores from us:

Model
reported ACC
reproduced ACC
reported SIM
reproduced SIM

STRAP 0.0
67.7
71.3
72.5
60.9

STRAP 0.6
70.7
73.5
69.9
58.7

STRAP 0.9
76.8
79.3
62.9
52.4

A general trend is that the reproduces scores have higher ACC and lower SIM.
The scores for "reproduced SIM" were averaged after comparing with four .ref* files in GYAFC/Entertainment_Music/test.
Qualitatively examining your results, one possible reason for such discrepancy might be the existence of &apos, &quot, and &amp in your output. Should I manually replace these with ', ", and & and proceed evaluating? Were the current reported scores measured after such replacement? FYI, the example outputs in this repo also contains &apos, &quot, and &amp.
I think it is fair to replace them to compare your outputs with other baselines and ours, but I didn't want to edit any output of yours without your permission.
I also measured SIM with the original input just in case, and got scores closer to your reported SIM. We got 71.4, 68.3, 60.4 for STRAP 0.0, 0.6, 0.9. It should be that the reported scores are from comparison with the reference sentences, NOT the original sentences, but it was little weird that the reported scores tend to represent SIM with original sentences instead.
If both are not the case, can you tell me what could be the possible reason, and whether I should report my reproduced scores or the previously reported scores for ACC and SIM in my paper?
I would really appreciate any guidance. btw, awesome work, my coworkers and I were really inspired. Thanks in advance! :)

Hi @minniie thanks for reaching out! Are these reproduced numbers with the pretrained checkpoint, or with models you trained yourself using the scripts provided? If it's the latter, there could be some variation from run-to-run.
Another thing I wanted to check was whether you were using the evaluation script provided, which takes max SIM score (instead of average) over the provided four references at an instance level? You mentioned you took an average, but was that across instances only or references as well?

Hi, thank you so much for your reply.
First, we downloaded the pretrained checkpoint and used it only for inference.
We used the script in https://github.com/martiansideofthemoon/style-transfer-paraphrase/blob/master/style_paraphrase/evaluation/scripts/evaluate_formality.sh, and only changed line 48 so that it takes the four .ref* files instead of the original input concatenated in reverse order, since it's not the correct reference for GYAFC dataset.
formality.log is the log file after running the above script, which gives weird scores at generated vs gold section. The reason for this is that unlike Shakespeare dataset, the two test sets in GYAFC are not parallel, thus cannot serve as references for each other.
After making our edit, our scores are in formality_after_edit.log. As you pointed out, we averaged the scores manually instead of taking the max SIM score. Taking the max, the scores are 71.46, 68.88, 61.71, which is still about one point lower than the reported scores but much closer than our average.

Hi, thanks for getting back..
I don't see much of a difference between the two log files, which part were you referring to? I agree line 48 doesn't make sense (since sizes of formal/informal are different) but the file created in line 48 is not used for evaluation (we use the ref* files instead).
Yes ~1% difference could be due to some preprocessing reason. p=0.6/0.9 can vary due to stochasticity, but p=0.0 should get you a number similar to that reported in paper. How did you create the data splits? If you created them on your own, I could send over preprocessed files which do some tokenization etc. (see point 3 here: https://github.com/martiansideofthemoon/style-transfer-paraphrase#datasets)

Hi,
Now that I look at the script more carefully, line 48 shouldn't be the issue. So sorry about that. My teammate actually ran the code and sent me the results, so I'd have to check with them if any other changes were made. But line 66 makes total sense to me, and I believe we're doing the same given the similar scores.
Also, we might have missed the part for asking you for the preprocessed dataset, so my teammate actually preprocessed it himself. The splits were the same as the original split in GYAFC, which comes with train/dev/test. But I agree there might be slight difference from bpe tokenization. Can you send the preprocessed files to<EMAIL_ADDRESS>?
Again, so sorry about our hastiness. We're kinda running on time and I wasn't careful enough to check everything perfectly. We'll try again once we receive the preprocessed files, and hopefully it solves the issue.

Oh no worries! I think the preprocessing will fix issues for p=0.0. Could you write me an email<EMAIL_ADDRESS>with a screenshot of the email from Joel Tetreault confirming you have access to GYAFC? I'll promptly send the preprocessed version after I get that.. (i know you probably do, but just following protocol since GYAFC is not publicly available)

Awesome! Just sent it :)

Awesome, sent you the dataset. I'm closing this issue for now, but feel free to re-open it if the issue persists.


PR: Rename plugins for simpler interface

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Renamed plugins for a simpler, less crowded interface.

Issue(s) Resolved

Fixes #9207
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
Juanis2112

@juanis2112, our tests are failing because here:
https://github.com/spyder-ide/spyder/blob/be98b086f95968fccc4e8dbe3f1140154c94a412/spyder/app/tests/test_mainwindow.py#L1668
we're looking for a plugin called "Static code analysis" instead of "Code analysis", which is the new name.

Thanks a lot @juanis2112!


How to find the optimal training model in tensorboard?

Could you please tell me how to choose the number of epochs with the best performance when viewing training process information in tensorboard? I encountered the following doubts during the actual operation: I trained for a total of 30 epochs. The relevant train and val indicators in tensorboard for the 14th epoch were worse than those for the 20th epoch, but the 14th epoch The evaluation result is the best among 30 epochs. What causes this?

OK, I got it, thank you very much for your reply.


Update to latest 1.16.5-R0.1-SNAPSHOT dependency.

This will break support for 1.14 and below.

Add minidev json dependency.
Remove use of travel agent.

I need this for some 5.0.0 PRs.

You should add respawning at the respawn anchor when updating to 1.16: https://github.com/Brokkonaut/Multiverse-Core/commit/126e005057c33e39da784ea2bcec863a71d620ac#diff-007320f3c3d7e7ef72ba8edfcf728c30ceb1e940504eff3378ea96f43cebe0e7R73

You should add respawning at the respawn anchor when updating to 1.16: Brokkonaut@126e005#diff-007320f3c3d7e7ef72ba8edfcf728c30ceb1e940504eff3378ea96f43cebe0e7R73

will be a separate PR


v2.2.x compilation fails on Ubuntu (with stock g++)

While installing the v2.2.x gem on my machine (Ubuntu 18.04-based, with stock g++), I get this error (edit):
linking shared-object sassc/libsass.so
lto1: fatal error: bytecode stream in file ‘c99func.o’ generated with LTO version 7.1 instead of the expected 6.0

On the same machine, compiling v2.1.0 succeeds.
Software versions:
$ g++ --version
g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
$ aptitude show libsass-dev | grep Version
Version: 3.4.8-1

I've traced back the problem to be the difference between gcc version I use (v8) and g++ (v7). I was mislead by the error, as I'm not a C/++ programmer. Closing, as it's a configuration problem.


TypeError: Cannot read property 'name' of undefined

speccy lint yaml_obj.yml --rules=test.rule
(node:50261) ExperimentalWarning: The http2 module is an experimental API.
Specification contains lint errors: 2
/usr/local/lib/node_modules/speccy/lint.js:58
${colors.yellow + pointer} ${colors.cyan} R: ${rule.name} ${colors.white} D: ${rule.description}
^
TypeError: Cannot read property 'name' of undefined
at lintResults.forEach.result (/usr/local/lib/node_modules/speccy/lint.js:58:53)
at Array.forEach ()
at formatLintResults (/usr/local/lib/node_modules/speccy/lint.js:54:17)
at validator.validate (/usr/local/lib/node_modules/speccy/lint.js:98:30)
at /usr/local/lib/node_modules/speccy/node_modules/call-me-maybe/index.js:13:28
at _combinedTickCallback (internal/process/next_tick.js:132:7)
at process._tickCallback (internal/process/next_tick.js:181:9)

Can you add the contents of your rule.yaml file, it looks like one or more rules are missing a name property.

I used the default rule file:
rules:

name: parameter-description
object: parameter
description: parameter objects should have a description
truthy: description
name: parameter-name-regex
object: parameter
disabled: true
description: parameter names should match RFC6570
pattern:
property: name
value: ''
name: operation-operationId
object: operation
description: operation should have an operationId
truthy: operationId
name: operation-summary-or-description
object: operation
description: operation should have summary or description
or:

summary
description

name: operation-tags
object: operation
description: operation should have non-empty tags array
truthy: tags
skip: isCallback
name: path-keys-no-trailing-slash
object: paths
description: paths should not end with a slash
notEndWith:
property: "$key"
value: "/"
name: server-trailing-slash
object: server
description: server url should not have a trailing slash
notEndWith:
property: url
value: "/"
name: openapi-tags
object: openapi
description: openapi object should have non-empty tags array
truthy: tags
name: openapi-tags-alphabetical
object: openapi
description: openapi object should have alphabetical tags
alphabetical:
properties: tags
keyedBy: name
name: reference-no-other-properties
object: reference
description: reference objects should only have a $ref property
truthy: "$ref"
properties: 1
name: example-value-or-externalValue
object: example
description: example should have either value or externalValue
xor:

value
externalValue

name: default-and-example-are-redundant
object: "*"
description: don't need to define an example if its exactly the same as your default
schema:
dependencies:
default:
properties:
example:
not:
const:
"$data": "1/default"
name: reference-components-regex
object: reference
disabled: true
description: reference components should all match regex ^[a-zA-Z0-9.-]+
pattern:
property: "$ref"
omit: "#"
split: "/"
value: "^[a-zA-Z0-9\.\-]+$"
name: no-script-tags-in-markdown
object: "*"
description: markdown descriptions should not contain

@MikeRalphson  Here is more info on this issues:
Looks like the results has some non object results like:
Specification contains lint errors: 4
Test string [ 'Anonymous requestBody: requestBody_definition',
'Anonymous requestBody: requestBody_message',
{ pointer: '#/info',
rule:
{ name: 'info-contact',
object: [Array],
description: 'info object should contain contact object',
truthy: [Array],
url: undefined },
ruleName: 'info-contact',
error:
{ AssertionError: expected Object {
this is causing the error , so on adding a if condition in formatLintResults function as below may fix the issue .
const formatLintResults = lintResults => {
console.log("Test string", lintResults)
let output = '';
lintResults.forEach(result => {
console.log("Test  results", result);
if (result.rule){
const { rule, error, pointer } = result;
        output += `
    ${colors.yellow + pointer} ${colors.cyan} R: ${rule.name} ${colors.white} D: ${rule.description}
    ${colors.reset + truncateLongMessages(error.message)}

    More information: https://speccy.io/rules/1-rulesets#${rule.name}
    `;

    }

});

return output;

}

This will be solved with my current PRs and in a next release of speccy. Please have a look at it when released.

This has been fixed in v0.11.0


[Update][Ease of Use] Community / Contrib Package

Community / Contrib Package
Chroma has common touch points which are contributed by the community. Currently, this is embedding functions, but in this set of features, may grow to include the chunker, re-ranker, as well as future data loaders.
This can make it unclear which features are supported and developed directly by the Chroma team, and which are exclusively community supported.
API Design
No change.
[Complexity] Subtask

[Low] Extracting community supported components int

Splitting up EF's is the first step: https://github.com/chroma-core/chroma/pull/2034


query returned wrong number of labels: 1, 0

exporter

https://github.com/wrouesnel/postgres_exporter
node_exporter

one timescale-prometheus - docker installed - latest
tow prometheus

prom-a one for collect
prom-b one for read by grafana

but query process_start_time_seconds will failed on prom-b, prom-a can execute correctly
remote_read: remote server http://<IP_ADDRESS>:9202/read returned HTTP status 500 Internal Server Error: query returned wrong number of labels: 1, 0

https://github.com/timescale/timescale-prometheus/blob/6693256251629559a609f9e7f56131d6107eba2f/pkg/pgmodel/sql_reader.go#L252
both node_exporter and postgres_exporter has process_start_time_seconds metric
error log
{
  "caller": "read.go:45",
  "err": "query returned wrong number of labels: 1, 0",
  "level": "warn",
  "msg": "Error executing query",
  "query": {
    "queries": [
      {
        "start_timestamp_ms":<PHONE_NUMBER>800,
        "end_timestamp_ms":<PHONE_NUMBER>800,
        "matchers": [
          { "name": "__name__", "value": "process_start_time_seconds" }
        ],
        "hints": {
          "step_ms": 14000,
          "start_ms":<PHONE_NUMBER>800,
          "end_ms":<PHONE_NUMBER>800
        }
      }
    ]
  },
  "storage": "PostgreSQL",
  "ts": "2020-08-08T10:03:53.854Z"
}

This should be fixed by PR #184

@wenerme This should be fixed in release 0.1.0-beta.2. Can you please confirm?

Works now.


[DNM] Placeholder for prototype

Signed-off-by: tabokie<EMAIL_ADDRESS>Used for building binary, please don't close it.
Release note
None

/release

/release

/release

/release

/release

/release

/release

/release

/release

/release

/test

/release

/run-build

/run-build

/run-build

/run-build

/release

/release

/run-build

/run-build

/run-build

/run-build

/run-build

/run-build

/run-build

/run-build

/release

/run-build-arm64 comment=true

/release

/release

/release

/release

/release

/release


Upgrade repository idp

-add repository
-add models
-refactore ccontrollers code

add requests
add passport credentials
add vuejs on frontend
add tests
edit migrations and factories

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ae0db27). Click here to learn what that means.
The diff coverage is 81.96%.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   72.35%
  Complexity        ?      198
=========================================
  Files             ?       49
  Lines             ?      651
  Branches          ?        0
=========================================
  Hits              ?      471
  Misses            ?      180
  Partials          ?        0

Impacted Files
Coverage Δ
Complexity Δ

app/Listeners/LogLoginListener.php
90.9% <ø> (ø)
3 <0> (?)

app/Events/LoginEvent.php
100% <ø> (ø)
3 <0> (?)

app/Models/Client.php
0% <0%> (ø)
1 <1> (?)

app/Http/Controllers/ClientRoleController.php
0% <0%> (ø)
2 <2> (?)

app/Http/Requests/LoginRequest.php
100% <100%> (ø)
2 <2> (?)

app/Http/Middleware/RedirectIfUnauthenticated.php
100% <100%> (ø)
2 <2> (?)

app/Repositories/BaseRepository.php
100% <100%> (ø)
1 <1> (?)

app/Http/Controllers/Manage/ProviderController.php
100% <100%> (ø)
6 <6> (?)

app/Http/Controllers/Manage/UserController.php
100% <100%> (ø)
8 <8> (?)

app/Providers/AuthServiceProvider.php
100% <100%> (ø)
1 <1> (?)

... and 28 more

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 ae0db27...1c10ac7. Read the comment docs.


Error while trying to build iOS Zoom SDK on iPhone Simulator

Followed All necessary steps to run on iPhone Sim :

unzipped zoom_sdk dev
gave camera and audio permissions
disabled bitcode

Uncategorized (Xcode): Command EmitSwiftModule failed with a nonzero exit code

Swift Compiler Error (Xcode): No such module 'MobileRTC'
/Users/admin/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_zoom_sdk-1.1.0+4/ios/Classes/SwiftFlutterZoomSdkPlugin.swift:2:7
2

Could not build the application for the simulator.
Error launching application on iPhone 13.

Same Issue here

Same issue

Same issue here

Same here 🙈

having same problem

I too am having the same issue if anyone can help please do.

iPhone Simulator will not work as of now

the same issue, anyone solved it ??

Was anyone able to solve this?


#2705 when generate a new dataset, add sequence for distinction

Description
Applying #2716  into 3.3.x branch.
Related Issue : #2705

run build
deploy to 2


\d:DomainName is not prepended to the username when using -sec-nla

When using service with NLA disabled, xfreerdp do not prepend the DomainName\ in front of the username.
In fact, I found no possible way to prepend the domain name. For instance, none of those 2 ways actually works:
xfreerdp -sec-nla /d:CompanyAD<EMAIL_ADDRESS>/v:rdpserver.mycompany.com
xfreerdp -sec-nla<EMAIL_ADDRESS>/v:rdpserver.mycompany.com
It connects to the login screen, but the CompanyAD\ is never prepended to the username and/or the logon domain is never provided.
Regards,

Please add some information, can not reproduce.
which versions are you useing?

Please add some information, can not reproduce.
which versions are you useing?

Hi,
This is FreeRDP version 2.2.0 (2.2.0)
Strange that you can't reproduce. I can try to provide a screenshot of the windows login screen after executing those 2 examples.

Hi,
This is FreeRDP version 2.2.0 (2.2.0)
Strange that you can't reproduce. I can try to provide a screenshot of the windows login screen after executing those 2 examples.

For instance, using the below command on my Windows10 Pro:
xfreerdp -sec-nla /cert:ignore /d:MyAD<EMAIL_ADDRESS>/v:<IP_ADDRESS>
provides:

The domain (MyAD) is not prepended to the username in the form MyAD\ nor taken as the domain name below the "Sign in to:"

For instance, using the below command on my Windows10 Pro:
xfreerdp -sec-nla /cert:ignore /d:MyAD<EMAIL_ADDRESS>/v:<IP_ADDRESS>
provides:

The domain (MyAD) is not prepended to the username in the form MyAD\ nor taken as the domain name below the "Sign in to:"

@Pivert thank you. Indeed, there was a bug fixed with https://github.com/FreeRDP/FreeRDP/pull/2051
can you try with nightly builds and check if that works for you>

Hi,
Tested on
This is FreeRDP version 3.0.0-dev (fab649a)
This is exactly the same problem & behaviour.

@Pivert please clarify, just tested the command line from above with my credentials against a windows 10 setup and it works as expected.

@Pivert ok, retried, and it looks windows 10 has some (strange) automation that strips the domain with certain conditions.
Try something like<EMAIL_ADDRESS>and it will always show correctly.

Thanks Akallabeth,
I did a try on the Windows10 I had the issue, and it does not seem to pass with this trick.
I do not have access to this PC any more, so I cannot try further. But it definitely seems to work in the above configuration, when the username contains an @


refactor: 💡 add attributes to improve querying in tests

Adding missing attributes to components as I find them while writing the BasicForm story test
✅ Closes: #149

I think this should be a fix commit so that these component changes get distributed to npm.
For example, if our QA automated testing team wanted to leverage these query selectors tomorrow, they wouldn't be able to because there's no new version of the code.

I think this should be a fix commit so that these component changes get distributed to npm.
For example, if our QA automated testing team wanted to leverage these query selectors tomorrow, they wouldn't be able to because there's no new version of the code.

Ah okay. Adding a new fix commit would trigger that, right?

I think this should be a fix commit so that these component changes get distributed to npm.
For example, if our QA automated testing team wanted to leverage these query selectors tomorrow, they wouldn't be able to because there's no new version of the code.

I think this should be a fix commit so that these component changes get distributed to npm.
For example, if our QA automated testing team wanted to leverage these query selectors tomorrow, they wouldn't be able to because there's no new version of the code.

Ah okay. Adding a new fix commit would trigger that, right?

Yep!

This is interesting stuff.  I would really like to learn more about the plan/direction we are going in for testing this project.  Maybe a team meeting would be a good place to outline the vision.

This is interesting stuff. I would really like to learn more about the plan/direction we are going in for testing this project. Maybe a team meeting would be a good place to outline the vision.

I've outlined some things in #148 and #117, but there are certainly more things to discuss

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Avoid void casts on serialization error

If I use microxrceddsgen, inside the serialization function, it discards errors. If there are errors serializing, I want that brought up to my application.
Furthermore, certain coding standards like MISRA explicitly forbid this, unless there is a comment  explaining why it's being discarded (MISRA C:2012 Rule 17.7).
Current Behavior:
bool ShapeType_serialize_topic(ucdrBuffer* writer, const ShapeType* topic)
{
    (void) ucdr_serialize_string(writer, topic->color);

    (void) ucdr_serialize_int32_t(writer, topic->x);

    (void) ucdr_serialize_int32_t(writer, topic->y);

    (void) ucdr_serialize_int32_t(writer, topic->shapesize);

    return !writer->error;
}

MISRA compliant Behavior:
bool ShapeType_serialize_topic(ucdrBuffer* writer, const ShapeType* topic)
{
    bool success = true;
    success &= ucdr_serialize_string(writer, topic->color);

    success &= ucdr_serialize_int32_t(writer, topic->x);

    success &= ucdr_serialize_int32_t(writer, topic->y);

    success &= ucdr_serialize_int32_t(writer, topic->shapesize);

    return success & (!writer->error);
}

I have a PR to submit that changes this. Let me know if you agree this is desirable behavior.

If there is any good way to write tests to check this new logic, let me know.

https://github.com/eProsima/Micro-XRCE-DDS-Gen/pull/46 merged. Closing


Internal: upgrade @playwright/test to 1.32.0

upgrading Playwright and associated packages

I don't have time to debug this. Abandoning for now


proposal: cmd/go: add -reproducible flag

There seems to be a growing number of flags required to get reproducible builds with Go (e.g. see https://github.com/golang/go/issues/51748). It’d be nice if there was -reproducible flag that would

Disable CGO_ENABLED and GO_EXTLINK_ENABLED by default, unless explicitly set via environment variables.
Default to -reproducible=true for go install. Currently there are some platforms (e.g. android) where Cgo is required, but those are usually cross-compiled so CGO_ENABLED must be set explicitly anyway.
Forbid setting -buildvcs=auto explicitly—there is no reason to set that if the goal is reproducible builds.
Default to -trimpath=true and -buildvcs=true flags, unless explicitly set via command line arguments or GOFLAGS environment variable.

Additionally, for -reproducible=true and -buildvcs=true, given a non-dirty VCS source tree of an example.com module, go build -reproducible should produce the same output as go install example.com@version-or-revision (even if the current revision was not pushed yet). Otherwise, if the tree is dirty, build should fail.
If go.mod contains replace and other directives that would cause go install to fail, go build should fail too with -reproducible=true.
Using VCS information to make go build reproducible against go install seems to be non-trivial to implement, so alternatively perhaps we can just set -buildvcs=false by default with -reproducible flag.

I think it could be confusing for a cmd/go flag like -reproducible to disable cgo.  Many people want reproducible builds and many program use cgo.  Having -reproducible disable cgo would be a confusing experience.

Cgo already must be enabled explicitly when cross-compiling. Setting up reproducible builds with C toolchain is already an explicit step since that relies heavily on the state of the host system (e.g. presence the system libraries), and I don’t think an extra step of setting an environment variable would be confusing for people that need reproducible builds with Cgo.
That said, on a second thought, that would only cause an issue with go install that under this proposal would have -reproducible=true (and hence Cgo disabled), and I’d like to retract this part.
This way, builds that have to be reproducible can run with GOFLAGS=-reproducible without changing any existing behavior in Go toolchain when the flag is not set.

I don't really see a point in having a flag that can have every setting it controls then be overridden by something else, it makes it harder to reason about which setting is actually taking effect, especially combined with setting flags in GOFLAGS.
And having a flag named like this but only getting you half of the way there (if you use CGo) seems worse than having no such flag to mislead you.

We're not going to make a -reproducible flag disable cgo. That's mixing two unrelated things.
At that point I don't see the difference between -reproducible and -trimpath.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

If -trimpath is the -reproducible flag, then the latter is a better name for it. We could likely deprecate the former and replace it with the latter.

/cc @bcmills for thoughts on renaming/aliasing/deprecating -trimpath to -reproducible?

I think -trimpath is the more appropriate word for what the flag does today.
Notably, it does not audit or stamp the versions of external C headers or libraries linked into the resulting binary, so using the same Go release to build a cgo-enabled binary with -trimpath on two different machines (or on one machine with intervening changes to system C libraries) does not necessarily reproduce the exact binary.
I think a -reproducible flag conceptually ought to error out if any of the other flags might result in a non-reproducible binary: so, for example, rather than disabling cgo implicitly, -reproducible might error out completely. But then I'm not sure how useful it would really be.

I agree with Bryan; Go has enough misconceptions as it stands today, and I can certainly see this one appearing in no time:

use the -reproducible flag to make your builds reproducible

It is a requirement to make reproducible builds possible, but it's not enough in many scenarios, and I imagine it will rarely be enough in most large projects.

I agree with @mvdan. The other piece of the puzzle that I think would be extremely valuable would be a debug mode that prints every input to the build ID. I'm in a thread on Twitter where developers were complaining about a "random" build ID causing Arch Linux reproducibility failures, and it would be useful to tell them "run it under -debug-build-id and check the diff" instead of a guessing game of what is causing the issue.

ensure that the cgo build is reproducible (toolchain, dependencies, etc), or disable cgo

But is there any testing on this part? Currently it seems like cgo is not tested and the ability to test them seems hard at best. Building delve under two chroots with CGO and the same flags produce different buildids which gets propagated to the buildid of the binary.
CGO is desirable because of binary hardening which is lacking in the main Go compiler.

The other piece of the puzzle that I think would be extremely valuable would be a debug mode that prints every input to the build ID.

I won't claim that the output is easy to read, but you get this by setting GODEBUG=gocachehash=1.

The above mentioned issue from twitter is LTO symbols having random numbers in their suffix. I tried adding -frandom-seed=0 a few places in the compiler but I haven't managed to get them deterministic :/
We should maybe document the current cases where Go is not reproducible?
Diffoscope output:

    λ something » diffoscope _pkg_.a repro.a
    --- _pkg_.a
    +++ repro.a
    ├── file list
    │ @@ -1,16 +1,16 @@
    │  ?rw-r--r--   0        0        0     2036 1970-01-01 00:00:00.000000 __.PKGDEF
    │  ?rw-r--r--   0        0        0    36887 1970-01-01 00:00:00.000000 _go_.o
    │  ?rw-r--r--   0        0        0     1096 1970-01-01 00:00:00.000000 asm_amd64.o
    │  ?rw-r--r--   0        0        0     2784 1970-01-01 00:00:00.000000 _x001.o
    │  ?rw-r--r--   0        0        0     2776 1970-01-01 00:00:00.000000 _x002.o
    │  ?rw-r--r--   0        0        0     4536 1970-01-01 00:00:00.000000 _x003.o
    │ -?rw-r--r--   0        0        0     7208 1970-01-01 00:00:00.000000 _x004.o
    │ +?rw-r--r--   0        0        0     7224 1970-01-01 00:00:00.000000 _x004.o
    │  ?rw-r--r--   0        0        0    14504 1970-01-01 00:00:00.000000 _x005.o
    │  ?rw-r--r--   0        0        0    10176 1970-01-01 00:00:00.000000 _x006.o
    │  ?rw-r--r--   0        0        0     6680 1970-01-01 00:00:00.000000 _x007.o
    │  ?rw-r--r--   0        0        0     4936 1970-01-01 00:00:00.000000 _x008.o
    │ -?rw-r--r--   0        0        0     8544 1970-01-01 00:00:00.000000 _x009.o
    │ +?rw-r--r--   0        0        0     8528 1970-01-01 00:00:00.000000 _x009.o
    │  ?rw-r--r--   0        0        0     4720 1970-01-01 00:00:00.000000 _x010.o
    │  ?rw-r--r--   0        0        0     7752 1970-01-01 00:00:00.000000 _x011.o
    │  ?rw-r--r--   0        0        0    16568 1970-01-01 00:00:00.000000 _x012.o
    │  ?rw-r--r--   0        0        0      864 1970-01-01 00:00:00.000000 _x013.o
    ├── __.PKGDEF
    │ @@ -1,16 +1,16 @@
    │  00000000: 676f 206f 626a 6563 7420 6c69 6e75 7820  go object linux
    │  00000010: 616d 6436 3420 676f 312e 3138 2e33 2058  amd64 go1.18.3 X
    │  00000020: 3a72 6567 6162 6977 7261 7070 6572 732c  :regabiwrappers,
    │  00000030: 7265 6761 6269 7265 666c 6563 742c 7265  regabireflect,re
    │  00000040: 6761 6269 6172 6773 2c70 6163 6572 7265  gabiargs,pacerre
    │  00000050: 6465 7369 676e 0a62 7569 6c64 2069 6420  design.build id
    │  00000060: 224b 325f 3375 582d 6e6e 4d59 657a 6748  "K2_3uX-nnMYezgH
    │ -00000070: 7677 3630 762f 484e 5645 6779 2d37 7a66  vw60v/HNVEgy-7zf
    │ -00000080: 6637 7162 5842 796b 6170 220a 0a0a 2424  f7qbXBykap"...$$
    │ +00000070: 7677 3630 762f 4539 4f4d 7252 7763 3236  vw60v/E9OMrRwc26
    │ +00000080: 7679 746f 4249 504f 3450 220a 0a0a 2424  vytoBIPO4P"...$$
    │  00000090: 420a 6902 8705 9309 2124 474f 524f 4f54  B.i.....!$GOROOT
    │  000000a0: 2f73 7263 2f72 756e 7469 6d65 2f63 676f  /src/runtime/cgo
    │  000000b0: 2f68 616e 646c 652e 676f 0556 616c 7565  /handle.go.Value
    │  000000c0: 0168 0648 616e 646c 6500 0644 656c 6574  .h.Handle..Delet
    │  000000d0: 6503 7e72 3001 7602 6f6b 034d 6170 0473  e.~r0.v.ok.Map.s
    │  000000e0: 796e 6304 4c6f 6164 0768 616e 646c 6573  ync.Load.handles
    │  000000f0: 1724 474f 524f 4f54 2f73 7263 2f73 796e  .$GOROOT/src/syn
    ├── _go_.o
    │ @@ -1,16 +1,16 @@
    │  00000000: 676f 206f 626a 6563 7420 6c69 6e75 7820  go object linux
    │  00000010: 616d 6436 3420 676f 312e 3138 2e33 2058  amd64 go1.18.3 X
    │  00000020: 3a72 6567 6162 6977 7261 7070 6572 732c  :regabiwrappers,
    │  00000030: 7265 6761 6269 7265 666c 6563 742c 7265  regabireflect,re
    │  00000040: 6761 6269 6172 6773 2c70 6163 6572 7265  gabiargs,pacerre
    │  00000050: 6465 7369 676e 0a62 7569 6c64 2069 6420  design.build id
    │  00000060: 224b 325f 3375 582d 6e6e 4d59 657a 6748  "K2_3uX-nnMYezgH
    │ -00000070: 7677 3630 762f 484e 5645 6779 2d37 7a66  vw60v/HNVEgy-7zf
    │ -00000080: 6637 7162 5842 796b 6170 220a 0a0a 2424  f7qbXBykap"...$$
    │ +00000070: 7677 3630 762f 4539 4f4d 7252 7763 3236  vw60v/E9OMrRwc26
    │ +00000080: 7679 746f 4249 504f 3450 220a 0a0a 2424  vytoBIPO4P"...$$
    │  00000090: 0a0a 2424 0a0a 0a24 2420 202f 2f20 6367  ..$$...$$  // cg
    │  000000a0: 6f0a 5b5b 2263 676f 5f65 7870 6f72 745f  o.[["cgo_export_
    │  000000b0: 7374 6174 6963 222c 2263 726f 7373 6361  static","crossca
    │  000000c0: 6c6c 3222 5d2c 5b22 6367 6f5f 6578 706f  ll2"],["cgo_expo
    │  000000d0: 7274 5f64 796e 616d 6963 222c 2263 726f  rt_dynamic","cro
    │  000000e0: 7373 6361 6c6c 3222 5d2c 5b22 6367 6f5f  sscall2"],["cgo_
    │  000000f0: 6578 706f 7274 5f73 7461 7469 6322 2c22  export_static","
    ├── _x001.o
    │ ├── readelf --wide --sections {}
    │ │ @@ -2,27 +2,27 @@
    │ │
    │ │  Section Headers:
    │ │    [Nr] Name              Type            Address          Off    Size   ES Flg Lk Inf Al
    │ │    [ 0]                   NULL<PHONE_NUMBER>000000<PHONE_NUMBER>00 00      0   0  0
    │ │    [ 1] .text             PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>00 00  AX  0   0  1
    │ │    [ 2] .data             PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>00 00  WA  0   0  1
    │ │    [ 3] .bss              NOBITS<PHONE_NUMBER>000000<PHONE_NUMBER>00 00  WA  0   0  1
    │ │ -  [ 4] .gnu.lto_.profile.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>0f 00   E  0   0  1
    │ │ -  [ 5] .gnu.lto_.icf.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 00004f 000011 00   E  0   0  1
    │ │ -  [ 6] .gnu.lto_.ipa_sra.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ -  [ 7] .gnu.lto_.inline.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ -  [ 8] .gnu.lto_.jmpfuncs.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ -  [ 9] .gnu.lto_.pureconst.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>0e 00   E  0   0  1
    │ │ -  [10] .gnu.lto_.ipa_modref.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000a1 000011 00   E  0   0  1
    │ │ -  [11] .gnu.lto_.lto.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000b2 000008 00   E  0   0  1
    │ │ -  [12] .gnu.lto_.symbol_nodes.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000ba 00000f 00   E  0   0  1
    │ │ -  [13] .gnu.lto_.refs.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000c9 00000e 00   E  0   0  1
    │ │ -  [14] .gnu.lto_.decls.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000d7 000026 00   E  0   0  1
    │ │ -  [15] .gnu.lto_.symtab.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000fd 000000 00   E  0   0  1
    │ │ -  [16] .gnu.lto_.ext_symtab.f64d60f5ec95f2ee PROGBITS<PHONE_NUMBER>000000 0000fd 000001 00   E  0   0  1
    │ │ +  [ 4] .gnu.lto_.profile.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>0f 00   E  0   0  1
    │ │ +  [ 5] .gnu.lto_.icf.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 00004f 000011 00   E  0   0  1
    │ │ +  [ 6] .gnu.lto_.ipa_sra.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ +  [ 7] .gnu.lto_.inline.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ +  [ 8] .gnu.lto_.jmpfuncs.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>11 00   E  0   0  1
    │ │ +  [ 9] .gnu.lto_.pureconst.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000<PHONE_NUMBER>0e 00   E  0   0  1
    │ │ +  [10] .gnu.lto_.ipa_modref.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000a1 000011 00   E  0   0  1
    │ │ +  [11] .gnu.lto_.lto.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000b2 000008 00   E  0   0  1
    │ │ +  [12] .gnu.lto_.symbol_nodes.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000ba 00000f 00   E  0   0  1
    │ │ +  [13] .gnu.lto_.refs.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000c9 00000e 00   E  0   0  1
    │ │ +  [14] .gnu.lto_.decls.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000d7 000026 00   E  0   0  1
    │ │ +  [15] .gnu.lto_.symtab.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000fd 000000 00   E  0   0  1
    │ │ +  [16] .gnu.lto_.ext_symtab.fd3e93c4e939fc22 PROGBITS<PHONE_NUMBER>000000 0000fd 000001 00   E  0   0  1
    │ │    [17] .gnu.lto_.opts    PROGBITS<PHONE_NUMBER>000000 0000fe 0000e5 00   E  0   0  1
    │ │    [18] .comment          PROGBITS<PHONE_NUMBER>000000 0001e3 000013 01  MS  0   0  1
    │ │    [19] .note.GNU-stack   PROGBITS<PHONE_NUMBER>000000 0001f6 000000 00      0   0  1
    │ │    [20] .note.gnu.property NOTE<PHONE_NUMBER>000000 0001f8 000050 00   A  0   0  8
    │ │    [21] .symtab           SYMTAB<PHONE_NUMBER>000000<PHONE_NUMBER>48 18     22   2  8
    │ │    [22] .strtab           STRTAB<PHONE_NUMBER>000000<PHONE_NUMBER>1e 00      0   0  1
    │ │    [23] .shstrtab         STRTAB<PHONE_NUMBER>000000 0002ae 00022d 00      0   0  1

No change in consensus, so declined.
— rsc for the proposal review group

It's fine to work on a doc (maybe a wiki page to start?) explaining the subtleties that go into a reproducible build.

This proposal is now closed, so I've opened https://github.com/golang/go/issues/53976 to track that.


Add global event handler window.onerror

As far as I can tell, there is no way to set the global event handler for window.onerror. The following code does nothing:
window.onerror = function() {
	console.log('Global Error!', arguments.length);
	return true;
};
throw new Error('TEST');

Would it be possible to add this functionality?

Technically speaking, that should be possible. We could wrap all event handling code in a try/catch and trigger an error event on window. We have to decide whether we want to support global error handlers. /cc @tbuschto

Instead of the Browser API on the global object, I'd rather provide an error event on the tabris object:
tabris.on('error', function(error) {
  // handle error
});

We can't provide the same parameters (source, lineno, colno) as the Browser API, but the message and stack properties are available on the error object.

Why a different API @ralfstx?  As @patbenatar mentioned if you can use the same browser API then the libraries from Rollbar/Airbrake/etc are drop-in installations instead of having to re-trigger them in the tabris.error listener.

@cookieguru We make some browser API available to allow for code re-use. However, Tabris.js is more a RequireJS environment than a browser and I don't think that simulating a complete browser environment would be a good direction. In particular, we should avoid polluting the global object (window === global).
It seems that the libraries you refer to can be used with Node.js, where there is no window.onerror as well (not even a window). Looking at Airbrake, delegating errors should be a one-liner:
tabris.on('error', err => airbrake.notify(err));


SQLPackage command is unable to connect Azure SQL Database

HI Team, i am trying to import data from onpremise folder to azure sql database using sql package command but its throwing me and error - *** Error importing database:Could not import package.
Unable to connect to master or target server 'pocdb'. You must have a user with the same password in master or target server 'pocdb'.
Below is my command.
sqlpackage.exe /a:Import /TargetServerName:sarveshserver.database.windows.net /TargetDatabaseName:pocdb /TargetUser:readonlyuser /TargetPassword:Passpass@123 /SourceFile:"C:\backups\adventureworks.bacpac"
I have also created a different login and user for this purpose but its still throwing the same error

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

ID: 1f7954fa-99b7-be69-922b-4cadbcedcf2f
Version Independent ID: a87d86dd-0354-ba30-eb0d-fbf3f4e0f8e5
Content: SqlPackage Import - SQL Server
Content Source: docs/tools/sqlpackage/sqlpackage-import.md
Product: sql
Technology: tools-other
GitHub Login: @dzsquared
Microsoft Alias: drskwier

@SarveshPandey -- thank you for your feedback.  This repo is solely for documentation issues, and this appears to be more of a support question.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

cc @dzsquared for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Prepare vertex_ai_featurestore_entitytype for inclusion in C.G.C. documentation

Intending to use this snippet on the following page:
https://cloud.google.com/vertex-ai/docs/featurestore/managing-entity-types

Please put this in a vertex_ai folder so that we don't add to the technical debt.

Not at all clear why this is failing testing. Maybe check with Bharath?


Merge AppRegistration and Application entity

There's no AppRegistration entity present in the Mastodon API documentation.
AppMethods.createApp() in our library returns AppRegistration whereas in the Mastodon documentation an object of type Application is returned.
Suggestion:

add vapid_key, client_id, and client_secret to Application entity (closes https://github.com/andregasser/bigbone/issues/17)
Delete AppRegistration entity
Adopt rest of the code to the new situation

Application entity:
https://docs.joinmastodon.org/entities/Application/
create app call:
https://docs.joinmastodon.org/methods/apps/#create

I only now see that the class just renamed to Token resides in the same auth subdirectory as this AppRegistration entity. With both being or being merged to "official" Mastodon entities, should we perhaps get rid of this subdirectory at the same time and move Token from social.bigbone.api.entity.auth to social.bigbone.api.entity?


Create 198-House-Robber.cs

File(s) Modified: 198-House-Robber.cs
Language(s) Used: c#
Submission URL: _https://leetcode.com/submissions/detail/773140484/_

Thanks, @notauserx!


ByteCodeLink.lookupCE error when trying to use with a project that uses Template Haskell

When I do this
hdevtools check src/Common.hs

I get this error
ByteCodeLink.lookupCE
During interactive linking, GHCi couldn't find the following symbol:
yamlzm0zi8zi22zmJnVa78d7VEeAGdzzI3mdboB_DataziYamlziConfig_ignoreEnv_closure
This may be due to you not asking GHCi to load extra object files,
archives or DLLs needed by your current session.  Restart GHCi, specifying
the missing library using the -L/path/to/object/dir and -lmissinglibname
flags, or simply by naming the relevant files on the GHCi command line.
Alternatively, this link failure might indicate a bug in GHCi.
If you suspect the latter, please send a bug report to:
<EMAIL_ADDRESS>The same error occurs when I use the -f-no-code flag while building (using stack).
Is there any way around this?
Edit: Tried compiling from source. Now there is no error, but the command just sits there producing nothing.

Is the module/package you try to check open source? Where could this symbol be defined?
Sent from TypeApp
On Apr 19, 2017, 7:50 AM, at 7:50 AM, "Sandeep.C.R"<EMAIL_ADDRESS>wrote:

When I do this
hdevtools check src/Common.hs

I get this error
ByteCodeLink.lookupCE
During interactive linking, GHCi couldn't find the following symbol:
yamlzm0zi8zi22zmJnVa78d7VEeAGdzzI3mdboB_DataziYamlziConfig_ignoreEnv_closure
This may be due to you not asking GHCi to load extra object files,
archives or DLLs needed by your current session.  Restart GHCi,
specifying
the missing library using the -L/path/to/object/dir and
-lmissinglibname
flags, or simply by naming the relevant files on the GHCi command line.
Alternatively, this link failure might indicate a bug in GHCi.
If you suspect the latter, please send a bug report to:
<EMAIL_ADDRESS>The same error occurs when I use the -f-no-code flag while building
(using stack).
Is there any way around this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/hdevtools/hdevtools/issues/48

The module I am trying to check is not open source. But the symbol mentioned in the error seem to be part of the Yaml Config package
We use template haskell is some of the modules, is that a problem?

Is this still relevant? You mentioned

Edit: Tried compiling from source. Now there is no error, but the command just sits there producing nothing.

I have encountered the exact same error. Here are some steps that reliably reproduce the error for me (Arch Linux with up-to-date packages as of now):
stack new example yesod-simple
cd example
stack build && stack install hdevtools
hdevtools check src/Application.hs

results in the following error:
ByteCodeLink.lookupCE
During interactive linking, GHCi couldn't find the following symbol:
  yesodzm1zi4zi5zm4W6Tw4ppHO8C6p4jZZwceFO_YesodziDefaultziConfig2_configSettingsYml_closure
This may be due to you not asking GHCi to load extra object files,
archives or DLLs needed by your current session.  Restart GHCi, specifying
the missing library using the -L/path/to/object/dir and -lmissinglibname
flags, or simply by naming the relevant files on the GHCi command line.
Alternatively, this link failure might indicate a bug in GHCi.
If you suspect the latter, please send a bug report to:
<EMAIL_ADDRESS>
Some background:
stack --version
Version 1.5.1 x86_64

resolver: lts-9.10

I am not very experienced with the stack / hdevtools eco system, however let me know if I can provide any additional information to track this down.

Seeing the same issue when using Template Haskell and dynamic binding (ghc -dynamic). Presumed https://github.com/hdevtools/hdevtools/pull/38 which landed in v1.5.0 solved this, but it seems to be an issue with v1.6.0 as well.

Seems that if you enable TH through a language pragma {-# LANGUAGE TemplateHaskell #-} or pass -XTemplateHaskell with hdevtools, it'll work, however I was using TH for quasiquoting and then the pragma itself is unnecessary.


Design for Data Model Extensibility

There are many situations where libraries want to add support for data types not native to a serialization library. The following use cases are known but do not have equivalents in the data model today:

i128 / u128
DateTime and DateTime<Tz>
UUID
Decimal
BigNum

Additionally there are cases I ran into in the past where for a compound type additional information would have been useful too for instance to distinguish sets from vectors.
Today serde relies on in-band signalling to pass such data. Preferable there is a better way to accomplish this.

Additionally there are cases I ran into in the past where for a compound type additional information would have been useful too for instance to distinguish sets from vectors.

Related to this one are "tagged values". Some formats (e.g. CBOR) have the ability to arbitrarily tag their values with additional information. This can be things like distinguish sets from vectors, "this string represents a date", or "these bytes represent a hash". For more information, there was also a discussion about it on the Serde repo: https://github.com/serde-rs/serde/pull/1643 (having worked more with Serde, I now have a better understand why they don't want to add it to Serde, but I think having a serialization library supporting this without hacks would be great).
Those tags could then also be ignored, in case your (de)serializer doesn't support it. E.g. if you deserialize from CBOR with tags into the internal data model, but then serialize into JSON.
So I see two use cases, but I guess they could use the same mechanism. The one I describe above is additional information, which is used to signal something between a serializer and deserializer of a single format. And the other one, outlined in the original issue, is signaling some type that different (de)serializers could agree one.


CC task serialization attempt when use TaskInputs.files(TaskProvider)

Fixes https://github.com/gradle/gradle/issues/24289
Problem:
When using notation like taskInputs.files(TaskProvider) CC trying to finalize a value of provider (which is evaluated as Task instance) and serialize it.
Suggested solution:
At TaskCodecNode level have a 'smart' finalization logic which is awared of possible caveats:

unpacked input file property is a Task
unpacked input file property is a Object[] where items are Task or TaskProvider

In both cases we are delegating unpacking to task.project.files() which is returning ConfigurableFileCollection
Alternative solution:

Introduce a new TaskInputs.files(TaskProvider... taskProviders) API which is CC friendly. Implementation should probably also delegate to task.project.files().

I've stuck a bit in because of uglyness of suggested solution. Such wild conditional unwrapping is doesn't feel natural.
Another thing that I've noticed is a javadoc of TaskInputs.files(Object... paths). It says : The given paths are evaluated as per {@link org.gradle.api.Project#files(Object...)}. It seems it's not a true? Or I've overlooked something?

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle cancel

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test acc

@bot-gradle test acc

I've triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test and merge

🚀

I've triggered a build for you.


Fix OpenAI invocation

[X] Fix OpenAI v0 chat model invocation (renaming prompt kwarg to messages)
[X] Allow specifying OpenAI completion models with either model or engine kwarg

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@f1f511c). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #451   +/-   ##
=======================================
  Coverage        ?   81.80%
=======================================
  Files           ?       44
  Lines           ?     4298
  Branches        ?        0
=======================================
  Hits            ?     3516
  Misses          ?      782
  Partials        ?        0

Flag
Coverage Δ

unittests
81.80% <0.00%> (?)

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

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


missing charset_normalizer dependency

Prerequisites

[X] I am using the latest version of Locust
[X] I am reporting a bug, not asking a question

Description
It appears that https://github.com/locustio/locust/commit/d4d92dc9172aa26fc0b63828cac7d58a4b3b6491 introduced charset_normalizer as a dependency without explciitely including it in https://github.com/locustio/locust/blob/master/pyproject.toml
This means on import if you are using locust library but don't have charset_normalizer installed you will end up with:
[2023-12-06T16:04:04.623Z] ImportError while loading conftest '/workarea/locust_tests/conftest.py'.
[2023-12-06T16:04:04.623Z] locust_tests/conftest.py:1: in <module>
[2023-12-06T16:04:04.623Z]     import locust
[2023-12-06T16:04:04.623Z] /opt/bb/lib/python3.8/site-packages/locust/__init__.py:22: in <module>
[2023-12-06T16:04:04.623Z]     from .contrib.fasthttp import FastHttpUser
[2023-12-06T16:04:04.623Z] /opt/bb/lib/python3.8/site-packages/locust/contrib/fasthttp.py:27: in <module>
[2023-12-06T16:04:04.623Z]     from charset_normalizer import detect
[2023-12-06T16:04:04.623Z] E   ModuleNotFoundError: No module named 'charset_normalizer'

Command line
locust -f mylocustfile.py -t 10s --headless
Locustfile contents
Import from fasthttp after installing latest locust

Python version
3.11
Locust version
2.19.1
Operating system
Linux 7

charset-normalizer is a dependency of requests, so this shouldnt be necessary. Are you sure you didnt just have a broken install somehow?

Hi, I've just got the same issue here. I was updating from an older version.
There is a dependency called 'charset-normalizer' which is missing. Perhaps on new installation, this does not happen, but I would add it in the requirements.txt just in case.

Perhaps it is an issue with older versions of requests. Since multiple people seem to have the issue I have merged the PR.


ReferenceError: require is not defined(for var Net = require('net') and  var JSFtp= require("jsftp"))

I had downloaded the 'jsftp-master.zip' file and extracted the zip file using jsftp.js file in my existing web application.From one of the jsp file I am calling one javascript method mentioned below,
..................................................
var JSFtp = require("jsftp");
function uploadFiles(){
var sourcefile="C:/Users/IBM_ADMIN/Documents/SametimeFileTransfers/Evergreen Hits Of Laxmikant Pyarelal.7z";
var destDir="/rchgsa-p1/03/fmtprjct/uploadtest";
var server="abcd.com";
var user="abc";
var port=21;
var passwrod="pqr";
var ftpServer = new JSFtp({
host:server,
user:user,
port:port,
pass:passwrod,
debugMode:true
});
ftpServer.auth(user, passwrod, function(hadErr) {
if (!hadErr)
alert("auth succesfull")
});
ftpServer.put(sourcefile, destDir, function(hadError) {
if (!hadError)
console.log("File transferred successfully!");
});
}
....................................................
While running in firefox browser I am getting error
ReferenceError: require is not defined for var net = require('net')
I am very much new to this api, can any one please help me to setup this api. I felt that It required some more dependent library but I don't know what are the library needed and from where I can download them.
Thanks in advance.

Hi @bipinmaurya , jsftp is built to be run in the server using Node.js, not in the browser.


Check MGF parser metadata fields and how we handle them

Since MSP and MGF formats are a bit unspecified - would the following be an idea:
First upload the MGF file into the system and then let the user pick out which of the metadata fields are important. For example, in the MGF experiment of the diterpenoids, the RTs are mentioned in the MGF file (RTinseconds) but not displayed in the MS2LDA model. We could store the metadata and let the user select and link the appropiate metadata fields to the parameters that we use (i.e., link RTinseconds to RT).

Too much work.

Simon (and me) is working on this! 🙂


Security group explanation

I think that this document could do with explaining if security groups can be synchronized and, if so, what kinds of security groups are supported.
Thanks,
Ian.

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

ID: 7af61cbd-0ade-e458-e674-c15971b05c05
Version Independent ID: e885e540-00ae-e7fa-8490-6735eeb8a8dc
Content: Azure AD Connect sync: Understanding Users, Groups, and Contacts
Content Source: articles/active-directory/hybrid/concept-azure-ad-connect-sync-user-and-contacts.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@JamesTran-MSFT any news regarding this issue?

@iansmittie
Thank you for following up on this!
@billmath
Can you share any updates on this since?

The following issue is being closed due to the age.  If this is still an issue, please re-submit this.  Thank you.
#please-close


Invalid lambda function output : Invalid JSON error in my PreSignup Lambda

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.13.0
Amplify CLI Version
6.3.1
What operating system are you using?
Mac
Amplify Categories
auth, function
Amplify Commands
push
Describe the bug
I add a PreSignup lambda function so that I can autoConfirm my user on signUp. However, I've noticed that if I remove the async from my handler, the function throws a Invalid lambda function output : Invalid JSON error. But, I am not awaiting anything in the handler itself, so I should not have to use async.
Moreover, I am not clear why both an index.js and custom.js file were generated - ultimately, where should the logic of my lambda live? It doesn't appear as though the custom.js file is being read.
Here is the code in the index.js file:
exports.handler = async (event) => {
  // Confirm the user
  event.response.autoConfirmUser = true;

  // Set the email as verified if it is in the request
  if (event.request.userAttributes.hasOwnProperty("email")) {
    event.response.autoVerifyEmail = true;
  }

  // Set the phone number as verified if it is in the request
  if (event.request.userAttributes.hasOwnProperty("phone_number")) {
    event.response.autoVerifyPhone = true;
  }

  // Return to Amazon Cognito
  return event;
};

As you can see, there's nothing async about the function
Expected behavior
The code in my PreSignup lambda is executed without an issue, aka the user is autoConfirmed.
Reproduction steps

amplify add auth
configure auth with presignup lambda
customize presignup lambda function
amplify push

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

@codybreene If you would remove async you would have to use the callback signature as cognito is expecting a promise.

Also to understand the issue better why would you like to remove async?

How can I tell the Lambda is expecting a promise? Also, is the lambda reading from index.js or custom.js? Why are there two files?

The lambda gets a MODULES env variable injected which should have custom included in it. You can see it in the amplify/backend/function/<resource-name>PreSignup/parameters.json. index.json is what gets executed and expect a promise to be returned.


[Typescript] Where does the tsbuildinfo generated?

Hi fellow engineers,
Since Typescript has --incremental build feature, I just want to know if my app was created using Create React App, where does cache being saved?
I modified my tsconfig.json and added some value to outDir param but I cannot find where does this tsbuildinfo being saved.
    "incremental": true,
    "outDir": "./lib/"

I appreciate any response.
Thanks,
Rem

It's apparently not created. We use fork-ts-checker-webpack-plugin, and it doesn't appear to support it yet, so you can track here.


added cursor not-allowed to no permission

Notes for Reviewers
This PR fixes #
https://github.com/user-attachments/assets/d9b94591-ba1f-4d15-8deb-355dd71bb47c
Signed commits

[ ] Yes, I signed my commits.

@rishabhsharma1997 Could we discuss this issue during the Meshery dev meeting call? Please add it as an agenda item to the meeting minutes.

In addition to adding do-not-allow, I'll suggest that we gray-out the buttons and/or set to disabled.


Fix syntax checks for zoom-in-text/ locate-text to accept both single and double quotes.

In control-zoom: zoom-in-text will work if the string is enclosed in single quotes and not in double quotes.
In control-locate: it's the reverse, the same syntax won't work unless the string is in double quotes.
Code Snippet:
<px-map-control-zoom position="bottomleft" zoom-in-title ="Zoom it on me" zoom-in-text=''></px-map-control-zoom>

<px-map-control-locate position="bottomright" locate-title="Locate Me" locate-text=""></px-map-control-locate>

/cc @davidrleonard

@ppeyro looks like this is working for me with either single or double quotes:

Code snippet:
<px-map-control-zoom position="bottomright" zoom-in-text=''></px-map-control-zoom>
<px-map-control-zoom position="topright" zoom-in-text=""></px-map-control-zoom>

<px-map-control-locate position="bottomleft" locate-text=''></px-map-control-locate>
<px-map-control-locate position="topleft" locate-text=""></px-map-control-locate>

Let me know if I'm misunderstanding the issue, otherwise I think we can close this.

Thanks Tali for looking into it.
I think the title of the issue is misleading.  The issue is the class value being in single quotes vs. double quotes, not the class itself as a whole.  I don't know how much preventive error checking we can do, but basically the fa fa-briefcase being in double quotes vs. single quotes that's causing the issue.
<px-map-control-zoom position="bottomleft" zoom-in-title ="Zoom it on me" zoom-in-text=''></px-map-control-zoom>
    <px-map-control-zoom position="topleft" zoom-in-title ="Zoom it on me" zoom-in-text=''></px-map-control-zoom>

    <px-map-control-locate position="bottomright" locate-title="Locate Me" locate-text=""></px-map-control-locate>
    <px-map-control-locate position="topright" locate-title="Locate Me" locate-text=""></px-map-control-locate>

Check out the debugger when I inspect the elements,   is missing if in single quotes:

Let me know if this helps clarify or more info is needed.
/cc @talimarcus

Thanks for the clarification @ppeyro, that makes more sense now. I'll look into it

Confirmed with David that we can't check this. Closing this issue.


code

hi,
This article Cluster Head Detection for Hierarchical UAV Swarm With Graph Self-supervised Learning is very novel.
Can you open source the code for the article?

Hi jiwei,
Thanks for your interest in our paper. We will discuss opening the source and plan to release our codes next month, contingent upon reaching an agreement.

Thank you very much.  Looking forward to the open source of the code.


Thorium messes up with VS Code installation

System Details

OS: Fedora Linux 38 (Linux 6.4.12-200.fc38.x86_64)
Thorium Version 115.0.5790.172

Problem
Why does the Thorium Browser has a dependency on a certain version of VSCode?
Screenshots

Additional Notes
After installation, if I run system update, vscode installs the exploration and insiders build. removing which also removes Thorium Browser

@h1zardian Thats really weird. I will see if there are any conflicting dependencies on the AUR page. However, I do not maintain the AUR builds of Thorium. If it still causes issues, I recommend using the .appimage or .zip (although I know it wont auto update)


Service Not Started Kill App and Again Open - Android

I have make demo with sdk into ReactNative by using native bridging. It is working when app install first time. But When i will kill app from stack and again open app index file run and call native method for start gimble  and method is call from native but not detecting any method of placemanager.
i show log in android studio that Failed to update places: Unable to refresh place bubble, not fix available. is it Issue or other ?
i'm stuck from 2 days and now i'm questing about the SDK. please help asap so i can give better resolution to client.

Hey @DaxeshKhatri I don't think you have the proper repo. This repo is a networking repo for Kubernetes & Contour. Can you please double-check?


No manual entry for ceph-salt

master:~ # ceph-salt --version
ceph-salt 15.2.12+1601288307.gf6c5fd7
master:~ # man ceph-salt
No manual entry for ceph-salt

Duplicate of https://github.com/ceph/ceph-salt/issues/279


Available field list to the left?? Anyone help?

Hello,
used pivottable for couple of month. Brilliant thing. And I had the available fields on the left side (rather than the top).
I did an update to react-pivottable and they are on top now. I do not find any information how to move them to the left. Is there a parameter? :-( .. I am out of ideas right now.

A couple of things:

react-pivottable is a different project from this one, and issues with that project should be raised here please: https://github.com/plotly/react-pivottable/issues
You're likely looking for the unusedOrientationCutoff prop from react-pivottable

I'm going to close this issue now... If you need any more help, I'd be happy to answer issues in the react-pivottable project :)


Back to pascal case for readability.

Note: for the time being, the KB should be reachable under https://nfdi4plants.org/content/docs/ResearchDataManagement.html again. So no need to change links until KB is out-sourced. y

No idea, why the file name changes did not make it to GitHub. They're all updated on my machine..


Update 'job' parameter help text

It specifies the total number of jobs, not the number of slaves.
Fixes #18

Will merge right away to avoid confusion, give you credit in next release. :)

:smiley:


Rauthy does not shut down upon SIGTERM when metrics server is enabled

Using v0.25.0-lite it seems like rauthy does a graceful shutdown when receiving SIGTERM as printed in logs, however if the METRICS_ENABLED configuration is true, it seems to execute some of the shutdown sequence, but continues running until process is killed after the accept thread is stopped as reported by the logs

 Log with METRICS_ENABLED=true
2024-10-14T11:13:43.129175Z  INFO actix_server::server: SIGTERM received; starting graceful shutdown
2024-10-14T11:13:43.129196Z  INFO actix_server::server: SIGTERM received; starting graceful shutdown
2024-10-14T11:13:43.129245Z  INFO actix_server::accept: accept thread stopped
2024-10-14T11:13:43.129246Z  INFO actix_server::worker: shutting down idle worker
2024-10-14T11:13:43.129299Z  INFO actix_server::worker: graceful worker shutdown; finishing 2 connections
2024-10-14T11:13:43.129307Z  INFO actix_server::accept: accept thread stopped
2024-10-14T11:13:45.133587Z  INFO rauthy_middlewares::logging: <IP_ADDRESS> HTTP/2.0 POST /auth/v1/oidc/token "Go-http-client/2.0"
... continues until process is killed

 Log with METRICS_ENABLED=false
and SWAGGER_UI_INTERNAL and EXTERNAL = false
2024-10-14T11:11:08.915316Z  INFO actix_server::server: SIGTERM received; starting graceful shutdown
2024-10-14T11:11:08.915379Z  INFO actix_server::worker: graceful worker shutdown; finishing 2 connections
2024-10-14T11:11:08.915398Z  INFO actix_server::accept: accept thread stopped
<process is shut down>

It can't have anything to do with the metrics, because I am running with metrics all the time and never had that issue.
But more important:
Does this happen on 0.26 too and is it reproducable?
I had this situation a few times in the past with Hiqlite and am trying since then to find a way to reproduce this, but haven't seen it in quite a while, especially after the latest (blind) fixes for this. But... 0.25 does not use Hiqlite at all yet. Could it also be that this is somehow related to your environment?

It can't have anything to do with the metrics, because I am running with metrics all the time and never had that issue. But more important:

Weird, that seems to be the only difference in the configuration that triggers it for me

Does this happen on 0.26 too and is it reproducable?

I will report back when I test it with 0.26

I had this situation a few times in the past with Hiqlite and am trying since then to find a way to reproduce this, but haven't seen it in quite a while, especially after the latest (blind) fixes for this. But... 0.25 does not use Hiqlite at all yet. Could it also be that this is somehow related to your environment?

Could be related to my environment for sure. I am running rauthy inside a docker-compose configuration.

You were right in that it (with high probability) is not related to METRICS or enabled or not.
In docker-compose, when shutting down services, the default compose waits for a service before sending it SIGKILL is 10 seconds after sending it SIGINT/SIGTERM. It seems like rauthy too has such a timeout internally somewhere (maybe one of these https://github.com/search?q=repo%3Asebadob%2Frauthy from_secs(10)&type=code ?), and so it seems like it becomes a race between docker and rauthy who hits the timeout first, which rauthy loses more often than not on my setup, leading I suspect to rauthy being sigkilled most of the time. I think I am ok with simply increasing the timout for rauthy in my compose config though.
If this seems realistic to you, I am ready to close this issue. (all of this on v0.25.0 BTW)

Oh, if your docker compose does an auto-kill after a timeout, there is a high chance that this produces some conflicts.
Rauthy has internal timeouts, waits for some things to finish like ongoing web-requests, if schedulers are currently running, and most importantly, it will try to do a graceful switch in HA deployments if the current instance is the leader, if a database backup is currently running, and many more. You will start to notice this timeout probably a bit more when using the Hiqlite version. It introduces shutdown delays on purpose to have smoother leader switches in HA scenarios and rolling releases when deployed inside K8s.
Sending a SIGKILL after 10 seconds is pretty quick and I would bump this value up to something like 60. It could take some time depending on what state the application is currently in.

That sounds reasonable. I adjusted the timeout to 20 seconds as I'm running a single instance configuration, but maybe I should consider increasing it further. Anyway I consider this resolved, thank your for the help (and a great software) yet again =)


feat:  ensure the style and app dom correctly

Even though the result ok , but the main question is the timing of content js?


New Google Cloud Platform icon for docs site

I noticed your site is still using the old Google logo in the header. Below I have attached the new logo to replace it.

Ohhhh fancy

I think we need this in higher quality and SVG. Know of any asset stashes?

This issue was moved to GoogleCloudPlatform/gcloud-common#38


Unable to verify some signals

Can't test this on my board.

BIF[2..0]
PCIE_PRES
OCP_WAKE_N
OCP_PWRBRK_N
RBT_ISOLATE_EN
Also, I have a jumper between P12.1 and P_UART1.3 to enable NIC_PWR_GOOD.  However, with card inserted and powered down, this is a 1 and the LED is lit. Removing the card and both the signal and LED are off.  I was expecting this signal and LED to be active when main/aux power is on, on the card.  Is that expectation incorrect?

@rickbrandwein  can you please verify these signals and close the ticket if they are OK? Thx.


NIFI-3065 Per Process Group logging

Summary
Add a toggle in Process Group configuration (default: off), that when turned on would generate a dedicated log file for the process group.
The nifi-app.log file would not be changed and would still contain all of the data.
The nifi_app_pg_.log file would have the same properties as nifi-app.log file (roll over, size, etc) and would contain the logs generated by the components included in that process group.
NIFI-3065
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks @turcsanyip for your review, I've corrected SimpleProcessLogger.

Hello, I don't know if this is the right place to comment this, but I couldn't find anywhere else to ask but my team and I are currently working on implementing a similar cluster monitoring system within our codebase however we have run into some issues. I understand that you have created this PR recently, but do you have an estimated ETA (Like months or years?) on how long you think this will hit production. Let me know if there's a better place to reach you/ask this. Thank you.

Hey @aszkowski - I'm obviously not speaking in the name of the Apache NiFi community, but this pull request should be merged fairly soon as this is under active review. However it's very likely that this change will only be merged on the main branch (which means this change will be for the upcoming NiFi 2.0) and not the support branch for 1.x. In terms of release, the community is making great progress around the NiFi 2.0 goals and I think we can expect a first release of NiFi 2.0 in the next 2-3 months.

As an additional note - this change is bringing a very nice feature to NiFi so any help to build the change and give this a try and share feedback is more than appreciated!

Hello @markap14,
Thanks for your review, I've modified the PR based on your recommendations.

Thanks @timeabarna I think we're really close! Have been testing this, and everything is working well for the most part. I'll leave a couple of minor comments inline, but also I noticed an issue with regards to the synchronization. I created a group and set the Log File Suffix to "Main" and saved it to the registry a Version 1. I then made some other changes to the flow, and I changed the Log File Suffix to "Main22" and saved that as V2.
Now, I can change the Log File Suffix to "SomeOtherFile" and change version to V1. This changed the Log File Suffix back to "Main". If I then change it again to "SomeOtherFile" and change to V2, it again gets overwritten to "Main22". So in the StandardFlowSynchronizer, we need to ensure that we don't overwrite the value if it's already been set.

Thanks @markap14 for your recommendations, I've updated the PR accordingly.

Thanks @timeabarna I did some additional testing, etc. and all looks good to me now. I'm a +1. Looks like Github Actions hasn't yet run.  Assuming that it's green, I should be able to merge today. Thanks!


data:ssbarnea

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Looks good!

Please add displayStatsPublic with a value of true or false then this will be good to go.

Hey, Emma. It's by default false. So, I don't think it's necessary to add that.

@EmmaDawsonDev With lack of json json schema is quite hard to guess which fields are available.


Update Lightning version to 2.4.0 pre

Includes the fix: https://github.com/Lightning-AI/pytorch-lightning/pull/20121 @rasbt
There will be a 2.4 release soon.
Closes #1604 (?)

Thanks! There should be a test for this now (something I added via the previous PR) but I just additionally manually checked and it works great!


Release 0.8.0

Closes/fixes/resolves issue(s)?
No issue
What was added/changed/fixed?
Release 0.8.0 :tada:
Related issue(s)? [Optional]
Others [Optional]
Checklist (after created PR)

[x] Added reviewers
[x] Added assignee(s)
[x] Added label(s)
[x] Added to project
[x] Added to milestone

Might be a problem with the version bump for zwaldowski/semver-release-action https://github.com/fredrikhgrelland/vagrant-hashistack/blob/master/.github/workflows/on_pr_master.yml#L240

Might be a problem with the version bump for zwaldowski/semver-release-action https://github.com/fredrikhgrelland/vagrant-hashistack/blob/master/.github/workflows/on_pr_master.yml#L240

Do you know anything about this, @pdmthorsrud ?


Multilanguage: Languages should show language and country name in dropdown menu

When selecting a homepage language in the multilanguage settings, we can't tell which language we're selecting when having languages enabled in countries with multiple languages.
For some reason, this isn't an issue for "English, American".
In the example below, we have nl_BE and fr_BE  enabled.
In the settings tab, it shows as followed:

Was resolved with latest version of multilanguage/MW


E2E test: only pay attention to internal IPs only and explicitly check for ipv6 address

Signed-off-by: Martin Kennelly<EMAIL_ADDRESS>Comment from @msherif1234 that wasn't addressed in #173

yeah I called out that during E2E PR didn't double check the last diffs I assumed it was done :(
/lgtm
/approve

/hold

Tested it with KinD and ip.To16() acts as expected.

/lgtm

/hold cancel


Move <ExternalLink> into src/components

It may be good to double check this, but I think form components aren't the only ones that use that component.

has PR pending some testing issues


getting error after installing the plugin

I'm having the same issue.

I had the same problem.
The solution was to rollback to commit 0378a6c428a0bed6a2781d459d7943843f374bce
my lazy-lock.json
`{
...
"harpoon": { "branch": "harpoon2", "commit": "0378a6c428a0bed6a2781d459d7943843f374bce" },
...
}`


Remove object synchronously

I think it's good if we have an option to remove/clear objects synchronously.
The scenario is that i know the cache is no longer valid and i want to make sure that i don't fetch from it until i completely remove all objects.

You could do implement this in user-space using a semaphore or dispatch group, no?

You can't. The function to remove/clear objects itself is asynchronous, it will return immediately. It's no point calling that function with a semaphore or distpatch_sync.

Ah, sorry. Did not realize there was not even a completion block.

@namanhams Do you think a completion block would be sufficient? I am not sure if I want to add sync methods for everything, since that would make the API much larger and more difficult to understand. Since the async part is backed by a serial queue, you should be able to call removeObject and setObject immediately after each other and the queue would make sure to first remove then add the object.

@aschuch : i think adding a completion block would be good enough. Actually i prefer this over a separate sync methods.

One thing worth considering (and we experienced this with TMCache) is that while async by default with the ability to make synchronous using semaphores or dispatch groups seems like a great idea on paper, it ends up using more threads than synchronous by default with the ability to make asynchronous when needed does. Just food for thought.

Actually @irace  is right. Make the methods synchronous and wrap it with asynchronous when needed is much easier. That's what i usually do as well

Please take a look at the WIP draft for AwesomeCache 3.0 #56, which will move towards a sync only API as suggested by @irace and @namanhams. Let me know what you think.


#58 Test that the code properly handles multiple columns

See this issue for details.

Wow! Very fast turnaround, and excellent job on this; this isn't a simple task and it's extra impressive as a first-contribution. Also, bonus points for PEP8ing the order of the import statements via putting import pandas as pd above the flagging_site module imports-- I see that and appreciate that!
I'll be able to run this later tonight, but it looks really good and looks like it'll run. I do not believe I will have any additional. comments or feedback if this works.
One small thing, and I hate to be super nitpicky about this: We agreed a while ago to use single-quoted strings (for non-docstrings): https://github.com/codeforboston/flagging/wiki/Code-Style-Guide#1-use-pep-8

Nitpicky is good! I definitely appreciate learning best practices, especially since I'm new to Python 3 (from 2.7). Just updated the strings to use single quotes

As a note so I don't confuse you: neither single nor double by itself is a best practice-- the best practice is being consistent within a project directory.

LGTM!

LGTM!


Update Documentation

Update the Documentation in a way, that new student workers/developers are able to understand the code base without much introduction.

TODO

[ ] README
[ ] HAL Libraries
[ ] Flash Library
[ ] Sensor Libraries
[ ] RTOS library
[ ] Network Libraries
[ ] FPGA Libraries

[ ] Write a SETUP_GUIDE.adoc

Setup Guide
Step By Step Guide how to setup every tool, regarding CLion as IDE.

[ ]  Convert Markdown based Documentation to Asciidoc

Asciidoc
Benefits:

Richer Ecosystem out of the box

External Sorce Code Includes
Improved Tables
Einfach zu erweitern

Supported by GitHub/Gitlab/...
Supported by IDEs (IDEA, CLion, PyCharm, ...)

Test
Added via GH CLI
@ME

[ ] add link to landing page

[ ] Add XVC-Pico to Vivado Debugger Guide

Also see https://github.com/es-ude/elastic-ai.runtime.enV5/issues/171#issuecomment-1813112144


Defining a Foyer XML format

There are now a few force field XML formats: the original OpenMM XML, Foyer's soft fork, Open Force Field's flavor (https://github.com/openforcefield/openforcefields/tree/master/openforcefields/offxml), and another we are developing in the backend. To somewhat clarify compatibility, I propose we introduce a Foyer-specific file extension that explicitly tells a loader that a given XML is meant to be a Foyer XML. This can be .foyerxml, .fxml, or something else, I don't have a strong preference. This would involve

Modifying the loaders to prefer this extension and possibly warn if file.xml is passed (i.e. "Reading file in as a Foyer XML, consider changing the file extension to .foyerxml")
Not erroring out if a file.xml is passed, thus making this a non-breaking change
Changing some of our own XML files to this new extension
Updating documentation specifying the differences between this and other XML format(s)

What do you think @mosdef-hub/mosdef-contributors?

Sounds reasonable, .ffxml might be better for SEO someday so we don't conflict with fxml.


Hugo 0.75.1 improperly escapes HTML in the header.html partial, while version 0.74.3 handled it correctly

I am using Hugo 0.75.1 (0.75.1-1 as packaged by Debian bullseye) and I am experiencing an issue by which {{ .Title | markdownify }} does not work properly in the theme’s header.html partial (HTML is escaped instead of being passed through into the final output), while it does work properly in the theme’s single.html file (HTML is not escaped and is passed through to the final output). Specifically, the problem is as follows:
In my Hugo-based website, I often use  tags within my post titles. As an example, take a post where the title given in the header of the Markdown file is as follows:
title: 'This is a title with Spanish: Hola!'

In the single.html partial of my Hugo theme,
{{ .Title | markdownify }}
 works correctly, it passes This is a title with Spanish: Hola! to the final HTML of the page.
However, in the header.html partial of my Hugo theme, <title>{{ .Title | markdownify }}</title> does not work. Instead, Hugo passes an escaped string to the final HTML of the page: <title>This is title with Spanish: <span lang="es">Hola!</span></title>
I have created a minimal working example in a Github repository.
Now, I posted a question at Stackoverflow under the assumption that there might be something wrong with my setup. However, in the Stackoverflow discussion thread, another user reports that he gets correct output on Hugo version 0.74.3. Therefore, has a bug been introduced into 0.75.1?

The "title" in the HEAD tag does not allow HTML, only inline text.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/title
I did not test your repo, but it's probably the browser that encodes your tags there.

No, it is not the browser. Reading the raw HTML output generated by Hugo, it is clear that Hugo is escaping the HTML.
In fact, if the browser (Firefox in my case) got the unescaped HTML, it would handle it without problems. In spite of your link,  tags in the <title> for the sake of language markup are common, and at least the W3C’s validator regards them as valid HTML.

What I am saying is, that if the tag would contain other HTML tags it would be improper content for the head>title tag. Maybe the change is not a bug but a fix. You can't have HTML in the title tag. You can have HTML in a h1-6 tag. The way Hugo handles it now is proper. I would strip all html in the title tag instead of transforming it.

Again, HTML in the <title> tag validates according to the W3C, so this is a reasonable matter for disagreement both according to the standard and according to real-world usage. What I am trying to ascertain with this Issue report is whether this change in Hugo 0.75.1 (if Hugo 0.74.3 really did handle it different) is intentional and documented.

Ok, I am clinking myself out now. Before I go, here is a screenshot of the specification of HTML.

I belive, this is a hugo issue:
partial
 <title> {{ .Title | safeHTML  }}</title>
 <titlee> {{ .Title | safeHTML  }}</titlee>
{{ .Title | safeHTML  }}

result:
cat public/example.html
    <title><span></span> This is a post with Spanish: <span lang='es'>Hola!</span></title>
    <titlee> This is a post with Spanish: Hola!</titlee>
This is a post with Spanish: Hola!

Text is the only permitted content for the <title> and <textarea> elements per the HTML specification, and Hugo renders these elements accordingly. This is not a bug.