semantic-release breaking changes

Summary
The semantic-release NPM module has been updated to v18.0.0 with a breaking change that requires Node.js v14 or higher.
Semantic release v18
Most of our third party apps use this module to handle creating new releases, but do not lock down the module's version. So these workflows will now be attempting to use v18 of semantic-release.
Acceptance Criteria
To resolve this problem we need to update the Node.js version in these workflows for all the repos below to use >14.17 and lock down the semantic-release version to 18.0.0.
Affected repos

nr1-account-maturity
nr1-browser-analyzer
nr1-cloud-optimize
nr1-container-explorer
nr1-datalyzer
nr1-deployment-analyzer
nr1-event-stream
nr1-github
nr1-graphiql-notebook
nr1-groundskeeper
nr1-integrations-manager
nr1-kentik-network-monitoring
nr1-learn-nrql
nr1-metrics-aggregator
nr1-neon
nr1-network-telemetry
nr1-nimbus
nr1-observability-maps
nr1-pageview-map
nr1-pathpoint
nr1-quickstarts
nr1-slo-r
nr1-status-pages
nr1-status-widgets
nr1-tag-improver
nr1-top
nr1-workload-geoops

Here is a link to the update on the developer site https://github.com/newrelic/developer-website/blob/develop/.github/workflows/release.yml#L129-L167

The Eslint failure on the has bin happenin https://github.com/newrelic/nr1-network-telemetry/pull/60/checks?check_run_id=1983954280 so not sure what to do with that?

Hey @rudouglas, I started going through these and they look great! I just noticed one thing, we probably want to remove the caching step to prevent polluting the cache for other jobs. I commented on a few of the PR's, but I figured a message here would be easier for you.

We should update the template to lock down these versions as well

@aswanson-nr Probably worthwhile. I'm not sure if anyone uses the template anymore, but can't hurt to update it

Quick update: All the repos that have been merged are checked off.
For the few that are left:

Graphiql-notebook waiting on this ticket
pathpoint Don't have permissions to merge
status widgets Don't have permissions to merge
template nerdpack Don't have permissions to merge


[TorchBench] Performance Signal Detected

TorchBench CI has detected a performance signal.
Affected Tests:

eval-cuda-fp32:

BERT_pytorch[dynamo-disc (latency)] 26.208 -> 46.208, -76.3126%
BERT_pytorch[disc (compiled)] 1217 -> 0
BERT_pytorch[disc (clusters)] 1 -> 0
BERT_pytorch[dynamo-disc (clusters)] 1 -> 0
BERT_pytorch[dynamo-disc (compiled)] 1170 -> 0
dlrm[disc (latency)] 1.759 -> 1.866, -6.083%
functorch_dp_cifar10[disc (latency)] 2.093 -> 1.924, +8.0745%
hf_Longformer[dynamo-disc (latency)] 105.792 -> 118.755, -12.2533%
mobilenet_v3_large[disc (compiled)] 580 -> 590
mobilenet_v3_large[disc (clusters)] 9 -> 10
mobilenet_v3_large[dynamo-disc (clusters)] 9 -> 10
mobilenet_v3_large[dynamo-disc (compiled)] 580 -> 590
phlippe_resnet[dynamo-disc (latency)] 2.474 -> 2.869, -15.966%
yolov3[disc (latency)] 41.283 -> 37.248, +9.774%

detail data can be seen in oss://bladedisc-ci/TorchBench/full/20230317-15
created by TorchBench CI automatically

see https://github.com/alibaba/BladeDISC/issues/1117


Rename urls to minimize changes to urls

operations -> operation
install -> deploy
the default landing page was /en/Overview.html but was moved and renamed to /en/overview/Introduction.html. reverted this back to /en/Overview.html

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

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

alluxio-bot, merge this please


MudLink's Underline setting defaulting to "Hover" is not WCAG 1.4.1 A-standard Accessible

Feature request type
Enhance component
Component name
MudLink
Is your feature request related to a problem?
At our org, we're required to meet a AA standard minimum for WCAG. According to the spec, your site's links must meet 3 points to be considered an accessible link. MudLink fails one of those conditions and it is fixed by explicitly setting the Underline setting to Always.
Describe the solution you'd like
I would like for MudLink's default Underline value to default to Always so we don't have to keep explicitly adding Underline="Underline.Always" to every instance of MudLink.
Have you seen this feature anywhere else?
Go to any page in the docs that utilize the MudLink component, use SiteImprove to check the accessibility of the page. Other than issues pertaining to that site's particular design and implementation, every page will show the same "Links are not clearly identifiable" A-standard warning.
Describe alternatives you've considered
We could just keep adding Underline="Underline.Always" to each usage of MudLink but it becomes quite a lot over time. If there's anyway to change the default for my specific project, I'm open to that too. I do think omitting the underline does look better, but it's objectively not accessible according to WCAG guidelines.
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

cc @danielchalmers @igotinfected @henon

so we don't have to keep explicitly adding Underline="Underline.Always" to every instance of MudLink.

We probably could just add it to the MudGlobal as well?

cc @danielchalmers @igotinfected @henon

so we don't have to keep explicitly adding Underline="Underline.Always" to every instance of MudLink.

We probably could just add it to the MudGlobal as well?

I don't see this in the docs, is that (dev)user configurable, or is that just internal to the source code?

I don't see this in the docs, is that (dev)user configurable, or is that just internal to the source code?

It's public https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Services/MudGlobal.cs
And can be used by the end developer, we keep adding new defaults there.
You are right that it has no docs and bad discoverability, I think @danielchalmers wanted to add in to the docs soon or later.

I don't see this in the docs, is that (dev)user configurable, or is that just internal to the source code?

It's public https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Services/MudGlobal.cs And can be used by the end developer, we keep adding new defaults there. You are right that it has no docs and bad discoverability, I think @danielchalmers wanted to add in to the docs soon or later.

This is fantastic, I can set it in my custom service initializer along with other settings.
Seems like "Underline" is already in there, is the dev branch a branch soon to merged into stable?

1.4.1 only states that links have to be distinguishable, underlines are not mandatory.
I do think the default should be Underline though to provide better accessibility out of the box.
We'd have to review MudLinks in the docs for visual consistency and probably mark it as a "breaking change" since it impacts existing visuals.

Seems like "Underline" is already in there, is the dev branch a branch soon to merged into stable?

Hmm, dev is only for the v8 which is currently in the preview, but let me see if I can try to cherry pick it to the v7

Seems like "Underline" is already in there, is the dev branch a branch soon to merged into stable?

Hmm, dev is only for the v8 which is currently in the preview, but let me see if I can try to cherry pick it to the v7

Would be much appreciated, the more configurability the better in my opinion.

New version https://www.nuget.org/packages/MudBlazor/7.15.0
I think I will close it for now, as it can be configurable now with one line.

We'd have to review MudLinks in the docs for visual consistency and probably mark it as a "breaking change" since it impacts existing visuals.

If anyone from the team & community wants to do it, feel free.


Add new job for running rally tasks on qa hw

The traditional question: Should this be in the yaml file? Or perhaps a function in qa_crowbarsetup.sh (or any other) and then just called from this yaml file?

@s-t-e-v-e-n-k  can you take look again ,Thanks!


latest release not available

the latest release does not seem to be available when running
vagrant plugin install vagrant-ca-certificates

I get 1.0.2 not 1.1.0

I'll release master in a few minutes as 1.2.

Never mind, since we haven't released 1.1 it'll go out as that.


Commented constraints in SHACL shapes

Hi,
I noticed some constraints are commented like the sh:minCount in some SHACL shapes, could you explain what this means?
Thanks in advance!

What is commented is # sh:minCount 0, this is a case where in practice it is unrestricted, you may have 0 or more values so it seemed costly to have this check. That is the reason why it is commented.

Hi @xuemduan, could you confirm if the answer provided by @ednaru  answer your issue? if yes, maybe we could close the issue? TIA

Hi @gatemezing . Yes, it answers my question. It can be closed now. Thank you!!


Illegal punning for hasConversionRatio

fibo-der-drc-raw:hasConversionRatio is a sub property of an object property (fibo-fnd-qt-qtu:hasFactor) and a datatype property (fibo-fnd-qt-qtu:hasNumericValue):
<owl:DatatypeProperty rdf:about="&fibo-der-drc-raw;hasConversionRatio">
<rdfs:subPropertyOf rdf:resource="&fibo-fnd-qt-qtu;hasFactor"/>
<rdfs:subPropertyOf rdf:resource="&fibo-fnd-qt-qtu;hasNumericValue"/>
<rdfs:label xml:lang="en">has conversion ratio</rdfs:label>
<rdfs:domain rdf:resource="&fibo-fbc-fi-fi;Entitlement"/>
<rdfs:range rdf:resource="&xsd;decimal"/>
<skos:definition xml:lang="en">indicates the factor used to determine the number of warrants needed in order to buy or sell a specific number of securities or investment units</skos:definition>
	</owl:DatatypeProperty>

This qualifies fibo-der-drc-raw:hasConversionRatio as illegal punning, so we should decide on its proper type.
Note that this makes PR-1627 to terminate - see: https://jenkins.edmcouncil.org/blue/rest/organizations/jenkins/pipelines/fibo/branches/PR-1627/runs/1/nodes/19/steps/47/log/?start=0

@merelog - fixed, but this is in a provisional ontology and shouldn't cause the process to terminate ??

In general, I agree with @ElisaKendall, but in this particular case there was just one fix needed and after the fix we have a stronger suite of tests that would block further issues like this one in both dev and prod.


keybase team request-access claims to hide team existence, but keybase team create reveals it

If I request access to a team that already exists, I get a privacy-preserving message:
~> keybase team request-access $existing_team
If "$existing_team" exists, an email has been sent to its admins, notifying of your request for access.

However, if I try to create the team, I can see whether it already exists:
~> keybase team create $existing_team
▶ ERROR team already exists (code 2619)

I'm not sure it's a bad thing to reveal the existence of teams, but these two things are not consistent :)

This is a good point.  The error messages can use some work. But top level
teams are public knowledge and subteams have names that are hidden. So
probably we didn't differentiate those two cases in the request access
command. Thanks for the feedback!
On Sep 19, 2017 6:57 AM, "Katriel Cohn-Gordon"<EMAIL_ADDRESS>wrote:

If I request access to a team that already exists, I get a
privacy-preserving message:
~> keybase team request-access $existing_team
If "$existing_team" exists, an email has been sent to its admins, notifying of your request for access.
However, if I try to create the team, I can see whether it already exists:
~> keybase team create $existing_team
▶ ERROR team already exists (code 2619)
I'm not sure it's a bad thing to reveal the existence of teams, but these
two things are not consistent :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/8527, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_9VIlJbCwk_jF5CozyXd6k7HYTD2ks5sj54IgaJpZM4PcNs-
.


Question: json_serializable deleted

Why json_serializable package was deleted?
I does this question, because at onfido_config.dart line 3, it has this code:
part 'onfido_config.g.dart'; // GENERATED BY json_serializable, dependency removed, if any changes use online generator

Hi @LeonardoRosaa it was because of some conflicts between build_runners or versioning if I remember correctly, so it was quicker to simply exclude it from the package


how to see if a package is installed?

How do check if a package is installed?
For instance, on Centos8, if you have this snippet:
        dnf.rpm(
            {'Enable EPEL'},
            'https://dl.fedoraproject.org/pub/epel/epel-release-latest-{{  host.fact.linux_distribution.major }}.noarch.rpm',
        )

It will work the first time just fine, but a 2nd time it errors:
--> Starting operation: Enable EPEL
    [<IP_ADDRESS>] package epel-release-8-8.el8.noarch (which is newer than epel-release-8-7.el8.noarch) is already installed
    [<IP_ADDRESS>] Error

I can add the ignore_errors=True option, but that feels... wrong.

Hmm this should work - we check for the package being installed already (in rpm_packages fact) - but the versions are different here; so I think it's trying to install the old version over the newer 8-8 version, and rejecting it.
What's the output if you run with -v? It should be simply running rpm -U <filename>.rpm, which is correct - but I believe rpm will reject it as there's a newer version already.

--> Beginning operation run...
--> Starting operation: Install EPEL rpm to enable EPEL repo
[<IP_ADDRESS>] >>> sudo -H sh -c 'rpm -U /tmp/b7f95f3f0daf418959443bae7b416941df7e134d.rpm'
[<IP_ADDRESS>] package epel-release-8-8.el8.noarch (which is newer than epel-release-8-7.el8.noarch) is already installed
    [<IP_ADDRESS>] Error (ignored)

Hmm yeah this is as expected really - the RPM it's trying to install is older than the one already installed on the system. Not sure what the best course of action here is; I see a few options:

If the package exists, no matter the version, don't do the install (and add a force=False keyword to force install of the older version)
Compare the installed version to the one to-be-installed, which might not always work as expected (poorly versioned packages/etc)
Keep as-is, which will fail if the system has a newer version but this seems silly

I'm leaning towards the first option, what do you think @mkinney?

#1 would require code... that I'm not really sure is necessary at this time.
I think option #4 is to add ignore_errors=True,. (lol)
But, what would the python code to see if a 'epel-release*' package is installed?

Currently you could look for epel-release in the rpm_packages fact (it should have epel-release as the key and a list containing the installed version).

I was trying to figure out something like this:
from pyinfra import host
from pyinfra.modules import dnf

SUDO = True

packages = host.fact.rpm_packages
if packages.get('vim-enhanced', ''):
    print("installed")
else:
    print("not installed")

Is there a better way than that?
So, for the epel thing...
    packages = host.fact.rpm_packages
    epel_installed = False
    for p in packages.keys():
        if p.startswith('epel-release'):
            epel_installed = True

    if not epel_installed:
        dnf.rpm(
            {'Install EPEL rpm to enable EPEL repo'},
            'https://dl.fedoraproject.org/pub/epel/epel-release-latest-'
            '{{  host.fact.linux_distribution.major }}.noarch.rpm',
        )

Thoughts?

I just commented on the PR :) I think this should be something the operation handles (ie option #1!). I've flagged this as a bug for me to fix!

This should now be fixed by https://github.com/Fizzadar/pyinfra/commit/dd6ddcf7c34a8a47449e39a2c059102970fc96b7 (option 1).


Feature Request: custom controls

hey there,
is it possible to create stylish standalone custom controls (combo-box, textbox, button) that could be generated and placed in forms ( where we would define their positions in the form and maybe properties (similar to ms access controls ?) ) , could you tell me if such a thing is possible and maybe some advice on how to do it) , maybe same as how ms access ActiveX work ?
best regards.

i have checked this https://stackoverflow.com/questions/312558/ways-to-use-net-within-ms-access . and it seems that doing such thing is performance heavy and prone to errors thats why i will close this .


Some class paths are created with double backslashes if source file contains some namespace classes

This seems to be a bug.
For example:
1.
 * @param \DateTime $startDate
converts to
* @param \\DateTime $startDate

catch (\TYPO3\CMS\Extbase\Mvc\Exception\InvalidArgumentValue $exception)
converts to
catch (\TYPO3\CMS\Extbase\Mvc\\Exception\InvalidArgumentValue $exception)

Please update, this is fixed in the latest commits already. Had this bug by myself.


[2.0] Test update: ODM no longer supports PHP < 7.2

Q
A

Type
improvement

BC Break
no

Fixed issues
partial #1791

Yes, I did a search. I have to fix the CS failure and it will be all good.

Done.

Thanks @caciobanu!


core: set global namespace version track

Summary
Add a global namespace to append versions to so we can easily track Core versions being used.
Only append when in running in the browser. When a version is loaded add to the list. This will help detect version conflicts when dependencies are not deduped.
window.CDS = {
  versions: ['3.0.0']
}

We will want to do some kind of workaround for SSR to make sure we don't break vuepress and ngUniversal, etc.
I think it's fine that we just don't set the version in those environments. It's a nice-to-have and we shouldn't write code that relies on versions, IMO.

closed in https://github.com/vmware/clarity/pull/4306


[WIP][CI] cache compiled 3rd party crates

Testing in CI.

:umbrella: The latest upstream changes (presumably e6c1c846eb5cf16b1bd9c6e47125d418a5a517fb) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably<PHONE_NUMBER>190fc32aa9bd9a39795b9d51055a98) made this pull request unmergeable. Please resolve the merge conflicts.

Over a month old, no activity closing out, feel free to re-open.


Missing folder_xml in the folder example

readthedocs.io, Examples, Folder, Create
It would be nice to see an example of a folder_xml.
Thanks
https://api4jenkins.readthedocs.io/en/latest/user/example.html#folder

thanks for suggestion. i'm working on doc, will add such xml in doc,
here is version i'm working on: https://api4jenkins.readthedocs.io/en/doc/user/example.html#

folder xml is placed in example now:https://api4jenkins.readthedocs.io/en/doc/user/example.html#folder


Sheet navigation does not work in QS June 2020

Sheet navigation does not work in QS June 2020

It does still work in another app. I'll try to see if I can isolate the actual problem. Closing this issue for now


OAuth not working

See
http://iamemmanouil.com/blog/electron-oauth-with-github/
http://stackoverflow.com/questions/30281732/electron-reactjs-use-browserwindow-for-github-oauth-authentication

Fixed by https://github.com/RocketChat/Rocket.Chat.Electron/commit/5cbb7846f152cd61080d7b956a3a8c673b55345a


HAWQ-1518. Add a UDF for showing whether the data directory is an encryption zone.

@wengyanqing @interma Pls feel free to review this pr. Thank you.

LGTM


Add dtype option to verify_mxnet_frontend_impl

This PR makes it possible to pass the dtype to the mxnet frontend operaot test.
related to #1814

@ehsanmok @tqchen Could you please review this?

Thansk @nishi-t ! this is  now merged


Cannot remove permissions from Role

Laravel: v6.17.1
Voyager: v1.3.1
PHP: 7.2
Database: postgresql 10

Description
Unchecking permissions of a role and then saving the Role has no effect; the Role still has those permissions and they remain checked upon editing again.
Steps To Reproduce

Create a new custom Role, add some permissions and save
Go to edit this new custom role (ex. http://<IP_ADDRESS>:8000/admin/roles/3/edit )
Uncheck some of the permissions selected in step 0
Scroll down and Save
Go back to Step 1: the permissions are still there and not removed

Expected behavior
The entire permissions array should be considered and "replaced" into the database, but instead it's probably just saving the submitted IDs, not removing any non-submitted IDs

I'll be this is a general issue in the code-base logic, about submitting deletions by way of absence of data (ex. lack of certain permission IDs being submitted) is not being considered and not deleted, only presence of data (ex. only the permission IDs submitted) are noticed and are being saved/updated.

It was a problem with routes, please search before opening an issue.
Duplicate of #4668 you can find a fix there.

Voyager: v1.3.1
Issue still persists
This bug as well as bug #4668 are NOT fixed yet, i.e. default vanilla installation of voyager still results in erroneous saving of users/roles

Workarounds
The workaround mentioned in #4668 setting the VoyagerRoleController in role's BREAD work.
See also the details in this comment https://github.com/the-control-group/voyager/pull/4669#pullrequestreview-337527167
However - as of yet a vanilla install of voyager without visiting these github issues and manually implementing the workarounds still has the bug


Adding new state/transition to existing objects

In my workflow, I wanted to add a new state/transition, and I'm getting the available proceedings through get_available_proceedings method, but the old objects don't show the new created transition, only shows in new records.
Is it supposed? There is a way to "update" or "rebuild" in order to show the new transition in old objects?
Thanks in advance

@javrasya

Yes, it's possible.
from river.services.proceeding import ProceedingService
from yourapp.models import ModelWithState
obj = ModelWithState.objects.first()  # get first object for example. You need to do this with each instance
ProceedingService.init_proceedings(obj)

After this, you get available transition.

@I-NOZex, Sorry for the very late response. I have just released v1.0.0 and reviewing all the issues.
First of all, this is a very complicated situation.
Maybe adding a new transition is not hard to handle but if this was allowed by django-river, then django-river would have to support all other modifications like an update and delete as well in the workflow. As you may guess, it is turning out to be hard to manage. This is why this has never been an intention to support modifications in the workflow and have it applied for already existing objects. But new objects will definetly will apply your new workflow definition.
But if you really need it for adding so, you can use @Intey's way. It will ensure that your workflow changes for addings are applied. In the new version of django-river, it looks like this;
obj.river.your_state_field_name.initialize_approvals()


⚠ Adacta-fintech.com has degraded performance

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

HTTP code: 200
Response time: 8317 ms

Resolved: Adacta-fintech.com performance has improved in aba04ea.


Pygments By Default

Syntax highlighting should be included and enabled by default.

That would be nice but I'd like to avoid forcing Suplemon to depend on any non standard libraries. Any idea if we could auto-install it if it's available, but ignore it if it's not?

Found this, looks useful: https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies

I'm not a Python programmer nor do I have any experience with your rather strange assortment of dependency managers.

Maybe I should just add the following to setup.py
      install_requires=[
          "pygments"
      ],

@twolfson Is there a better way of doing this? I'd like it to ignore the dependency if it's not found, but I guess that won't be a problem since pygments is on pypi. What about when people simply run python3 setup.py install ?

What about when people simply run python3 setup.py install ?

You could just output text stating that if they want syntax highlighting they must install pygments as well, or even offer to install it for them.

@richrd Shooting from the hip I would say that optional dependencies sounds reasonable for what you want. People should be able to do:
pip3 install suplemon[all]

I used [all] since I don't know if you can have multiple install requisites specified. If you need a point of reference, splinter uses extra_requires for installing different browser engines:
https://github.com/cobrateam/splinter/blob/0.7.4/setup.py#L27-L30
https://splinter.readthedocs.io/en/latest/drivers/flask.html
I'm not familiar enough with what would happen to a python3 setup.py install but I suggest try it and find out =P
@indolering It's already documented that pygments must be installed for syntax highlighting (including instructions):
https://github.com/richrd/suplemon/tree/v0.1.44#optional-dependencies
https://github.com/richrd/suplemon/blob/v0.1.44/docs/optional-dependencies.md

Thanks for the help!
Looks like python3 setup.py install will download & install pygments even if pip isn't installed. It makes me feel like maybe pygments could even be a required dependency.
Suplemon will install even if pygments can't be installed (e.g. no network connection), but unfortunately it won't run.
pkg_resources.DistributionNotFound: The 'pygments' distribution was not found and is required by Suplemon

I'll play devil's advocate on this one. Syntax highlighting if wonderful,
but it's not necessary. If you're only using the editor to tweak basic
config files from time to time or during setup, but not doing any real
coding with it, it's certainly not needed. Nano would be the prime example
of a useful editor without syntax highlighting support.
I will fully admit however that I am using suplemon with pygments though.
Just pointing out that having pygments as only an optional dependency isn't
horrible. :)
On August 27, 2016 1:22:28 PM Richard Lewis<EMAIL_ADDRESS>wrote:

Thanks for the help!
Looks like python3 setup.py install will download & install pygments even
if pip isn't installed. It makes me feel like maybe pygments could even be
a required dependency.
Suplemon will install even if pygments can't be installed (e.g. no network
connection), but unfortunately it won't run.
found and is required by Suplemon```

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/richrd/suplemon/issues/166#issuecomment-242929543

For what it's worth, nano supports syntax highlighting and even has files bundled for them but they are disabled by default:
http://askubuntu.com/questions/90013/how-do-i-enable-syntax-highlighting-in-nano

Ok, that's cool, I didn't know that :)
On August 27, 2016 5:47:35 PM Todd Wolfson<EMAIL_ADDRESS>wrote:

For what it's worth, nano supports syntax highlighting and even has files
bundled for them but they are disabled by default:
http://askubuntu.com/questions/90013/how-do-i-enable-syntax-highlighting-in-nano
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/richrd/suplemon/issues/166#issuecomment-242942684

Thanks for the input @MrDowntempo @twolfson :+1: Lets go for the optional dependency. It's nice that pygment's is on pypi, because we can just use the same command for installing on all platforms. (No need to instruct the user to install a distro specific package)
@MrDowntempo regarding what you said about syntax highlighting: what do you think about the (greatly inferior) line based highlighting provided by default? Did it feel weird or was it nice to have at least some colors before installing pygments?

I'll play devil's advocate on this one. Syntax highlighting if wonderful, but it's not necessary.

This is a very neckbeard argument, I even saw a config file that disabled syntax highlighting by default because it "distracts" users.  Syntax highlighting reduces cognitive load and helps catch mistakes (especially for those of us who are not natural programmers).

If you're only using the editor to tweak basic config files from time to time or during setup, but not doing any real coding with it, it's certainly not needed. Nano would be the prime example of a useful editor without syntax highlighting support. ... Just pointing out that having pygments as only an optional dependency isn't horrible.   You don't need syntax highlighting to modify a text file, but then why don't we just use nano?

I will fully admit however that I am using suplemon with pygments though.

Shouldn't we give users the best configuration by default?

For what it's worth, nano supports syntax highlighting and even has files bundled for them but they are disabled by default:

Yes, Bash and Nano and everyone else disables syntax highlighting by default, and that is a mistake.  For me, Suplemon differentiates itself from Nano because it is easier to use and syntax highlighting significantly enhances usability.  It's 2016: can we please let usability take priority in FOSS software?
This really should be enabled by default, with disabling it available as a config option during install.  Everyone has internet, no one is going to download Suplemon to a floppy disk and sneakernet it across the server room.  If someone needs to install it without any dependencies, then give them a link to some documentation on how to do it.

I can't really argue your points because I mostly agree with them.  I could argue that pygments is more bloat for supper minimal
installs, but honestly if someone is that tight on space and performance,
they're likely not using a Python coded text editor like suplemon in that
use case either. And again, I use it with Pygments regardless of weather
that becomes required or not. Your arguments about providing the best
defaults in this case are in my view valid. Suplemon does work without
pygments though, so allowing it to be installed without it as an option for
people with some weird use case I can't imagine right now seems OK too. I
guess in a perfect world pygments would be installed by default but
suplemon would still work with pygments uninstalled? Would making it a
required dependency make suplemon easier to maintain? And let me just say,
I'm only a user and not enough of a programmer to provide really helpful
opinions, I just am really enamored by this project :) I'm cool with
whatever route Richard chooses!
On August 27, 2016 10:05:52 PM Zach Lym<EMAIL_ADDRESS>wrote:

I'll play devil's advocate on this one. Syntax highlighting if wonderful,
but it's not necessary.

This is a very neckbeard argument, I even saw a config file that disabled
syntax highlighting by default because it "distracts" users.  Syntax
highlighting reduces cognitive load and helps catch mistakes (especially
for those of us who are not natural programmers).

If you're only using the editor to tweak basic config files from time to
time or during setup, but not doing any real coding with it, it's certainly
not needed. Nano would be the prime example of a useful editor without
syntax highlighting support. ... Just pointing out that having pygments as
only an optional dependency isn't horrible.   You
don't need syntax highlighting to modify a text file, but then why don't
we just use nano?

I will fully admit however that I am using suplemon with pygments though.

Shouldn't we give users the best configuration by default?

For what it's worth, nano supports syntax highlighting and even has files
bundled for them but they are disabled by default:

Yes, Bash and Nano and everyone else disables syntax highlighting by
default, and that is a mistake.  For me, Suplemon differentiates itself
from Nano because it is easier to use and syntax highlighting significantly
enhances usability.  It's 2016: can we please let usability take priority
in FOSS software?
This really should be enabled by default, with disabling it available as a
config option during install.  Everyone has internet, no one is going to
download Suplemon to a floppy disk and sneakernet it across the server
room.  If someone needs to install it without any dependencies, then give
them a link to some documentation on how to do it.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/richrd/suplemon/issues/166#issuecomment-242951622

Sorry I can't answer that, Richard. I installed pygments from the get go
and didn't use suplemon without it. :(
On August 27, 2016 8:51:15 PM Richard Lewis<EMAIL_ADDRESS>wrote:

Thanks for the input @MrDowntempo @twolfson :+1: Lets go for the optional
dependency. It's nice that pygment's is on pypi, because we can just use
the same command for installing on all platforms. (No need to instruct the
user to install a distro specific package)
@MrDowntempo regarding what you said about syntax highlighting: what do you
think about the (greatly inferior) line based highlighting provided by
default? Did it feel weird or was it nice to have at least some colors
before installing pygments?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/richrd/suplemon/issues/166#issuecomment-242949301

I've decided to have pygments install by default when installing the package. Pygments is available on pypi, so it shouldn't be a problem. Even if it can't be installed running suplemon from source will still work fine. Hopefully this is the best of both worlds.

Wow, this took a long time, way too long. I added pygments as a dependency in the latest release. :tada:


Plex for Android: Peer certificate issue

There is a bug on Android Plex App, the app fails to play transcoded medias if the transcoder use a different certificate provider (for example your Plex/Load balancer uses Cloudflare and your transcoder uses LetsEncrypt).
More info here: https://forums.plex.tv/t/android-ffmpeg-peer-certificate-failed-verification/579509

It works on Android build <IP_ADDRESS>53-beta. Plex team fixed it! 🥳


Add all RCT1 walls

Adds all of the RCT1 walls with different heights/colors as compat objects. For the RCT1AA glass wall i've taken the liberty of making the frame remappable for consistency with the RCT2 glass walls.
Currently the sceneryGroup option only allows for one scenery group. So the themed walls will be placed only within their original scenery groups and not within the general fences scenery group.
Note for maintainers: There's some hard coded color converters in S4Importer.cpp within ConvertWall, these will need to be changed to import the brown wooden fence gate properly and to remove the wooden fence color remapping that will be made redundant by these walls.

Could you provide a screenshot of their differences? There are some walls in this PR I didn’t hear about before.

Sure.
Green tile = RCT1
Red tile = RCT2

these will need to be changed to import the brown wooden fence gate properly

Can you clarify this? Seems the brown wooden fence gate has something specific going on?

Within ConvertWall in S4Importer, there's a switch case that remaps colors during S4 import
void ConvertWall(const int32_t& type, colour_t* colourA, colour_t* colourB)
    {
        switch (type)
        {
            case RCT1_WALL_TYPE_WOODEN_PANEL_FENCE:
                *colourA = COLOUR_DARK_BROWN;
                break;
            case RCT1_WALL_TYPE_WHITE_WOODEN_PANEL_FENCE:
                *colourA = COLOUR_WHITE;
                break;
            case RCT1_WALL_TYPE_RED_WOODEN_PANEL_FENCE:
                *colourA = COLOUR_SALMON_PINK;
                break;
            case RCT1_WALL_TYPE_WOODEN_PANEL_FENCE_WITH_SNOW:
                *colourA = COLOUR_DARK_BROWN;
                break;
            case RCT1_WALL_TYPE_WOODEN_PANEL_FENCE_WITH_GATE:
                *colourB = *colourA;
                *colourA = COLOUR_DARK_BROWN;
                break;
            case RCT1_WALL_TYPE_GLASS_SMOOTH:
            case RCT1_WALL_TYPE_GLASS_PANELS:
                *colourB = COLOUR_WHITE;
                break;
            case RCT1_WALL_TYPE_SMALL_GREY_CASTLE:
            case RCT1_WALL_TYPE_LARGE_GREY_CASTLE:
            case RCT1_WALL_TYPE_LARGE_GREY_CASTLE_CROSS:
            case RCT1_WALL_TYPE_LARGE_GREY_CASTLE_GATE:
            case RCT1_WALL_TYPE_LARGE_GREY_CASTLE_WINDOW:
            case RCT1_WALL_TYPE_MEDIUM_GREY_CASTLE:
                *colourA = COLOUR_GREY;
                break;
        }
    }

The brown wooden fence gate (RCT1_WALL_TYPE_WOODEN_PANEL_FENCE_WITH_GATE) has it's RCT1 primary color set to it's OpenRCT2 secondary color during importing as the RCT2 wooden fence gate uses the secondary color for the gate, while RCT1 uses the primary color for it.


Enable CI pipelines for the smart_home branch

Summary
The smart_home branch has been added as a target for the test and lint pipelines
Reasons
Since we will use the smart_home branch as the main branch, it is necessary to run CI testing and static analysis pipelines on it
References

closes #30

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


.transaction([]) fails with Request Timeout Error on large dataset

Bug description
I get this error in v2.8.1
_p [Error]:
Invalid `prisma.injection.upsert()` invocation in
webpack-internal:///./src/pages/api/injection/index.ts:191:79

  Request Timeout Error
    at Jw.request (/Users/user/project/node_modules/@prisma/client/runtime/index.js:210:54)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'UND_ERR_REQUEST_TIMEOUT',
  meta: undefined
}
{
  "code": "UND_ERR_REQUEST_TIMEOUT"
}

if I use prisma.$transation on a large dataset (25k) and if i use Promise.all on the same dataset it works.
How to reproduce
  const businesses= await prisma.business.findMany({
      where: { businessOptions: { some: { isSelected: true } } },
      // take: 10,
      include: {
        businessOptions: { where: { isSelected: true }, include: { directory: true } },
      },
    });

   const operations = prisma.map(({ ...data }) =>
      prisma.injection.upsert({
        where: { id: data.id },
        create: { ...data, business: { connect: { id: data.id } } },
        update: {
          ...data,
        },
      }),
    );

   await appClient.$transaction(operations);

Expected behavior
Not throwing error when using prisma.$transation on a large dataset
Prisma information

Environment & setup

OS: Macos
Database: PostgresSQL 12
Node.js version: 12
Prisma version: 2.8.1

I don't know if it's related but if I map an array with 325 items to upsert functions it'll work, if the array I map from has 326 then I get the request timeout error.
Gf [Error]:  Invalid prisma.job.upsert()` invocation in
D:\Code\Javascript\api\src\bot.ts:51:15
47    }
48 })
49 let cut = filtered.slice(0, 325)
50 const upsertFuncs: any = cut.map((job,[object Object], any) =>
→ 51    prisma.job.upsert(
Request Timeout Error
at $w.request (D:\Code\Javascript\api\node_modules@prisma\client\runtime\src\runtime\getPrismaClient.ts:1258:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0) {
code: 'UND_ERR_REQUEST_TIMEOUT',
clientVersion: '2.9.0',
meta: undefined
}
`
I was playing around with it in order to figure out what was causing this and I think it's the size of the data being passed to the upsert.  When I change the source of my array, the limit increases (possibly because the objects in the array contain less data, another possibility is that it has something to do the number being created and updated. Not entirely sure here).  The 2nd time I tried it, 334 array items worked but 335 failed.

I have a job queue that runs an import of 25-30k records every day and I get this error 100% of the time now.  It actually fails when deleting the previous day's records before the insert (deleteMany call).  Also, it worked fine on Prisma 1.5.1, but we just upgraded to 1.9 (and fixed our breaking changes that blocked the last few updates) and now our nightly import job fails every time.
Do you still need a reproduction for this or is this a confirmed issue?  Happy to put something together, but I suspect any large insert/update/delete will trigger it because a bulk delete of 25k records does the same thing.
Database: postgres:13-alpine
Node: 12.18.4
Prisma: 2.9.0
Request Timeout Error
  at $w.request (/Users/me/myapp/node_modules/@prisma/client/runtime/src/runtime/getPrismaClient.ts:1258:15)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)

A reproduction we could try would be wonderful.

Ok @janpio, here's a reliable reproduction (at least for me)...
https://github.com/jshimko/prisma-issue-3892
That fails for me 100% of the time at around 25-30secs.  Same error...
Gf [Error]:
Invalid `prisma.user.create()` invocation in
/Users/me/prisma-issue-3892/script.ts:25:37

  21 }
  22
  23 // insert generated data
  24 await prisma.$transaction(
→ 25   users.map((data) => prisma.user.create(
  Request Timeout Error
    at $w.request (/Users/me/prisma-issue-3892/node_modules/@prisma/client/runtime/src/runtime/getPrismaClient.ts:1258:15)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'UND_ERR_REQUEST_TIMEOUT',
  clientVersion: '2.9.0',
  meta: undefined
}

Note that lowering the number to 10k records seems to work, so the script is confirmed valid other than the timeout issue.
Let me know if I can provide any more info.  Thanks!

@jshimko I am able to reproduce this, thanks for the reproduction.

Hey guys.  Just curious for planning purposes on our side... is there currently any idea when this issue might be getting looked at (and worked on)?  Not being able to do large bulk inserts is actually a pretty significant blocker on our end that can't wait too much longer and our only temporary fix appears to be reverting back to 1.5.1 (pretty sure that was the last version that worked) and then undo our usage of several features that came in releases after that (which wouldn't be a trivial amount of work at this point).
I completely understand that you guys obviously have to favor your own business priorities.  I'm just trying to figure out if this is days, weeks, or months away.  Because if it's on the longer side, I'm going to have to revert a lot of updates on our side and go back to an older version of Prisma so we can get things working.  In the spirit of supporting open source projects that I depend on (and really love working with!), I'm also happy to figure it out and submit a PR if that makes sense.  But I suspect that someone more familiar with the inner workings of Prisma would be a better/faster option.
Let me know what you guys are thinking and I'll do whatever I have to on my side.  Thanks!

Getting this issue too when adding an array with 600 items in it.

+1 for this.

+1 - wondering why this issue is closed.
Request Timout Error
  let dbTransaction = [];

  for (let index = 0; index < articlesArray.length; index++) {

    const dbWrite = prisma.article.create({
      data: {
        artNr: article.artnr,
        imgSrc: article.bild,
        desc: _desc,
        shop: { connect: { name: shopName } },
      },
    });

    dbTransaction.push(dbWrite);
  }

  console.log('start transaction');
  const dbRes = await prisma
    .$transaction(dbTransaction)
    .then(() => console.log('transaction commited'))
    .catch((e) => console.log(e));

  code: 'UND_ERR_REQUEST_TIMEOUT',
  clientVersion: '2.10.1',
  meta: undefined

TypeError: argument entity is required at etag

using PSQL 12 & NextJS 10

@NikoMontana I think the most recent version has removed those errors.
You're using "2.10.1"
Upgrade to:
"@prisma/client": "^2.11.0",
"@prisma/cli": "^2.11.0",

Yes, 2.11 removed timeouts from undici via https://github.com/prisma/prisma/pull/4156 so this is fixed in 2.11

@GlennChon & @pantharshit00 thank you, updating to 2.11 solved it.


fix dynamic entities on terrain when depth textures are not supported

Fixes #7103
What was happening was that DynamicGeometryUpdater was creating a GroundPrimitive with a "lit" PerInstanceColor. This produces shaders using materials-on-polygons-on-terrain, which won't work on platforms without depth texture support.

Thanks for the pull request @likangning93!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @likangning93!


Fix Japanese translation: "ch-labs", "ch-demos", "2021" folders

Updated the wrong appearance of the equations on Japanese translation of the files under /translations/ja/ch-labs, /translations/ja/ch-demos, and translations/ja/summer-school/2021 folders.
Checked these updates are good in my local build environment.

@0sophy1 thank you so much!


Feature/scrolling - Scrolling and overflowing

Added significant changes to the hierarchy and adds scrolling

Wrong branch my bad


Rapid test registration: Browser not compatible

Where to find the issue
Try to register a rapid test result via a link instead of scanning a QR code, and open the link in Firefox Browser on Android.
Describe the issue
Instead of a successful registration, the website displays a big red text, along with a request to download the Corona-Warn-App:
Your Browser is not compatible. Please open the link in Chrome.

Suggested change
Allow rapid test result registration via other Android browsers (especially Firefox).

Internal Tracking ID: EXPOSUREAPP-7379
Internal Tracking ID: EXPOSUREAPP-7359

@thomorl Thanks for your report. Can you please let us know which device you are using and android version.

May be the browser or system ignores this setting and opens the link in the browser, in which the link is clicked.

Hmmm, I see. So the problem is more related to the way Firefox handles links which can also be opened in an external app, and not to the actual CWA.
When the obtuse red warning about opening the link in another browser has been replaced by an FAQ entry explaining the problem/solution, this issue will probably be resolved.

A user is reporting that under Android with "Samsung Internet" it also says that the Browser is not compatible.

If I open https://e.coronawarn.app in Samsung Internet Version <IP_ADDRESS> I get an error:

@MikeMcC399 If you create an event QR code, and you scan it with the native camera, does it correctly open the CWA? https://e.coronawarn.app/ opens on iPhone Safari browser also just the page and not the app, however an QR code will open the app.

@dsarkar

If you create an event QR code, and you scan it with the native camera, does it correctly open the CWA? https://e.coronawarn.app/ opens on iPhone Safari browser also just the page and not the app, however an QR code will open the app.

I was testing on a Samsung Galaxy A5 (2017) with Android 8.0 and I could not find a native QR scanner, so I tested with a downloaded QR scanner from Google Play Store.
Here are the results:

App installed \ Default browser
Samsung Internet
Google Chrome

no
Your browser is not compatible
prompt to download app

yes
app is opened
app is opened

So it seems the best advice for anybody facing the Samsung Internet browser compatibility error is to set the browser default to "Google Chrome". On my device this was through:
Settings > Apps > Default apps > Browser app and select "Chrome" instead of "Samsung Internet".

@MikeMcC399 Thanks for analysis. The good news: When the CWA is install it works as intended. If not, the user still gets a hin where to download the apps, so I think that is good enough. Some users might prefer to choose their browsers.

@dsarkar
Maybe the error message could be changed, so that the first thing it advises is to check that the app is already installed instead of first saying that the browser isn't compatible?

In terms of messages, the messages can be changed in index.json / index_de.json. However, I personally don't want to make any changes without the approval of @thomasaugsten since he created all the redirect logic.
https://github.com/corona-warn-app/cwa-event-landingpage/blob/9a6ffb27046523938b0225ae3a1ae8fae52332ce/src/data/index.json#L6-L13

@svengabr
Before any messages are changed, perhaps a better idea would be to follow up on the suggestion of the original submitter of this issue @thomorl to publish an FAQ article (https://github.com/corona-warn-app/cwa-event-landingpage/issues/23#issuecomment-850481352). The message could be changed to link to the FAQ article.

There seem to be multiple problems here:

If the incompatible message is output, the instructions to download are overwritten
The text language does not match the page language

I will submit these as separate issues with repro steps.

A start has been made on writing a PR (see https://github.com/corona-warn-app/cwa-website/pull/2428) however the underlying issues need to be clarified before publishing this.

Related new issue #44

@thomorl
The original issue here was (mostly) about Firefox and according to reports in https://github.com/corona-warn-app/cwa-wishlist/issues/532#issuecomment-848999875, this specific issue is now resolved.
Now there are some other points coming up which would probably be better in new issues. What do you think about closing this one and transferring anything else to new issues which make it clearer what needs to be addressed individually?

I added #46 for the special case of attempting to scan a CWA event code using the built-in Firefox QR code scanner. It looks like this is a Firefox restriction, so the relevant information is the list of workaround at the bottom of the issue logged.

Due to the ramp-down, this issue is now obsolete.

https://github.com/corona-warn-app/cwa-event-landingpage/issues/79

The landingpages don't exist any more, this issue is obsolete.


IOU - infinite loading is displayed when select Pay as "I'll settle up elsewhere"

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/12762
Action Performed:
Precondition: use the same device for 3 accounts

Launch the app
Have account A request money from account B
Cancel a request from account A
Have account A request money from account B
Decline a request from account B
Have account A initiate a Split with Account B and account C
Pay a request from account A from account B
Sorry, the video is too long

Expected Result:
Able to Pay a request from account A from account B as "I'll settle up elsewhere"
Actual Result:
infinite loading is displayed when select Pay as "I'll settle up elsewhere"
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS
Android

Version Number: <IP_ADDRESS>
Reproducible in staging?: <IP_ADDRESS>
Reproducible in production?: Yes
Email or phone of affected tester (no customers): Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Sorry for the long video
https://user-images.githubusercontent.com/93399543/203859184-6bd92c32-c34f-4f6f-babd-339b96063feb.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

I'm not able to reproduce this.
https://user-images.githubusercontent.com/22219519/204037255-52292252-b08f-4d53-8a28-f3db8c5edacd.MP4

I was able to reproduce.

For account A I used<EMAIL_ADDRESS>For account B I used<EMAIL_ADDRESS>For account C I used<EMAIL_ADDRESS>

I requested then canceled a payment request from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>I made the same request again, then declined from<EMAIL_ADDRESS>I made a split bill request from<EMAIL_ADDRESS>to the other two

I was able to select the "Settle Elsewhere" option and it worked fine from<EMAIL_ADDRESS>but when I tried the same from<EMAIL_ADDRESS>I got the endless spinner.
@luacmartins I noticed that you had the "Pay from Expensify" option - I didn't see that option when I reproduced. I wonder if it only happens when there is no wallet? Not sure what triggers it, it's a pretty specific set of steps to trigger the issue and feels like a bit of an edge case, but still a bug.

@kbecciv you mentioned that you found this while testing this PR. Do you think that this is a regression related to that PR, or do you think it's an existing bug that you just happened to find while running through those test steps?

I haven't looked into this in more details, but my guess is that IOU reports are not being returned properly by OpenReport and the data is not available. Not sure what's causing this though.

@MonilBhavsar bump.

Sorry, looking now

Heads up, this issue hits the 30 day mark tomorrow, which means it's one of the 6 issues that are currently preventing us from closing out WAQ. Do we think that Carlos's theory will help us solve this? I'm going to be highlighting this issue on Monday in Slack to see if we can hopefully get to the bottom of this and speed up the fix. 😉

@sakluger I tried reproducing the issue, reported by adeel in the slack room, but couldn't reproduce. I commented on that thread. Moving to the original reported issue

Thanks!
also, now I'm not able to reproduce the original issue by following steps mentioned in the GH. @kbecciv could you please retest and confirm. cc @sakluger

I'll test this now and try to confirm. If we can't reproduce, let's close out the issue.

I wasn't able to reproduce this issue either, so I think we should close this. I could also see how this issue was temporarily created while we were merging PRs for the PayIOU refactor, so we can open back up if anyone is able to reproduce in this future.


New version: BioStructures v0.5.0

Registering package: BioStructures
Repository: https://github.com/BioJulia/BioStructures.jl
Created by: @jgreener64
Version: v0.5.0
Commit: d22ce6cad00977766f12751282da245eea8fa957
Reviewed by: @jgreener64
Reference: https://github.com/BioJulia/BioStructures.jl/commit/d22ce6cad00977766f12751282da245eea8fa957#commitcomment-34797057

Thanks for the merge. Will tag the release manually.


Wrong typescript type

Bug Report
Current Behavior
Context.config function as wrong return type
https://github.com/probot/probot/blob/5100488ef3e30c281af9be870b7121e6ec8d7624/src/context.ts#L192
Expected behavior/code
public async config<T> (fileName: string, defaultConfig?: T, deepMergeOptions?: MergeOptions): Promise<T | null>

Environment
not relevant
Possible Solution
Simply fix the return type. I can send a pr if suggested.

#1252 was merged, can the issue be closed? (@viceice)

Have not yet testet but the pr looks good. So yes


New User Response and Session Cookie

Changes
Ensure that when a new user is created:

on success, a success object is returned with a session cookie the app can use to render itself as logged in
on error, an error object is returned that denotes fields with their errors

I spent some time recently trying to ensure that we get cookies from the backend all the way to the frontend. It seems like our cookies are getting set, but there's something funky with Chrome not actually setting our cookies properly. Like, they don't show up in DevTools, or anything similar. It looks like they might be getting set, but I can't quite tell.


Benchmark datasets

Closes #129
Adds CRoaring benchmark datasets. File contents are zstd compressed serialized bitmaps using a shared dictionary. All together adds about 18 MiB.
Utilizing the datasets is out of scope for this PR.

Wasn't the initial plan to create a submodule of the real-roaring-dataset repository and to let the user submodule init/update by himself?

Correct. This avoid a manual step.
Is there some other concern regarding adding these? Would it bloat the size of the published crate?

Correct. This avoid a manual step.

Yup, but cloning the repository is a little issue now, 18Mo of dataset is a lot. Also, I'm not sure that we want to make git care about them. I would prefer that we depend on the official repo, even with a specific revision.

Is there some other concern regarding adding these? Would it bloat the size of the published crate?

Yup, the other concern is about the size of the repository itself, not the crate as you put the datasets in the benchmark subcrate. I hope that cargo doesn't push useless folders!

Yup, the other concern is about the size of the repository itself

The difference between this PR and all the zips is rather large  ~18 MB compared to ~95. zstd is ✨ magic ✨
This size reduction was what led me to just include them in the benchmark crate.

I hope that cargo doesn't push useless folders!

I have verified, it does not.
My main concern is admittedly a subjective one. It just feels icky 🤢  to introduce a manual fetch step to run benchmarks.

My main concern is admittedly a subjective one. It just feels icky 🤢 to introduce a manual fetch step to run benchmarks.

Maybe we can git submodule init/update by ourselves in the build.rs. I just checked the size of the repository, not even compressed, it's 628K, adding 18M to that is a lot. The other downside I see is that the user needs to install zstd to be able to run the benchmarks.
I am sure that we can find a solution to this by automating the clone in the build.rs script or something.  It could even just be a call to the git submodule init/update Command. What do you think?

The other downside I see is that the user needs to install zstd to be able to run the benchmarks.

This uses the zstd create under the hood, they are decompressed in the benchmark code.

I just checked the size of the repository, not even compressed, it's 628K, adding 18M to that is a lot.

Valid.
I'm going to close this and explore using git binary through Command and also check to see if there's some other magic cargo can do. It might make sense to have a crate of datasets.

I'm going to close this and explore using git binary through Command and also check to see if there's some other magic cargo can do. It might make sense to have a crate of datasets.

BTW, I don't think that creating a crate to store the benchmarks is a great idea: https://github.com/rust-lang/crates.io/issues/195.


split private/public API and update namespaces

couchbase/ contains Public API
core/ contains current implementation of the SDK, which right now should be considered "internal" or "implementation details".
Similar logic in C++ namespaces.
everything under core/ directory is defined in couchbase::core::* namespace.
public API from couchbase/ is using just couchbase:: namespace.
Next steps will be gradually move operations/structures/functions that we can expose as public API into couchbase/ directory and document them on the way.
The Transactions C++ library will be merged and live in transactions/ directory, which public API going into couchbase/

jenkins, test this please

@avsej - I noticed that there are things like query_scan_consistency which moved into couchbase::core.   But -- it seems like this is/will be exposed to the public for use in the options, etc...   Do you plan to pull things out of couchbase::core as they are exposed (perhaps via a query_options) in the couchbase:: namespace?

these will be exposed on demand when the related API will be exposed. I'm doing it it this way to ensure that only public parts will be visible, and it also simplifying documenting task

Ok -- that seems reasonable to me.   Anything that doesn't get exposed, stays in the couchbase::core namespace like we'd want.   The wrappers will just have to change their #import ... and namespace references as it changes.

Yes, and technically everything still exposed, but ::core:: in namespace and #include <core/ in headers should be a flag, that the unite is using some of the "core" APIs


Functional Testing - Provide Liquidity

https://docs.google.com/document/d/11hoq2UxlylhBw45m-llrZZ548PGTz6IwWGvZSjodGrg/edit

done as per @desislavva


Chapters over 20 are not handled correctly

Currently chapters like '21' are translated as 'twenty one' (two separate words). This results in a wrong or invalid reference.
Example: 'Isaiah 27:1' is translated as 'Isaiah twenty seven one' and the current logic will result in a recognized reference of 'Isaiah 20:7'.

This may be tricky to fix, but it seems like we would need to look at the second word after the 'twenty'. If it is not a number then use 20 as the chapter, otherwise combine the first two numbers to create the chapter and then use the third (and possibly fourth) as the verse.

Resolved in #v0.5.0


⚠ DDoS-Relay US-W-sfo3-02 has degraded performance

In 6b9ae2f, DDoS-Relay US-W-sfo3-02 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 142 ms

Resolved: DDoS-Relay US-W-sfo3-02 performance has improved in 97a1a3d after 17 minutes.


Add support for caching multipart file uploads

Fixes #113

Coverage increased (+0.004%) to 99.631% when pulling ba66f3b1eb6ab98bbff0c52e9f3a2d252ba2eb42 on JWCook:fix-multipart-uploads into 37ca444b33431866d42c19fdd922a068c20f4a7f on reclosedev:master.


[REVIEW] priyankar pal

GitHub Profile Link
https://github.com/priyankarpal

@priyankarpal It's looking great.

Thanks, @AniketNS


Adding remove + Updating install personal apps

Adds a new documentation article for removing personal apps with a comprehensive PowerShell script. Also updating the installing of personal app to utilize the "soon to come" teams user app list command.
ON HOLD until #1874 is completed.

Merged manually. Thank you! 👏


Setup pnpm and cache dependencies with github action in CI builds

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Closing this as, pnpm/action-setup@v2 is not allowed to be used in apache/kyuubi


Simple sign in/out

Really very simple.
Please leave a comment "OK" if you agree with this pull request.
The 6th "OK" please kindly press the "Merge pull request".

great

I think it is ok~

OK ~

It is ok


Feat/conservation-area-expectations

What?
Some major changes to how expectations and ran and how outputs are stored. This is to align with work on a data manager app, also added some better integration and unit testing for functions. Created simpler more general expectations for use
Why?
To run conservation area tests and make output more similar to issue outputs etc.

Codecov Report
Base: 66.78% // Head: 68.14% // Increases project coverage by +1.36% :tada:

Coverage data is based on head (b01cde8) compared to base (bc08103).
Patch coverage: 74.26% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
+ Coverage   66.78%   68.14%   +1.36%
==========================================
  Files          67       67
  Lines        3056     3171     +115
==========================================
+ Hits         2041     2161     +120
+ Misses       1015     1010       -5

Impacted Files
Coverage Δ

digital_land/commands.py
46.93% <0.00%> (ø)

digital_land/expectations/main.py
43.33% <41.17%> (+43.33%)
:arrow_up:

digital_land/expectations/expectations.py
85.92% <77.51%> (+3.64%)
:arrow_up:

digital_land/expectations/core.py
76.92% <86.95%> (+4.06%)
:arrow_up:

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

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


[Snyk] Security upgrade puppeteer-core from 10.4.0 to 13.3.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

lambda/package.json
lambda/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

768/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-NODEFETCH-2964180
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: puppeteer-core
    The new version differs by 144 commits.

6879f9c chore(release): mark v13.3.0 (#7979)
8ff9d59 chore(deps): update deps
523b487 feat(puppeteer): export esm modules in package.json (#7964)
a858cf7 chore(deps-dev): bump @ types/node from 16.10.9 to 17.0.15 (#7965)
02d651d chore: bump version to v13.2.0-post (#7971)
b531f49 chore(release): mark v13.2.0 (#7970)
41ab4e9 fix: typos in documentation (#7968)
9afdc63 fix: make projectRoot optional in Puppeteer and launchers (#7967)
09ff56b chore: remove commit lint from pull requests (#7957)
96c3f94 feat(chromium): roll to Chromium 99.0.4844.16 (r961656) (#7960)
6a655cb feat: add more models to DeviceDescriptors (#7904)
3b19851 chore(deps): bump debug from 4.3.2 to 4.3.3 (#7948)
2fefcc9 chore: set up ossf/scorecard-action (#7953)
aaac8d9 fix: migrate more files to strict-mode TypeScript (#7950)
f708ceb chore(deps-dev): bump @ commitlint/config-conventional (#7945)
161b283 chore: bump version to v13.1.3-post (#7947)
7b76883 chore(release): mark v13.1.3 (#7946)
06ba963 fix: issue with reading versions.js in doclint (#7940)
43aa986 chore: update minimist to 1.2.5 (#7938)
1247056 chore: update jpeg-js to 0.4.3 (#7937)
0636513 fix: make more files work in strict-mode TypeScript (#7936)
000c1f6 chore: add TODO to use size parameter in getReadableFromProtocolStream (#7930)
776ced6 chore: apply deprecation command (#7929)
afea509 fix: page.pdf producing an invalid pdf (#7868)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

proposed<EMAIL_ADDRESS>is not compatible with<EMAIL_ADDRESS>We'll have to wait until chrome-aws-lambda gets compatible with puppeteer 13.


Explore: Alternatives to OpenSSL

The signature code currently uses the OpenSSL library to create and verify RSA signatures.  This causes use to have the OpenSSL library installed to build. We should investigate the availability of a pure Rust alternative that will not require an external library to be installed for builds to succeed.
Use RusTLS crate (rust implementation of OpenSSL functionality )

The Linux Foundation has a shared cryptographic library project: Hyperledger Ursa.
Reference: https://www.hyperledger.org/use/ursa
Maybe we can try this.

The signature algorithm in the blockchain currently uses the libp2p ed25519 algorithm.
├── libp2p-core v0.31.0
│   ├── ed25519-dalek v1.0.1
│   │   ├── curve25519-dalek v3.2.0
│   │   ├── ed25519 v1.3.0

Since getting this done will facilitate integration testing with Windows based laptops, I am moving this to the to-do column.

Closing since this will be addressed in the future under #511


results: feature reduction

Order of removing (the top one is the first removed, the bold was not removed as it was the last one):
inspire-ml-01:
author_second_given_name_similarity
author_second_initial_similarity
references_similarity
collaborations_similarity
abstract_similarity
journal_similarity
author_first_given_name_similarity
subject_similairty
title_similarity
author_other_names_similarity
year_diff
other_race
keywords_similarity
indian_or_american_native
white
japanese
author_full_name_similarity
affiliation_similarity
coauthors_similarity
black
asian_pacific_islander
chinese
inspire-ml-02
author_second_given_name_similarity
author_second_initial_similarity
collaborations_similarity
references_similarity
abstract_similarity
journal_similarity
author_first_given_name_similarity
subject_similairty
title_similarity
author_other_names_similarity
year_diff
keywords_similarity
indian_or_american_native
other_race
author_full_name_similarity
japanese
affiliation_similarity
black
coauthors_similarity
white
asian_pacific_islander
chinese
inspire-ml-03
author_second_given_name_similarity
author_second_initial_similarity
references_similarity
collaborations_similarity
abstract_similarity
author_first_given_name_similarity
journal_similarity
subject_similairty
title_similarity
author_other_names_similarity
year_diff
keywords_similarity
other_race
indian_or_american_native
author_full_name_similarity
japanese
affiliation_similarity
white
coauthors_similarity
black
asian_pacific_islander
chinese
The results files are called  lnfi_feature_reduction_<x>.dat where x is the number of features removed.

1 feature removed:

-
Precision
Recall
F-scores

paired test
0.9944
0.9733
0.9837

paired train
0.9983
0.9754
0.9867

paired overall
0.9949
0.9736
0.9841

b3 test
0.9895
0.9758
0.9826

b3 train
0.9979
0.9801
0.9889

b3 overall
0.9903
0.9761
0.9831

2 features removed:

-
Precision
Recall
F-scores

paired test
0.9943
0.9736
0.9839

paired train
0.9986
0.9756
0.987

paired overall
0.9949
0.9739
0.9843

b3 test
0.9896
0.976
0.9828

b3 train
0.9982
0.9803
0.9892

b3 overall
0.9904
0.9763
0.9833

-
Precision
Recall
F-scores

paired test
0.9942
0.9737
0.9838

paired train
0.9986
0.9754
0.9869

paired overall
0.9948
0.9739
0.9842

b3 test
0.9895
0.976
0.9827

b3 train
0.9982
0.9802
0.9891

b3 overall
0.9903
0.9762
0.9832

4 features removed

-
Precision
Recall
F-scores

paired test
0.9934
0.9731
0.9832

paired train
0.9979
0.9752
0.9865

paired overall
0.994
0.9734
0.9836

b3 test
0.9891
0.9756
0.9823

b3 train
0.9978
0.9801
0.9889

b3 overall
0.9899
0.9759
0.9828

5 features removed

-
Precision
Recall
F-scores

paired test
0.9943
0.9734
0.9837

paired train
0.9986
0.9753
0.9868

paired overall
0.9948
0.9737
0.9841

b3 test
0.9896
0.9761
0.9828

b3 train
0.9982
0.9803
0.9891

b3 overall
0.9904
0.9763
0.9833

6 features removed

-
Precision
Recall
F-scores

paired test
0.994
0.9733
0.9836

paired train
0.9984
0.9752
0.9867

paired overall
0.9946
0.9736
0.984

b3 test
0.9893
0.9755
0.9823

b3 train
0.9981
0.9798
0.9889

b3 overall
0.9901
0.9758
0.9829

7 features removed

-
Precision
Recall
F-scores

paired test
0.994
0.973
0.9834

paired train
0.9979
0.9751
0.9864

paired overall
0.9945
0.9733
0.9838

b3 test
0.9891
0.9752
0.9821

b3 train
0.9977
0.9798
0.9886

b3 overall
0.9899
0.9754
0.9826

8 features removed

-
Precision
Recall
F-scores

paired test
0.9939
0.9733
0.9835

paired train
0.9982
0.9753
0.9866

paired overall
0.9944
0.9735
0.9839

b3 test
0.9888
0.975
0.9818

b3 train
0.9977
0.9797
0.9886

b3 overall
0.9896
0.9753
0.9824

9 features removed

-
Precision
Recall
F-scores

paired test
0.9942
0.9736
0.9838

paired train
0.9988
0.9757
0.9871

paired overall
0.9948
0.9738
0.9842

b3 test
0.9888
0.975
0.9819

b3 train
0.9982
0.9799
0.9889

b3 overall
0.9897
0.9752
0.9824

10 features removed

-
Precision
Recall
F-scores

paired test
0.9939
0.9736
0.9836

paired train
0.9986
0.9759
0.9871

paired overall
0.9945
0.9739
0.9841

b3 test
0.9886
0.9747
0.9816

b3 train
0.998
0.9799
0.9889

b3 overall
0.9895
0.975
0.9822

11 features removed

-
Precision
Recall
F-scores

paired test
0.9938
0.973
0.9833

paired train
0.9985
0.9754
0.9868

paired overall
0.9944
0.9733
0.9837

b3 test
0.9883
0.9741
0.9812

b3 train
0.9979
0.9795
0.9886

b3 overall
0.9893
0.9745
0.9818

12 features removed

-
Precision
Recall
F-scores

paired test
0.9939
0.9734
0.9836

paired train
0.9983
0.9756
0.9868

paired overall
0.9945
0.9737
0.984

b3 test
0.9882
0.9743
0.9812

b3 train
0.9976
0.9796
0.9885

b3 overall
0.9891
0.9746
0.9818

13 features removed

-
Precision
Recall
F-scores

paired test
0.9936
0.9735
0.9834

paired train
0.9982
0.9757
0.9868

paired overall
0.9942
0.9738
0.9839

b3 test
0.9879
0.974
0.9809

b3 train
0.9976
0.9796
0.9885

b3 overall
0.9889
0.9743
0.9815

14 features removed

15 features removed

-
Precision
Recall
F-scores

paired test
0.9942
0.973
0.9834

paired train
0.9984
0.9751
0.9866

paired overall
0.9947
0.9732
0.9839

b3 test
0.9874
0.9722
0.9797

b3 train
0.9972
0.9782
0.9876

b3 overall
0.9883
0.9725
0.9804

16 features removed

-
Precision
Recall
F-scores

paired test
0.994
0.973
0.9834

paired train
0.9983
0.9752
0.9866

paired overall
0.9945
0.9733
0.9838

b3 test
0.987
0.9723
0.9796

b3 train
0.9971
0.9782
0.9875

b3 overall
0.9879
0.9726
0.9802

17 features removed

-
Precision
Recall
F-scores

paired test
0.991
0.9703
0.9805

paired train
0.9959
0.973
0.9843

paired overall
0.9916
0.9706
0.981

b3 test
0.9833
0.9677
0.9754

b3 train
0.9945
0.9748
0.9846

b3 overall
0.9843
0.9681
0.9761

18 features removed

-
Precision
Recall
F-scores

paired test
0.9888
0.9688
0.9787

paired train
0.9945
0.9721
0.9832

paired overall
0.9895
0.9692
0.9793

b3 test
0.981
0.9656
0.9732

b3 train
0.993
0.9732
0.983

b3 overall
0.982
0.966
0.9739

19 features removed

-
Precision
Recall
F-scores

paired test
0.9788
0.9679
0.9733

paired train
0.9845
0.9695
0.977

paired overall
0.9796
0.9681
0.9738

b3 test
0.9758
0.9605
0.9681

b3 train
0.9877
0.9685
0.978

b3 overall
0.9769
0.9607
0.9687

20 features removed

-
Precision
Recall
F-scores

paired test
0.9785
0.9672
0.9728

paired train
0.9842
0.9691
0.9766

paired overall
0.9792
0.9674
0.9733

b3 test
0.9751
0.9595
0.9672

b3 train
0.9873
0.9676
0.9773

b3 overall
0.9762
0.9597
0.9679

only chinese feature

-
Precision
Recall
F-scores

paired test
0.9751
0.9665
0.9708

paired train
0.9812
0.9681
0.9746

paired overall
0.9759
0.9667
0.9713

b3 test
0.9725
0.958
0.9652

b3 train
0.9844
0.9661
0.9751

b3 overall
0.9735
0.9582
0.9658

Closing all these issues, as the paper is now completed. Thanks @MSusik for setting everything up and running these :)


More info about missing fields

Hi,
so turning on debug I get this message, can you add the missing field to the error?
Loading scanner results from scanner export
POST importscan/
{}
400
{"error": "[u'This field cannot be blank.']"}

https://github.com/OWASP/django-DefectDojo/issues/415 issue originates in defect dojo api


AssertionError: applications must write bytes

Hi,
I'm getting the following error:
python3 ./scripts/tilestache-server.py -p 7070

Running on http://<IP_ADDRESS>:7070/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [23/Apr/2018 11:30:18] "GET / HTTP/1.1" 200 -
Error on request:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 270, in run_wsgi
execute(self.server.app)
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 261, in execute
write(data)
File "/usr/local/lib/python3.5/dist-packages/werkzeug/serving.py", line 241, in write
assert isinstance(data, bytes), 'applications must write bytes'
AssertionError: applications must write bytes

This is running with a reverse proxy in apache.
Any ideas?

probably related to #279
however with python2 I get the same error:
python ./scripts/tilestache-server.py -p 7070

Running on http://<IP_ADDRESS>:7070/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [23/Apr/2018 11:42:14] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [23/Apr/2018 11:42:18] "GET /osm/preview.html HTTP/1.1" 200 -
Error on request:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 270, in run_wsgi
execute(self.server.app)
File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 261, in execute
write(data)
File "/usr/local/lib/python2.7/dist-packages/werkzeug/serving.py", line 241, in write
assert isinstance(data, bytes), 'applications must write bytes'
AssertionError: applications must write bytes

@jucajuca Any luck ?

@jucajuca : Ahan. I found a solution. Hope it will help someone in future.
As the error says application must write bytes and I was returning bool.
To resolve this, when using yield to return data from iterator. All I did was to decode data to utf-8. This should fix the issue.
    def endpoint():
          results_bulk_iter = iter([])
          response = Response(stream_with_context(bulk_update_streamed_response(results_bulk_iter)),
                            mimetype='text/plain')
        return response

    def bulk_update_streamed_response(results):
        for updated, _ in results:
            yield str(counter).decode('utf-8')

I was using python 2 for flask streaming and faced this issue, switching to python 3 solved my problem.

I solved it by converting the expression to string before doing yield. Here is the line of code where I did it:
yield str(b'--frame\r\n' b'Content-Type: image/jpeg\r\n\r\n' + bytearray(encoded_image) + b'\r\n')


Metastore assignment appears incorrect with multiple metastores present

What happened?
We have a databricks environment with multiple metastores (one that will soon be deprecated, one that we're moving to)
When I assign a new workspace to the new metastore, it appears to successfully assign it the first time it's created, but on subsequent pulumi up's, it believes that the metastore assignment metastoreId is the old metastore (which is also has never been assigned to). If i proceed with this change, it appears to remove the assignment off the workspace completely.
Example
az_databricks_workspace = az_databricks.Workspace("dbw-default",
    resource_group_name=resource_group.name,
    location=azure_location,
    sku=az_databricks.SkuArgs(
        name='Premium',
    ),
    managed_resource_group_id=f"/subscriptions/{sub_id}/resourceGroups/rg-dataprojects-databricks",
    workspace_name=databricksworkspacename,
    opts=pulumi.ResourceOptions(parent=resource_group)
)

# Assign the existing Metastore to the new Databricks workspace
metastore_assignment = databricks.MetastoreAssignment("dma-default",
    workspace_id=az_databricks_workspace.workspace_id,
    metastore_id=metastore_id,
    default_catalog_name="main",
    opts=pulumi.ResourceOptions(
        parent=az_databricks_workspace
    )
)

Output of pulumi about
CLI
Version      3.107.0
Go Version   go1.22.0
Go Compiler  gc
Plugins
NAME          VERSION
azure-native  2.29.0
databricks    1.32.2
python        unknown
random        4.15.1
Host
OS       darwin
Version  14.2.1
Arch     arm64
This project is written in python: executable='/opt/homebrew/bin/python3' version='3.11.7'
Backend
Name           pulumi.com
URL            https://app.pulumi.com/jw-servco
User           jw-servco
Organizations  jw-servco, servco
Token type     personal
Dependencies:
NAME                 VERSION
databricks           0.2
pip                  24.0
pulumi_azure_native  2.29.0
pulumi_databricks    1.32.2
pulumi_random        4.15.1
setuptools           69.1.0
wheel                0.42.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @james-servco. I'm sorry you're hitting this issue. Just to clarify, the first time you run pulumi up it works as expected, but then subsequent pulumi ups produce invalid results. Is that right?
Could you give us a self-contained repro that we can run locally.

Looks like this may be related to https://github.com/databricks/terraform-provider-databricks/issues/2489.

Hey! Yep that is correct. The initial pulumi up works as expected, but subsequent ones (once the resources are created) report that the metastoreId points to the other metastore that's never been assigned, not the one that is currently assigned to it.
I'll attempt to create a repro - but i suspect the issue mentioned appears to be in line with what's happening!


Branch Overview Short Dump

Hi,
Recently we have installed abapgit, one of its feature Branch Overview when we select this option then we are getting below shortdump.

can you provide the value of variable ls_raw-author ?

Valie is  "prashantagl<EMAIL_ADDRESS>1487204566 +1100"

hmm, regex seems to be okay, https://regex101.com/r/Bj3ghQ/1
try copying the regex to a small test report to see what is happening, there might be some special characters in the string?

Looks fine in program DEMO_REGEX_TOY as well.

Dont know whats wrong, there are no special characters in the name

hmm, can you try reproducing the issue in a public repository? just add some dummy objects to a new public repository on github

Hi Lars.
I have reproduced same error, uploaded some dummy program into prashantagl/Demo public repository. When I go to ABAPGIT and select branch overview i get same shortdump

works for me, see below. Can you try updating abapGit to the latest version? Looking at the objects it looks like the version you have is at least a month old, however I am not sure it will fix the problem.

last week I updated code with latest one, but I was getting short dump in the staging option...I will try again today and let you know

Hi Larshp - I have one more question.
Scenario is I have created branch 1 from master branch. I make all my changes in Branch 1 and create transport to save those changes. When I release the transport  and check my program in se38 I can see my branch 1 changes there. Is it expected behavior.
However if I navigate thro ABAPGIT for master and Branch 1 changes, in master branch I dont see my Branch 1 changes, I can only see my changes in Branch 1 which is correct.
Can you please clear my understanding here how master and branches will behave when we release transport in which captured the branch 1 changes.
Cheers!!!
Prashant

abapGit does not integrate with the SAP transport system, so nothing will when a transport is released
(have been thinking of some features regarding this, but need to do more thinking)

Is it expected that when we create branch and make our changes in branch. and when we check the program via separate SE38 transaction(instead of navigating from abapgit), we should see changes from Branch or we just see master branch code there?

in SAP there is always only 1 version of each program active
If you want to work with branches, you decide how to use it, abapGit does not decide/help how to do branching(except for implementing the git protocol).
From my point of view each git branch can be a separate SAP system, this is they way SAP handles branching.

Issue regarding multiple active versions: #382
Please note the crazy label :blush:

thanks this helps


Does table1 use llava-1.5-7b？

llava's eval script does not have LLava-1.5-7b.json files for many data sets，such as SQA. How did you test the performance of SparseVLM in llava-1.5-7b. Look forward to your guidance.

I appreciate your interest in our work.
We currently provide only 3 types of scripts. The rest of the scripts can be rewritten according to this rule or released after the paper is accepted.


Also check "commondir" when checking for a stash

In git-info, we check if there is git stash by looking for .git/refs/stash file.
But in git worktrees, there is a file named commondir under $(git-dir), and it's usually ../.., and refs/stash is not in $(git-dir) but in $(git-dir)/../.. (the ../.. part comes from the content of commondir).
This patch checks there as well.

ok. i feel it's still important to check the file for performance reasons.
let me know if this'll do

Giving this a little push..

Looks good to me! Thanks for submitting this! And sorry about the delay in reviewing.


Avoid throwing exceptions from native modules when the host activity …

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native :thumbsup:
[ ] I am making a fix / change for the macOS implementation of react-native
[x] I am making a change required for Microsoft usage of react-native

(give an overview)
Office apps are not based on AppCompat/Fragment activities. This change avoid RN throwing exceptions when the host activities are not FragmentActivity.
I'm working on pushing this change to upstream Facebook repo too.
(optional)
Microsoft Reviewers: Open in CodeFlow

Raised a PR in the upstream FB repo : https://github.com/facebook/react-native/pull/27425

Unless its very urgent, can we hold off on merging until the upstream PR gets merged, in case there is core review feedback from Facebook on that one.

Unless its very urgent, can we hold off on merging until the upstream PR gets merged, in case there is core review feedback from Facebook on that one.

Sure.. we can wait.


Tuto POC

Hello, First i want to thank you for this great rootkit, can you please make a Demo or a Poc using cobaltstrike or meterpreter shellcode.

You're welcome :)
I'm not familiar with cobaltstrike. But in order to make r77 easy to deploy, it comes as one single executable Install.exe. You only need this one file - it already contains both DLL's, etc.
It can be executed using RunPE, so if your meterpreter supports execution of 32-bit EXE files using RunPE, you can transfer Install.exe like that. Although this is rather generic advice, because like I said, I'm not familiar with cobaltstrike.

thanks for the quick answer,keep up the the good job


Typo in Twitter account name

I just noticed that "Government" is misspelled as "Governement" in your Twitter account's name.

ping @ruebot


Migrate GitHub repo to Mesh organization

Assigned to Daniel for him to get us access to import the repo


Better docs for Vercel

Expected

As a user I expect to be able to follow the guide so I can understand how to set up Ackee.
As a user I expect to be able to click the Vercel Button in order to deploy Ackee automatically

Actual:

The docs don't explain what needs to be done to setup MongoDB
The Vercel Button clones the repo instead of forking it

It is unclear to me how to setup Ackee on Vercel.
I tried two options:

Vercel Button

This actually clones the repo instead of forking it.

Fork manually and deploy

This seems to be the better option since it allows to "Fetch upstream"
Actual Problem with Docs:
What is mostly unclear and undocumented is: "Setting up MongoDB"
The docs mention:

Set environment variables ACKEE_USERNAME, ACKEE_PASSWORD, ACKEE_MONGODB, and ACKEE_ALLOW_ORIGIN.

What should I put in ACKEE_MONGODB
What should I put in ACKEE_ALLOW_ORIGIN

Sorry if these questions seem dumb but I have no experience with MongoDB or Ackee.
It would be amazing if you could give me a hint on what needs to be done here.
I assume that ACKEE_ALLOW_ORIGIN would be the domain of the deployment but I'm unsure about it.
I have no idea what ACKEE_MONGODB does as it does not seem to be documented anywhere.
Do I need to setup a mongoDB instance myself or should this work out of the box?

Thanks for the feedback! We should definitely improve this part in the documentation. It also seems that the Vercel deploy website changed a bit and I can see why the documented steps aren't proving enough information.
This could help for now:
To set the ACKEE_MONGODB environment variable you need a MongoDB instance running somewhere. There're multiple services you can use, but I guess that MongoDB Atlas is the best one to start with: https://www.mongodb.com/de-de/cloud/atlas
Whatever service you choose, you will get a MongoDB connection URI. That's the string you should use for ACKEE_MONGODB: https://github.com/electerious/Ackee/blob/master/docs/Options.md#database
The ACKEE_ALLOW_ORIGIN is explained here: https://github.com/electerious/Ackee/blob/master/docs/CORS headers.md#platforms-as-a-service-configuration
Let me know if you have other questions. A PR for an improved documentation is also welcome!

Thx for the fast reply. I'll open a PR with the interesting parts of your comment, as soon as I manage to get this running. (Might take a few days/weeks since we're on a tight schedule)


Why did this happened?console warning   will be ignored

the consle waring 'Warning: You should not use  and  in the same route;  will be ignored'
<Switch>     <Redirect path="/" exact={true} to="/index" />     <Route component={Index} path='/'>      <Route path='/index' component={Indexpage}/>      <Route path='/artical' component={ArticalList}/>      </Route> </Switch>
I already tried like this code
<Switch>     <Redirect path="/" exact={true} to="/index" />     <Index>      <Route path='/index' component={Indexpage}/>      <Route path='/artical' component={ArticalList}/>      </Index> </Switch>
it's not working

What the warning says: You can't use the component prop and children at the same time. You can only use component, render xor children, but not combine any of the three.
The issue with the second code blob seems to be the <Index/> component blocking Switch from properly working.
Please note that this is not a support platform, but a bug tracker. If you have issues, please consult StackOverflow or the reactiflux discord server. This issue will be closed by a maintainer soon.

What the warning says: You can't use the component prop and children at the same time. You can only use component, render xor children, but not combine any of the three.
The issue with the second code blob seems to be the <Index/> component blocking Switch from properly working.
Please note that this is not a support platform, but a bug and feature request tracker. If you have usage questions or want general advice, please consult StackOverflow or the reactiflux discord server. This issue will be closed by a maintainer soon.

Thanks for ur reply,just because the  component which render for tow times blocking my process.Thank you!


Header styles aren't applied in the docs on Firefox

Description
Expected behavior:

Actual behavior:

Browser/OS Environment
Browser: Firefox 119.0 (64-bit)
OS: Fedora 38

This is because Firefox does not support CSS :has() IIRC it should be coming soon. Might make more sense to just wait it out unless someone wants to figure out another implementation

Hey, this issue can be closed now, right?


How we can create rating Content (polygon path) of any svg?

How we can create rating Content (polygon path) of any svg?
for example Heart svg etc.
<svg width="20" height="19" viewBox="0 0 20 19" fill="none" xmlns="http://www.w3.org/2000/svg"> <path d="M10 18.3137C6.38661 15.087 0 11.0734 0 5.70882C0 2.68756 2.42 0.313721 5.5 0.313721C7.24 0.313721 8.91 1.05813 10 2.31372C11.09 1.05813 12.76 0.313721 14.5 0.313721C17.58 0.313721 20 2.68756 20 5.70882C20 11.0647 13.6214 15.1044 10 18.3137Z" fill="#2E3A59"/> </svg>

Hello, there is limitations in this way.
Someone already asked me that question. You can find my answer here :
https://github.com/TonyFresneau/nuxt-rating/issues/11
I'm closing this ticket because it corresponds to a request I've already dealt with. Have a nice day!


what is the multiply entry for?

I wondered. What is the 'multiply' attribute for in
    pin: A0
    name: "Gas ADC"
    update_interval: 1s
    filters:
      - multiply: 3.3 # for NodeMcu ESP8266 v3 Lua

I believe this is for ESP8266 only...D1 Mini or NodeMCU etc which has built-in voltage divider on pin A0 to bring 3.3v to 1V. On ESP32, this shouldn't be required.


Async functions in alterItems don't work

Steps to reproduce
I ran the examples from https://feathers-plus.github.io/v1/feathers-hooks-common/#alteritems
You can find my code and output here:
https://gist.github.com/sean-nicholas/c0d73e386743a2b20f690aa473d88134
Expected behavior
alterItems should work with async functions as described in the documentation and in https://github.com/feathers-plus/feathers-hooks-common/issues/307
Actual behavior
Promises are not resolved as you can see in the gist output file.
System configuration
Module versions (especially the part that's not working): 4.8.0
NodeJS version: 8.1.4
Operating System: macOS

I think the example below from the documentation is rather difficult to implement because every property of the (returned) object has to be checked (deep?) if it is a promise.

alterItems(rec => {  rec.userRecord = (async () => await service.get(...) )()})

It might be more straight forward if the users must wrap their whole altering function in a promise / make it a async function.
What do you think?

@beeplin ^^^ any comments?

Okay, I will create a PR in the next few days

Could you also please submit a PR for the docs? The file is feathers-plus/docs/source/feathers-hooks-common/index.md#alteritems . Thanks.


Removing users doesn't clear users data on all cases

Removing users trigger remove_user_directory(), which shall remove all user's data from disk.
The function doesn't take into account legacy or hashed paths, and it isn't able to clear users' data on such cases.

Hashed paths?

Moved to https://github.com/realm/realm-core/issues/4187


support spaces in status

Type of change
Bug fix (change which fixes an issue)
https://bazelbuild.slack.com/archives/C04281DTLH0/p1713216473704709
The old regex didn't support spaces in the workspace status entries, this should hopefully fix that 🎉
Test plan
Updated link to new regex101 examples

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


Incorrect command palette keyboard shortcut

The documentation says to use  use Ctrl+Alt+P to open the command palette, but the default keyboard shortcut is actually Ctrl+Shift+P.

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

ID: 5cf8b1c7-7e47-f9fd-67f7-64d56791e0f1
Version Independent ID: 5524a7f4-3a42-9641-73c1-4161be8ade08
Content: Create an Azure plug and play device
Content Source: articles/iot-pnp/quickstart-create-pnp-device.md
Service: iot-pnp
GitHub Login: @miagdp
Microsoft Alias: miag

Thanks for the feedback! We are currently investigating and will update you shortly.

@zadixon Thanks for reporting this issue. PR has been created to update the document.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


c++14 support needed

C++14 is intended to be a small extension over C++11, featuring mainly bug fixes and small improvements.
And in both visual studio 2015 and gcc/g++6, std=c++14 is specified by default.
So please support c++14 besides c++11. Thanks.
see:
https://docs.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version
https://gcc.gnu.org/gcc-6/changes.html

Hi @yantaozhao,  thaks for reaching out to us. What do you mean by "support"? So what is happening for you and what would be the thing you expect/want to happen?

Currently, when using the plugin to "Create Compilation Database" in visual studio, the upmost option is c11. And the plugin emits some errors on the codes which was built sucessfully with VS2015.3.
I don't know whether the plugin meets my codes which use some c++14 new feature. That's my concern.
Brs.

The C language standard you select in the Visual Studio extention is applied only for the C files in your Visual Studio solution. Visual Studio 2015 supports C++14 and this is the C++ standard that is automatically written to the compilation database for all C++ files in your solution. So everything should be fine for you.
What errors does the plugin emit?

Sound good. thx.


Updated from Meteor 2.8.0

@denihs , do you have write access to merge it?

Merged and published to version 1.17.1


advice on dynamically updating some widgets in the tree

I have a widget hierarchy that contains a list of items ... some of the items are being shown with a spinner to indicate that the content of the item is still pending ... and I will get fresh data for those items soon via a web socket.
Via websocket, I get a list of json fragments that contain the fresh data for these pending items.
Do you have any advice/recommendation about merging those items into the FullWidgetPage tree where just those updated items get redrawn?
Looking at things like for_each, dynamic, setWidgetByKey, etc ... I bet there is an good/easy way to do this.

One attempt I made was to have a set_widget item that defines widget1 and widget2.
I then display these in a list with ...
"${widget1}",
"${widget2}",

I then update the registry via an onTap on a button like this ...
          var registry = JsonWidgetRegistry.instance;
          var json = '''
{
  "type": "container",
  "args": {
    "padding": "20",
    "margin": "20",
    "color": "#88F"
  },
  "child": {
    "type": "text",
    "args": {
      "text": "widget1_data !!"
    }
  }
}
'''
              .trim();
          var data = JsonWidgetData.fromDynamic(
            json,
            registry: registry,
          );
          registry.setValue('widget1', data);

I step thru the code and see in the setValue function the valueStreamController is updated ... BUT ... the widget1 display does not update with the new UI definition.
For some reason, the widget references are not listening it seems?
"${widget1}",
"${widget2}",

Hmm ... this seemed to work by adding a listen to the container that wrapped my set_widget widget
                                {
                                  "type": "container",
                                  "child": "${widget1}",
                                  "listen": [
                                    "widget1"
                                  ]
                                },

instead of just
                                {
                                  "type": "container",
                                  "child": "${widget1}",
                                },

Ah, correct.  You have to tell the engine what to listen to changes on.  It's more expensive to listen to variables for changes so the default setup is to not listen unless explicitly told to.

make sense ... thanks !