Ignore trailing newlines when doing 'test and set' on reference files

This is because git commit might add these. Fix #610
/cc @djs55

The proper fix should probably be to modify https://github.com/mirage/ocaml-git/blob/master/src/git/fs.ml#L630-L638, but this should be fine too.

@samoht I've got some CI fixes on #612 for CircleCI and appveyor -- feel free to grab any you don't already have!

I think you might need

xcode.8.3: https://github.com/moby/datakit/pull/612/commits/30c52ade0a146664ba7c9aa1e9b18c8abdb95366
remove one of the references to version.ml: https://github.com/moby/datakit/pull/612/commits/ba1f3203a52d0316e347df6ecf81c8477b0001b6
fix opam-depext no such file or directory: https://github.com/moby/datakit/pull/612/commits/b6b6aa18d0ba5cf583c2f65893a896f80b3a60bc
fix "cannot find topfind" https://github.com/moby/datakit/pull/612/commits/52fa58cf50fdcbcbce2b0d043e2c0313de857a64

(the opam config exec -- ones are a bit weird. There was a bug in OCaml's standard library recently to do with environment variables wasn't there?)
I think these should fix CircleCI and appveyor

@djs55 thanks, I have rebased on top on your branch

Rebased on top of master.


todo

[x] add test
[ ] add optional command (e.g docker

[ ] shell script to rewrite LICENSE file ${account_name}

remove cobra to reduce binary size

The release is successful, but the badge is FAILING.

goinit return command lists and those usage
goinit run ${name} create ${name} directory and createFiles function
goinit run ${name} -p ${package_name} create ${name} directory and createFiles function and run go mod init
goinit -v return version

https://kazuhira-r.hatenablog.com/entry/2021/01/09/220048
text/template を使って、README.mdとLICENSEファイルを標準入力の値を使って作成する

windowsでもインストールできるようにする

FROM golang:1.17.3
WORKDIR /app
COPY go.mod ./
COPY go.sum ./
RUN go mod download

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
robsonpeixoto, @robertcollura, @duyguserbest, @yeahx, @satoru-takeuchi, @szktkfm, @baifan, @weidiaoxiang, @haiker2011, @hongshibao, @Senorsen, @jerryjayce, @fuhbar, @linux0x5c, @anitsh, @alwayrun, @shlykov, @mhanif, @frost1990, @mmpei


ENH: Set metal environment var for mac

Close: https://github.com/xorbitsai/inference/issues/723

But, chatglm cpp needs to explict set the environment var GGML_METAL=ON

Set environment var does not affect pip install dependencies. It seems that there is no way to set an environment var for the dependency in pyproject.toml or setup.cfg.


Outline shows when input type="search" is grouped with button

Please search for duplicate or closed issues first.
Describe the issue
Current Behavior
When  is grouped together with button there is an ugly outline showing around input on the side where the button is not. The corners are rounded, but focused outline is more rectangular than the side of the input
Expected Behavior
 grouped with button should behave the same as standalone input when focused
Reproduction URL
https://codepen.io/Frodik/pen/NWVQWjK
Environment
Chrome

Not sure what your goal is. Do you want to have the button also be round, or do you want the whole group (search input and button) to be rectangular?
If your goal is to achive the former, you need to use <fieldset role="search"> instead of <fieldset role="group">. (docs)
If you want the latter, I am not sure if this is possible, as search inputs are intentionally rounded. (docs)


Marks Percentage Calculator, resolving issue #150

This is a calculator that takes the marks of the subjects and provide the percentage and give error when the input marks is illegal.
Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <issue_number_here>

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSOC'22 contributor
[ ] Have you added a working video of your calculator ?

Screenshots / Gif (Optional) 📸


DBeaver not creating a table alias after adding a JOIN clause in SELECT query

System information:

Operating system (distribution) and version : Windows 10
DBeaver version: Version <IP_ADDRESS>005311732
Additional extensions: None

Connection specification:

Database name and version: MySQL 5.7.19
Driver name: mysql:mysql-connector-java
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
DBeaver doesn't auto-create table alias for the second (or any subsequent) table in a JOIN clause. The auto-alias for first table in the select query shows up fine.
Steps to reproduce, if exist:
Write a script like below. Dbeaver will automatically create the alias "a" because of auto-complete. However, as soon as you add tableB after an inner join, it does not create alias "b" automatically. You have to type in all subsequent aliases manually.
Select * from tableA a
inner join tableB b
on a.column = b.column
Include any warning/errors/backtraces from the logs

thanks for the bug report

verified

Fixed in 7.1.1

Hello, @MuqadderIqbal. Version 7.1.1 will be available on 22.06.2020

@LonwoLonwo thank you for the quick resolution! Much appreciated.

Verified as fixed in 7.1.1. There's another bug I found but I'll log a separate issue.

@MuqadderIqbal ok


Videojs-record and another simply videojs player on the same page

Sorry for my English
Description
When we have on one page video-record player and videojs player with any video occurs strange behaviour: click on simply player's progress control doesn't have any effect.
Steps to reproduce
Add to one page video-record object and simply videojs player
Additional Information
Please include any additional information necessary here. Including the following:
versions
videojs
6.8
browsers
all
OSes
win 10

@Xteda87 perhaps it's related to this piece of code: https://github.com/collab-project/videojs-record/blob/master/src/js/videojs.record.js#L32
Can you rip that out, try again and see if it improves things?

I found the problem. If I include the file videojs.wavesurfer.js version more than 2.0.3 then click on the progress controls doesn't work.

@Xteda87 can you provide some example code to reproduce this?

I just tried this with the following example:
<!doctype html>
<html>
<head>
  <meta charset="utf-8">
  <title>Audio-only Example - Record Plugin for Video.js</title>

  <link href="../node_modules/video.js/dist/video-js.min.css" rel="stylesheet">
  <link href="../dist/css/videojs.record.css" rel="stylesheet">

  <script src="../node_modules/video.js/dist/video.min.js"></script>
  <script src="../node_modules/recordrtc/RecordRTC.js"></script>
  <script src="../node_modules/webrtc-adapter/out/adapter.js"></script>
  <script src="../node_modules/wavesurfer.js/dist/wavesurfer.min.js"></script>
  <script src="../node_modules/wavesurfer.js/dist/plugin/wavesurfer.microphone.min.js"></script>
  <script src="../node_modules/videojs-wavesurfer/dist/videojs.wavesurfer.min.js"></script>

  <script src="../dist/videojs.record.js"></script>

  <style>
  /* change player background color */
  #myAudio {
      background-color: #9FD6BA;
  }
  </style>

</head>
<body>

<audio id="myAudio" class="video-js vjs-default-skin"></audio>

<video id="myVideo" class="video-js vjs-default-skin"></video>

<script>
var player = videojs("myAudio", {
    controls: true,
    width: 600,
    height: 300,
    fluid: false,
    plugins: {
        wavesurfer: {
            src: "live",
            waveColor: "#36393b",
            progressColor: "#black",
            debug: true,
            cursorWidth: 1,
            msDisplayMax: 20,
            hideScrollbar: true
        },
        record: {
            audio: true,
            video: false,
            maxLength: 20,
            debug: true
        }
    }
}, function() {
    // print version information at startup
    videojs.log('Using video.js', videojs.VERSION,
        'with videojs-record', videojs.getPluginVersion('record'),
        '+ videojs-wavesurfer', videojs.getPluginVersion('wavesurfer'),
        'and recordrtc', RecordRTC.version);
});

var player2 = videojs("myVideo", {
    controls: true,
    width: 600,
    height: 300
}, function() {
    console.log('second player ready');
});
// load example MP4 at startup
player2.src('big_buck_bunny.mp4');

// user completed recording and stream is available
player.on('finishRecord', function() {
    // the blob object contains the recorded data that
    // can be downloaded by the user, stored on server etc.
    console.log('finished recording: ', player.recordedData);
});
</script>
</body>
</html>

And the resulting player looks weird, likely because it picks up the player styles for videojs-record:

click on the progress controls doesn't work.

I'm not able to reproduce this though..

While working on a fix, I also noticed this weird waveform render issue, bizarre.

There's also an issue in videojs-wavesurfer, opened https://github.com/collab-project/videojs-wavesurfer/issues/60 for that.

@Xteda87 upgrade to videojs-wavesurfer 2.5.0 and videojs-record 2.3.1 (or newer) to fix this.


Create FASSt simulation branch of OLMT for running natively on modex

This is the branch for running on modex natively:
https://github.com/FASSt-simulation/OLMT/tree/fasst


docs: refactor styles and accessibility fixes

What I did

Fixes padding issue
Corrects labelling of  element in shadowroot of uxdot-toc

Closes #1819
Testing Instructions

Notes to Reviewers

Can we get the same benefits without lifting markup and styles into the lightdom? Maybe use a complementary role on the host?

Can we get the same benefits without lifting markup and styles into the lightdom? Maybe use a complementary role on the host?

Maybe, the idea originally was to only have 1 aside, but if we lock the aside into the shadowroot then we also need to provide aria-label prop on the toc.  Also we were using it as a container for styling which is why the padding got wonky when it was moved into the shadow.
What real benefit does it serve to move it or use a complementary role?  I'd personally rather just use the semantic tag here so we have the
 cascade.  The toc is not IMHO an aside, it is the content of an aside. YMMV

need to provide aria-label -> accessible-label prop on the toc.

Not terrible, we're talking about <= 2 call sites

a container for styling which is why the padding got wonky when it was moved into the shadow.

I'm confident that with some juggling of styles this can be resolved all in shadow styles. one approach could be to make the host the container, and put the complementary role on it

What benefit

One stylesheet to rule them all. when issues come up with the toc, i want to solve them either in the css or in the template, encapsualted, abstracted away, with as little leakage into other moving parts as we can muster

i want to solve them either in the css or in the template, encapsualted, abstracted away, with as little leakage into other moving parts as we can muster

I feel like the way I have it already abstracts this given the separation of concerns of the semantics tags which are then styled for the layout.  The toc is only then inserted into that layout.  Maybe this is a Potaaaayto Potaaaaatoe... thing though.  I'll explore

Given a conversation with @adamjohnson on this we determined due to Best Practices it was better just to remove the  all together.  The aria-labelledby in the shadowroot of the uxdot-toc already provides enough surface for assistive technology and its best to avoid using aside inside the  landmark all together.
https://html.spec.whatwg.org/multipage/sections.html#the-aside-element

The element can be used for typographical effects like pull quotes or sidebars, for advertising, for groups of nav elements, and for other content that is considered separate from the main content of the page.

A heavy refactor would be needed to property incorporate a semantic usage of aside throughout the site given current layout constraints.

sounds good to me
can we lose the
? the host element should be able to handle the whole kebab

can we lose the ?

that is needed for grid-area: aside.  I'd rather not do that on the host element if we want to add another element to that region of the layout.
https://github.com/RedHat-UX/red-hat-design-system/blob/4ae9fd85ce42f3a89d069a747e0872343add99d3/docs/styles/pages/backpage.css#L60-L75

In that case put aside class on the host

In that case put aside class on the host

My preference is to have a container here still.

Reasoning:
If not for the best practices for screen readers not yet handling the 5.1 html spec of aside inside other landmarks, semantically the aside element would IMHO make the most sense.
My argument/position here is that the container .aside is separate from the toc itself.  The container  .aside could contain MORE than the just the toc as a child in the future and therefore the layout shouldn't be tied specifically to the toc host element.  In an attempt to make content abstracted layout styles.
If you feel that strongly in opposition to that position, please feel free to push the commit and resolve.

Fine by me


Simple Processing of Google Analytics Data

Tasks

[ ] Read downloaded GA data csv file from working directory
[ ] Remove initial lines from file
[ ] Fill in null values - replace with NaN in pandas
[ ] Re-format header names to lowercase and replace  " " with "_"
[ ] Read in numbers using the commas argument in pandas
[ ] Combine new data with existing data using pandas.combine_first to add / update previously saved data.
[ ] Write file to data/social directory named website.csv.
[ ] Create summary files and save in src/_data/metrics/website/

[ ] Aggregate values based on month (per Twitter)

webzite_stats.zip


/api/v2/status/logs does not query all log events

Describe the bug
I just upgraded to REST API v2.01 from 1.75. I can no longer query all system and firewall events.
To Reproduce
Steps to reproduce the behavior:
When querying https://pfsense.domain.tld/api/v2/status/logs/system (or firewall), the oldest event is always the first event in the current log file. Example:
Jul 13 15:08:00 pfSense newsyslog[83161]: logfile turned over due to size>500K
No events from the rotated log files are returned. If the query is run just after the log files are rotated, only a single result is returned.
Changing values for limit=0&offset=0 still only returns results from the current log file.
Expected behavior
The ability to query all log events like the UI does (https://pfsense.domain.tld/status_logs.php and https://pfsense.domain.tld/status_logs_filter.php)
pfSense Version & Package Version:

pfSense Version: 2.7.2-RELEASE
Package Version: 2.0_1

Affected Endpoints:

URL: /api/v2/status/logs/system
URL: /api/v2/status/logs/firewall

This doesn't look like a bug, both v1 and v2 only look at the most recent log file and don't attempt to decompress or look at log files that have already been rotated:
https://github.com/jaredhendrickson13/pfsense-api/blob/5db64cd7be7d236a0b5cd840a1768058e1b42d84/pfSense-pkg-API/files/etc/inc/api/models/APIStatusLogSystemRead.inc#L27-L32
https://github.com/jaredhendrickson13/pfsense-api/blob/b21981dd1f3aaf12234e9294c19331b0945c226b/pfSense-pkg-RESTAPI/files/usr/local/pkg/RESTAPI/Models/SystemLog.inc#L28-L39
In v1 this was intentionally done to prevent API calls from hanging when reading a large number of logs, but it's likely feasible to do this in v2 now that pagination is supported. I'll see if I can work it into v2.1.0.
Thanks!


loadUpdate is called once when no assets are loaded

An error in the documentation

Phaser version(s): v2.9.3

I log in state for testing state life cycle methods.The document says loadUpdate will call when there is some assets load in preload method. doc
It calls without assets load in preload.
I thought loadRender will always after loadUpdate. But when i add an asset in preload method it always more once loadUpdate before create method.

https://codepen.io/samme/pen/RQVwgK
Happens via Phaser.StateManager#loadComplete

@photonstorm do you remember what the "extra" loadUpdate call is for?
https://github.com/photonstorm/phaser-ce/blob/e08c3119be1db8deb99cda9b4d909578d777852e/src/core/StateManager.js#L601-L605

https://github.com/photonstorm/phaser-ce/commit/1c65c48341d67d490a76fdda21ad2f1c96425125
I think because Loader#reset is now called earlier, the last loadUpdate call actually receives Loader#progress 0 instead of 100. So maybe I'll just remove it.


Fix badges in readme

Fix badges to point to the main instead of the master branch.

Pull Request Test Coverage Report for Build 651197413

0 of 0   changed or added relevant lines in 0 files are covered.
25 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-2.5%) to 72.664%

Files with Coverage Reduction
New Missed Lines
%

dtf/validators.py
1
76.47%

dtf/templatetags/dtf/custom_filters.py
8
53.1%

dtf/api.py
16
84.64%

Totals

Change from base Build 646329550:
-2.5%

Covered Lines:
731

Relevant Lines:
1006

💛  - Coveralls


[20.09] pcsx2: multiple improvements

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/104850
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks for the backport! I guess you have omitted the latest update to PCSX2 due the dependency on fmt?

That's part of the reason, but I mainly wanted to keep things as stable as possible; the last update was only merged a week ago.

Closing due to issues with software renderer


RHIDP-3377: Adding cross-links to the Installation titles

IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.2, 1.3
Issue: RHIDP-3377
Reviews:

[x] Docs review: @hmanwani-rh

/cherry-pick release-1.3

/cherry-pick 1.2.x


highlight string formatting in strings

Would be great if we could highlight the python style string formatting differently inside of strings.

Sorry, I'm not sure I understand. Can you provide an example of what you'd like to see highlighted differently?

Sure, jsonnet uses python C style string formatting like this:
"value: %s" % [someVar]
I am proposing that we highlight those occurrences in the string, in this
example %s would be highlighted differently than the rest of the string
text.
Another example is: "value: %(someVar)s" % {someVar: "text"}
in this case the %(someVar)s would be highlighted differently than the text.
I can help with the regex to highlight all of the C style python formatting
possibilities (the jsonnet vim plugin uses special vim style regex style
that would need transformed slightly, but I know what ever part of it is
doing). I just am not familiar enough with the VS code extensions
configuration to help make that happen currently.
On Wed, Apr 5, 2017 at 3:36 PM, Alex Clemmer<EMAIL_ADDRESS>wrote:

Sorry, I'm not sure I understand. Can you provide an example of what you'd
like to see highlighted differently?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/heptio/vscode-jsonnet/issues/4#issuecomment-292017239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEJ7CWVRGg-C-2kohkM5D8AsF0T9I4_8ks5rtBd0gaJpZM4Mzm0f
.

--
Preston Podaril
卜大祿 ˙ 溥睿敦
<EMAIL_ADDRESS>

Ah, yes. This has been on my TODO list for awhile. I am hoping to get around to it soon.


Using adonis Request object instead of express Request in download and attachment

Hi, I see that you are currently refactoring some code there, but in 3.x version of adonis was the following code:
jsonp (body) {
  const callback = this.request.input('callback') || configInstance.get('app.http.jsonpCallback')
  nodeRes.jsonp(this.request.request, this.response, body, callback)
}
download (filePath) {
  nodeRes.download(this.request, this.response, filePath)
}
attachment (filePath, name, disposition) {
  nodeRes.attachment(this.request, this.response, filePath, name, disposition)
}

As can be seen in the jsonp method you pass this.request.request (express Request) to nodeRes, while in download and attachment, you pass this.request (adonis Request) that afterwards is passed to the send method in node-res:
Response.download = function (req, res, filePath) {
  send(req, filePath).pipe(res)
}

I believe send expects regular express request and response objects. So currently there is an issue with detecting not modified case, when browser sends if-none-match or if-modified-since headers. So we should either change node-res:
Response.download = function (req, res, filePath) {
  send(req.request, filePath).pipe(res)
}

or adonis Request:
download (filePath) {
  nodeRes.download(this.request.request, this.response, filePath)
}
attachment (filePath, name, disposition) {
  nodeRes.attachment(this.request.request, this.response, filePath, name, disposition)
}

Not sure which version you are referring to, but in 4.0, Adonis Response passes the native req object to nodeRes.
Also there is no usage of express anywhere in the framework

I refer to 3.0.14 version, but I see that download and attachment implementation didn't change in 4.0. So the issue should be there as well. You pass Adonis Response to nodeRes and from there directly to send module which, I believe, doesn't know about Adonis and expects express req and res objects.

Hey @stas-sl !
Actually, nodeRes is made by @thetutlage and doesn't expect to have any express object. It use the default HTTP Request & Response from Node.js...

Hmm, sorry for confusion. Everywhere I wrote "express request/response" should be read as "default Node.js request/response". Now I see that this part actually changed in 4.0, so this issue probably will not be applicable to it.
So it is applicable only to 3.0.14 because Adonis Response has reference to Adonis Request:
// Server/index.js

handle (req, res) {
  const self = this
  const request = new this.Request(req, res)
  const response = new this.Response(request, res)
  ...
}

which is later passed to nodeRes:
// Response/index.js

download (filePath) {
  // here this.request is Adonis Request
  nodeRes.download(this.request, this.response, filePath)
}

But I'm not sure if you plan to support 3.x version

@stas-sl Yes, 3.x will be supported for another 6months, so I will look into it and will fix it.

Closing


net: TestAcceptIgnoreSomeErrors is flaky on Windows

Flaky test noticed in trybot run https://storage.googleapis.com/go-build-log/9bd00409/windows-amd64-gce_98deed0d.log :
--- FAIL: TestAcceptIgnoreSomeErrors (0.34s)
	net_windows_test.go:126: recv failed: read tcp <IP_ADDRESS>:49346-><IP_ADDRESS>:49349: wsarecv: An existing connection was forcibly closed by the remote host.
FAIL
FAIL	net	3.165s

/cc @mikioh @alexbrainman for any ideas

Sent https://go-review.googlesource.com/#/c/9911/, but not addressed @alexbrainman' comments yet. Perhaps using internal/socktest might be enough because only thing we need to test here is simply observing that Accept never returns any errors when it receives broken connection requests from pending queue.

I can reproduce it on my windows-386 computer. So it was easy to fix https://go-review.googlesource.com/9942.
Alex


Laplace filter self-cal stacks to find OPEN pixels

After some discussion with the Euclid NISP folks, it may make sense to use a 2D Laplace kernel to make OPEN and ADJ_OPEN pixels stand out more in OpenPixelStep.  Convolving with a kernel something like:
[[0,  1, 0],
 [1, -4, 1],
 [0,  1, 0]]

before thresholding will make them stand out more.

Given that the central pixel is set to NaN in RampFitStep, this short-circuits the Laplace filter if run on the _rate or _cal files.  It might make more sense to make a stack from the first group of the constituent _jump files, i.e. before the pixel values are set to NaN for bad pixels.


Build failure: obs-backgroundremoval fails to build with CUDA enabled

Steps To Reproduce
Steps to reproduce the behavior:

Enable CUDA, CUDNN and unfree pacakges via

 nixpkgs.config = {
   allowUnfree = true;
   cudaSupport = true;
   cudnnSupport = true;
 };

Add CUDA-Toolkit and CUDNN to Sytem-Packages

cudaPackages.cudatoolkit
cudaPackages.cudnn

Add OBS and plugins to packages via

(pkgs.wrapOBS {
  plugins = with pkgs.obs-studio-plugins; [
    waveform
    wlrobs
    obs-backgroundremoval
    obs-pipewire-audio-capture
  ];
})

Build log
https://gist.github.com/RedEtherbloom/f427920f2f37f779ebdab5943e254363
Additional context
All other packages build normally.
OBS builds normally if we remove obs-backgroundremoval  from the plugin list.
Notify maintainers
@Zahrun
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.44, NixOS, 24.11 (Vicuna), 24.11.20240814.c3aa7b8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/store/sfycwi72zfjsspidinx56ajaiffpyh17-source`

(Channel output seems misleading, as we're running Nixos-unstable via flakes)

Add a :+1: reaction to issues you find important.

I'm not sure how to fix this, let's see if upstream has an idea https://github.com/locaal-ai/obs-backgroundremoval/issues/598


Error in azure cli code snippet in Step 2: Find the appropriate role

In "Step 2: Find the appropriate role", the azure cli reads:
az role definition list --name "{roleName}"

where is should read
az role definition list --name "roleName"

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

ID: 7c76fa79-5773-13f1-8672-7b20f847f926
Version Independent ID: f8ed8f66-3519-e823-7010-8e16cca8d4e4
Content: Add or remove Azure role assignments using Azure CLI - Azure RBAC
Content Source: articles/role-based-access-control/role-assignments-cli.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

My mistake... beginners error.

My mistake... beginners error.

@esciara Thanks for the update that it was just a reading mistake.

@esciara Thanks for the update that it was just a reading mistake.


Inpractical CompilerServices.Unsafe dependency

Hi, seems you're using the wrong dependency which is causing issues in our projects.
The better one would be
<EMAIL_ADDRESS>which is also available from OpenUPM (see here: https://openupm.com/nuget/)
Other packages also use the nuget dependency for maximum compatibility.
Alternative: don't specify any dependency and let people choose which version of it they use. The problem is that you're currently depending on an entirely different package name.
Thanks!

Yeap. Your comment is reasonable. I will find to way to apply that. Thank you 👍

related: #46

As you mentioned, It started to use org.nuget.system.runtime.compilerservices.unsafe
Thank you!

99f180be928756f41efb08a6c9f63cc993bbe87a


The Table under Service application accounts is broken

I presume the translation to markdown has destroyed this table--the information presented makes no sense. It appears that the nested table became broken, but I can't make any sense of the information at all.
https://docs.microsoft.com/en-us/SharePoint/security-for-sharepoint-server/plan-for-administrative-and-service-accounts#service-application-accounts

updated table..closing comment


Using with docker and ENV.fetch

When reading Docker For Rails developers, I got an issue when the database secrets were defined in env files:
#.env/development/database

POSTGRES_USER=postgres
POSTGRES_PASSWORD=
POSTGRES_DB=myapp_development

In a docker-compose.yml this file is referenced:
...
env_file:
      - .env/development/database
      - .env/development/web
...

and its values are fetched in a Rails app database.yml file as follows:
default: &default
  adapter: postgresql
  encoding: unicode
  host: <%= ENV.fetch['DATABASE_HOST'] %>
  username: <%= ENV.fetch['POSTGRES_USER'] %>
  database: <%= ENV.fetch['POSTGRES_DB'] %>
  pool: 5
  variables:
    statement_timeout: 5000

development:
  <<: *default
...

It seems like it comes in conflict with the Figaro way to use ENV variable.
If I drop  fetch:
default: &default
  adapter: postgresql
  encoding: unicode
  host: <%= ENV['DATABASE_HOST'] %>
  username: <%= ENV['POSTGRES_USER'] %>
  database: <%= ENV['POSTGRES_DB'] %>
  pool: 5
  variables:
    statement_timeout: 5000

development:
  <<: *default
...

it works on macOS but fails on a Linux machine:
rails aborted!
ArgumentError: Cannot load `Rails.application.database_configuration`:
wrong number of arguments (given 0, expected 1..2)
(erb):4:in `fetch'
(erb):4:in `<main>'
...

NOTE: I have no values defined in my application.yml file for DATABASE_HOST, POSTGRES_USER, POSTGRES_DB keys.
So the question is what is right way to do that ?  Thank you.
Figaro version: 1.1.1.

My bad, I figured out what was the error, - wrong syntax:
ENV.fetch['DATABASE_HOST']

should be
ENV.fetch('DATABASE_HOST')


Investigate methods of making the code safer

One of the issues with the current unsafe blocks is the complete lack of checking for
lifetimes or the existance of the underlying pointer.

One approach is to use Cell for the values which can be modified by a basis, which doesn't implement the Send or Sync traits which would be required.
Another check which is possible is dealing with lifetimes of the data being modified using a PhantomData field. This currently has the problem of mutability.
While I have ideas, it may be that a completely different approach is the most appropriate.


Proposal: Allow filtering hooks based on tags

Currently, hooks are scoped to key/s path, it can be cool to add a filter based on tags, that way we can have behaviors like notification only on keys that have "critical" tag or something similar.
Although it's also simple to implement in the receiver side.

Closed by #1209!


BUG: 11g SQL Script Accessing v$diag_alert_ext that do not exists

Description
11g SQL Script accessing v$diag_alert_ext that do not exists in this DBVersion
Version
No response
Priority
priority:0
What oracle database version are you seeing the problem on?
No response
Relevant log output
No response

Based on MOS note
How To Query Oracle X$ Tables From Another User Other Than SYS? (Doc ID 2009144.1)
and in some testing, we can't substitute the original view.
"grant select any dictionary" and "grant select any table"  also doesn't work.


opencv:x64-uwp has issue

Error: Building package opencv:x64-uwp failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: opencv:x64-uwp
Vcpkg version: 0.0.81-59792e9e463d3781c7b95d96c49e24e1f9b7f154

Hi, thanks for reporting this issue!
I'm unable to reproduce the problem locally; could you attach the package-x64-uwp-rel-*.log files mentioned in the error message?

Hi @bigdimboom , please open a new issue if this is still a problem for you.
Thx.


Jgit dependency through git client

Please don't merge this PR, this is just a proof of concept, a base to discuss.
After creating #48, I experimented with a potential solution, though I'm not certain if it aligns with Maven best practices.
Here's what I tried:

I believe I managed to fetch the jgit dependency with the same version as the git-client plugin by referencing its pom.xml.
(The project compiles successfully, which suggests it's working)

To keep this approach current, we would need to maintain the version number:
<git.client.version>5.0.0</git.client.version>``

Tools like Dependabot or Renovate could help us keep this version up to date.
What are your thoughts on this approach? I'm particularly interested in:

Whether this aligns with Maven best practices
Any potential issues or benefits you foresee
Alternative approaches we might consider

I look forward to hearing your feedback and suggestions.
Testing done
mvn clean install
Submitter checklist

[X] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[X] Ensure that the pull request title represents the desired changelog entry
[X] Please describe what you did
[X] Link to relevant issues in GitHub or Jira
Link to relevant pull requests, esp. upstream and downstream changes
[X] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Hey Bruno, I had tested the changes locally and seems to work fine. IMO Initially, we can stick to this and experiment other approaches like "utilizing updatecli" later.

Hey Bruno, I have inspected a few past PRs from Dependabot to update Jgit dependency in the Git-client-plugin. From my observation, I found that there are only regressions either related to the Jenkins core or the plugin itself. If I am not wrong, then using Dependabot in our tool will not cause any issue (Since, neither core nor plugin involved in our tool). wdyt? (Please correct me if I am wrong) Thanks!

I appreciate your perspective. Upon reflection, I realize that my previous suggestion was based on a gut feeling rather than concrete data.
Given this, I agree that we should proceed with the following approach:

Start by implementing Dependabot for our version management.
Monitor the results over the next few months.
If we encounter any issues, we can reassess our strategy and consider alternatives.

This approach allows us to:

Begin with a widely-used, automated solution
Gather real-world data on its effectiveness for our specific use case
Remain flexible and open to adjustments if needed

Does this sound like a reasonable plan to everyone? I'm open to any thoughts or concerns you might have.

Sure fine for me


REST API

Matt, they just released a REST module. Goodbye suds, goodbye SOAP!
https://www.reddit.com/r/msp/comments/h7ipu2/automating_with_powershell_autotask_psa_rest_api/

That is great news.  We've been off autotask for 2 years and maintaining this was going to become very difficult.

Appreciate the efforts in keeping this running. I admit, I actually started a rewrite to add impersonation support and static typing (parsing the WSDL to generate the library; eliminating init parsing for speed when used with serverless MS Teams add-ons).
I just did a quick and dirty benchmark of the REST vs SOAP APIs (accounts with 2 simple filters). Typically SOAP was 700ish ms; then after 2 consecutive requests, ~400ish ms. The REST API behaved the same but had a 100ms performance hit.
Reviewing the documentation, a good chunk of things are different regarding entities. Such as account being presented as "companies."
How does everyone feel regarding keeping a REST API implementation 1:1 with Autotask?

I'll be continuing with above. For the time being it will be another project entirely, as I can't really see practicality of mixing the two APIs into one library. And I'm not sure the semantics will be compatible.

... And to be frank I am not skilled enough to make much sense of the methods found in this library. That being said, I'd love to add impersonation support to python-atws for 1.6 parity, just not sure where to start.


UnhandledPromiseRejectionWarning: Error: You have declared using "bundled" babelHelpers

I'm using nextjs framework, and this is the error that I get when trying to generate the code.
 UnhandledPromiseRejectionWarning: Error: You have declared using "bundled" babelHelpers, but transforming /home/user/path.to.machine/file.ts resulted in "runtime". Please check your configuration.
packages:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Thanks for this @ivandotv
This is another error caused by bundling, that will be fixed when we move to a TS-only extraction process in this PR: #29
That PR is our top priority right now - we're testing it this week.
See comments in other issues: #21 and #23.
But let's try to find a workaround. Do you have a babel.config.js knocking about?

Actually I do ( I should have mentioned that  earlier)
const pkg = require('./package.json')
const childProcess = require('child_process')
const pkgVersion = `${
  process.env.PKG_VERSION || pkg.version
}-${childProcess.execSync('git rev-parse --short HEAD')}`

module.exports = {
  presets: ['next/babel'],
  plugins: [
    ['inline-react-svg'],
    [
      'transform-define',
      {
        __VERSION__: pkgVersion,
        __DEV__: process.env.NODE_ENV !== 'production'
      }
    ]
  ]
}

This is on top of nextjs babel config.
https://nextjs.org/docs/advanced-features/customizing-babel-config

Our current rollup-based machine extractor sometimes reads from babel.config.js, so playing with commenting out things in your config may yield some results. Obviously, that may not be a sufficient workaround.
If you can't find a workaround here, it might be worth waiting until #29 is in. We'll be releasing it on a @next branch and I'll make sure to notify you.

I can't mess around with the 'next/babelpreset. I will wait for the@next` release.
Using Typescript with xstate is such a pain.
Thank you for a prompt reply.

in my case the problem was conflict between @babel/transform-runtime(in my project) and @rollup/plugin-babel(in xstate-codegen)
im using webpack for app bundling, so the solution was not to use  @babel/transform-runtimeduringxstate-codegen` processing
in my .babelrc.js
if (process.title === "webpack") {
  plugins.push("@babel/transform-runtime");
}


GCA-Gender Classification API

Gender Classification API
I propose to contribute to FaceX with a deep learning API called "GCA" which is a simple REST API for classifying the gender of a human being based on facial features.

Served as a GraphQL and REST API
Given an image of a human face, the API should be able to classify the gender of the image based on the facial features with ~95.1% accuracy. The API will exist in two endpoints on a flask local server that will be running on port 3001 which can be configured during starting the server script. The endpoints will be:
http://<IP_ADDRESS>:3001/api/gender - REST

- OR
http://<IP_ADDRESS>:3001/graphql - GraphQL

Request can be send to the server using different API clients for example using cURL you can classify the gender by sending the following request to the server.
curl -X POST -F<EMAIL_ADDRESS>http://<IP_ADDRESS>:3001/api/gender

The expected response from the server will be as follows:
{
  "predictions": {
    "class": "male",
    "label": 1,
    "meta": {
      "description": "classifying gender based on the face of a human being, (vgg16).",
      "language": "python",
      "library": "tensforflow: v2.*",
      "main": "computer vision (cv)",
      "programmer": "@crispengari"
    },
    "predictions": [
      {
        "class": "female",
        "label": 0,
        "probability": 0.019999999552965164
      },
      {
        "class": "male",
        "label": 1,
        "probability": 0.9800000190734863
      }
    ],
    "probability": 0.9800000190734863
  },
  "success": true
}

Go for it @CrispenGari


middle time indicator position not correct when I rotate the simulator from portrait to landscape and then back to portait.

Tested in iPhone 5 iOS 8.1 simulator.

I'll try to look into this within a few days. Thanks for the clear bug report. I've worked around this by disabling rotation up until now, obviously not ideal.

Fixed in https://github.com/lyahdav/LIYDateTimePicker/commit/64cf66ea30a85396391c00db9505203874779f60.


Remove unnecessary parentheses in rules

Would be good if talonfmt could get rid of the unnecessary parentheses here, [show | hide] scratch: ...

# apps/i3wm/i3wm.talon
- [(show | hide)] scratch: user.system_command("i3-msg scratchpad show")
+ [show | hide] scratch: user.system_command("i3-msg scratchpad show")

Originally posted by @rntz in https://github.com/knausj85/knausj_talon/pull/947#discussion_r935215308

See #12 for a possible implementation.


Add typescript .d.ts declaration files

This pull request allows for easy use in typescript environments and for typechecking within vscode. Feel free to change the type signatures, but I think they are correct.
No changes to the actual runtime code were made.

Cool! Will we get a release with this soon?


Spoke Template has Hard-Coded References to US-East-1 Region

Team AWS / Limit Monitor Solution-
First and foremost - thanks for this helpful tool / solution.  We have multiple internal partners in our enterprise who are keenly interested in this service (and more).
We struggled a bit with the deployment - and along the way, found some hard-coded references in the Spoke Template which assume that the centralized (main template) resources in the Primary account are deployed in us-east-1.  At first, we simply  updated these references to point to us-west-2, where we had Deployed the primary stack in a centralized account.  When things didn't work, we cut bait, went back to the 'stock' templates provided in the Solution, and deployed everything in us-east-1.
Happy to submit a PR to address this hard-coded dependency - by either allowing the user to 'select' the region for the centralized / 'back-end' services -- or my changing the hard-coded references to intrinsic functions and just looking for those resources in the same region in which the spoke template is executed.
Thanks again for this Solution!  We hope to use it as a foundation, incorporating additional limit monitoring not currently provided by Trusted Advisor, but feeding into the same collection / notification / archiving back-end - and will be sure to offer any enhancements developed back to the solution in the form of a PR.

Hello,
Thanks for the valuable feedback. I would like to tell you that the solution essentially leverages AWS Trusted Advisor service limit checks. The TA checks uses us-east-1 as its data plane, implying you need to deploy the solution and spoke template in us-east-1 only. It will not work in any other region. That being said, it will monitor ALL regions even though it only allows us-east-1 deployment. Hope it helps. Please feel free to come back anytime should you have more questions.

@gsingh04 Outstanding!  Thanks for this confirmation / clarification.  It could be that this is clearly articulated within the Solution Deployment Guide - but we had four sets of eyes on it as we stood it up, and didn't come across that (totally makes sense) guidance / caveat.  Totally understand that the TA service reports across all regions.  Closing out this issue -- thanks again for the great work on this product!


Add ZeroNet support

Add support for ZeroNet site address. ZeroNet uses old-style Bitcoin addresses as site addresses.
Also see multiformats/multicodec#140. This PR depends on multiformats/js-multicodec#48.

@pldespaigne PR for adding ZeroNet to multicodec package was merged and released. I created tests and updated multicodec version to correct one. I also updated demo with better support for onion, onion3 and zeronet. Can you now merge this PR?

Hi @filips123 ! I don't have much time right now, but I will look at your PR before Sunday

@pldespaigne Can you now check this?

There is a conflict with README.md. Could you update this PR @filips123 ?

I'm closing this PR because since v2.4.4, all multicodec are being encoded to utf-8 as a fallback


Updated pipeline

updated pipeline to suit the new sm_cnn model
handled duplicate docs
PTB tokenized the candidate sentences
added a feature to obtain the JSON of terms and their corresponding IDFs.

@gauravbaruah please review


ClassGenerator and TraitUsageGenerator should implement TraitUsageInterface

As I noticed in #109 interface TraitUsageInterface is not used but code suggest that it should be used in classes ClassGenerator and TraitUsageGenerator.
@Ocramius what do you think? Can I create PR with this change?

Done in https://github.com/zendframework/zend-code/commit/ebf86ddb1a3574f7c27a20fdaeca26019dad45e9 and released in 3.2.0


Reduce the per-node overhead of edge lists in OnHeapGraphIndex

Sizes for building with Bench (32 degree * 1.2 overflow):
Raw data (NodeArray nodes, scores, and size fields but not the NodeArray class header or array references): 436 bytes
Before:
436 + 44 [NodeArray overhead] + 24 [AtomicReference overhead] + 72 [CNS overhead] = 576 bytes
After: 436 + 44 [NodeArray overhead] + 40 [CNM.Neighbor overhead] = 520 bytes
I also tried making CNM.Neighbor static, which I expected would reduce the overhead of those instances by eliminating the implicit reference to CNM.this, but it did not actually change the observed size in the heap dump, so I reverted the change.  (I'm still not sure why this did not make a difference.)

Round 2:

Neighbors is static again, this time for keeps
Neighbors extends NodeArray to save the object reference (in Neighbors) and the object header (in the NodeArray instance)
Delete shortEdges field and compute it during cleanup instead

This brings us to
436 + 60 [Neighbor overhead] = 496 bytes


Documentation Questions

This ticket will serve as a central hub for users, contributors, and maintainers to exchange ideas, seek clarification, propose improvements, and contribute to the overall quality of our project's documentation.  Whether you have questions about specific features, suggestions for clearer explanations, or ideas for expanding the documentation, this single ticket should be used.

It looks like there are no questions yet so we'll close this and open new tickets when specific questions arise.


[Fix] Change on-demand resources downloaded state criteria

Description
This PR fixes the ODR resource force unwrap not found problem described in #48
Linked Issue(s)

swift/issues/4199

How To Test

Do a fresh install and fresh build
When the samples app first open, check an arbitrary sample that has ODR, e.g.

Add raster from file
Add feature layers
Change camera controller
Display map from mobile map package

Make sure none of them crashes

To Discuss
I haven't been able to reproduce a crash with this fix. My gut says the root cause was that when NSBundleResourceRequest sets its progress to 100%, it is not immediately setting the isResourceAvailable to true, or it is dispatched onto the main serial queue whereas the state change is propagated to the view earlier than that. 🧐

One way to fix is to move the requestState = .downloaded to a later point.

According to the doc for beginAccessingResources(completionHandler:),

The resources are not available until the completion handler is called with error set to nil.

So when the try await request.beginAccessingResources() call returns, the resource must be available.

Another potential way to fix is to call the download() method again after the progress reported 100%, so it conditionally checks for the resource again.

Thank you! I was able to crash twice on v.next with random order of accessing these ODR samples, and haven't crashed yet with the fix. Will merge and keep an eye on any future crashes if there is any. 👀


Incorrect line ending for pyIPOPT/setup.py

I believe the CI is failing due to incorrect line ending -- the file in pyOptSparse uses CRLF line endings. This is something I have identified before but never bothered fixing. We can either:

Fix this in pyOptSparse and make a patch release, or
For now convert the patch in this repo to CRLF to match the line endings.

I would be happy with approach 1) but what do others think?

This is very odd. I did indeed have to make the patch have CRLF endings to make this work the first time around. But it is very odd that the this feedstock would have CI behavior that is different from the CI used on staged-recipes. Before patching source or recipe, let's see what gitter has to say...

Yeah I'm also surprised that the CI on the PR passed but this failed. Sounds good.


Constructor constraint not working for inherit classes

I'm trying create a concrete rep class extending a generic abstract class rep, but I've shown a syntax error where I can't put a class that obey the rules:
Type 'Bar' does not satisfy the constraint 'new (c?: Foo | undefined) => Bar'.
  Type 'Bar' provides no match for the signature 'new (c?: Foo | undefined): Bar'."

TypeScript Version:  3.4.0-dev.201xxxxx
Search Terms:
Constructor constraint, Extends constructor in a abstract class
Code
interface Foo {

    a: number;
}

class Bar {

    b?: number;

    constructor(c?: Foo) {

        if (c) {

            this.b = c.a;
        }
    }
}

abstract class RepBase<F, B extends { new(c?: F): B }> {

    doSomething() {

    }
}

class RepConcrete extends RepBase<Foo, Bar> {

}

Expected behavior:
Compile successfully
Actual behavior:
Syntax error
Playground Link:
https://www.typescriptlang.org/play/#code/JYOwLgpgTgZghgYwgAgGIHt3IN4FgBQByxycAXMiAK4C2ARtANwEC+BBCANnAM4-IAhOFBzt8JZHQD8FavSZiJCdCB5goVBGHRQAFAhlpMASlGFxEksBjJ9pvOctPkYABbAeAOjrIAvMgRPOGYLJzZQ5HDwsTg6NShEMADuPmQAJQgAByEeCAAeVAAaQWQIAA9IEAATfmxKCAB3fUNUYwoBSIA+MyISKvQAZXQaCDdQAHNde0USKLEuXn4MzIBhFQQoUZRyypr0rJz8jHRioShuhzEWIA

This is a question, not an issue you should use SO
for questions.
Hint: For starters, you are using the instance type instead of the class type

Sorry, I will close this issue.


Allow doplet device_type

Will allow the use of a droplet storage backend.
Will try to get back with another PR for configuring the droplet itself.

Support for droplet has been added via #116 .


PR10 with original formating

So only relevant changes from #10 with original formatting. it was reverted to the last your commit. and created branch and inside it added in NetBeans to have non touched original formatting.

sorry for complications. but git isn't my daily bread. in company we are still on svn.

Released via sonatype, should be available in a few hours on maven central


forgot to use std_ thingy in utils::impossible

In src_core_extensions/util.rs, there is this on line 177:
std::hint::unreachable_unchecked()

and it should be
std_::hint::unreachable_unchecked()

This broke my build when I went to update all my dependencies, lol.
(this change would be a PR if it were anything less trivial, but it's literally a single typo fix)

Thanks for pointing this out, I'll fix this within 24 hours and add testing of #[cfg(not(debug_assertions))] code like what broke your build.

Fixed this in 1.3.3


records for zarr downloads via API not showing up in s3 logs

Describe the bug
When downloading a zarr, I expect to see records in our s3 logs that correspond to the zarr file, chunks, and other metadata being accessed. I see these when using the AWS CLI. However when I download using the API, it seems only one record shows up, which is a single GET list-type call.
To Reproduce
Steps to reproduce the behavior:

Follow instructions to download a zarr tomogram using the API, e.g.,

from cryoet_data_portal import Client, Tomogram
client = Client()
tomogram = Tomogram.get_by_id(client, 11134)
tomogram.download_omezarr()

Make note of the tomogram and download time to easily find any corresponding records in s3 logs.
Navigate to the log file in s3://cryoet-data-portal-public-logs/logs to confirm what records there are for your download.

Desktop (please complete the following information):

OS: macOS 14.5

additional context from Ben: It's not really a blocker, but it could mean we aren't getting complete records of zarr downloads via the API. It could possibly extend to mrcs and annotations. And I'm not sure if we can backfill after a fix. So addressing it sooner would be better for our analytics.

The research for this issue is going to be time bound to 1 day, if we aren't able to identify the underlying bug within said time, we will have to sync on the priority of this.

@bnelson-czi - could you do a quick check to see if this bug is still valid?


Large number of watchers starts failing hard on OSX

We are running a fairly large project with 922 JavaScript and .less files being watched by Webpack's watch function on OS X (10.10.2) running on Node.js 5.2.0. After the initial build, when the watcher needs to trigger a rebuild, the following happens:
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop: failed to create the cffd
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamCreate: _FSEventStreamCreate: ERROR: could not open kqueue
2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamScheduleWithRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStart(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamStop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamUnscheduleFromRunLoop(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamInvalidate(): failed assertion 'streamRef != NULL'

2015-12-10 18:01 node[76106] (FSEvents.framework) FSEventStreamRelease(): failed assertion 'streamRef != NULL'

I wonder if this may be related to #387 and we are simply hitting maximum open files limitations. Any other ideas I'm also open to, because this is a massive blocker in our development process and is affecting multiple people at once.

Did you raise the open file descriptor limit (see ulimit)? (Node used to do it automagically, but I'm not sure if that is the case now)

/cc @indutny

ulimit currently says unlimited, but I'm not sure I can trust that. I'm going to try and pull #641 and roll a Node.js build on top of that, see if the problem goes away.

Do a ulimit -a and check for "open files", or do uname -n.

Thanks (I feel like a noob now). 1000 is the answer. And we're watching 922 files. Add some other running apps to that, and it's likely we're hitting a limit there.

If #641 solves it (I should know soon enough), I hope that can make it into the next release.

I compiled and tried to run it, but the output is exactly the same, which is really odd because the error mentions kqueue, while the commit message in #641 says it should not be using kqueue at all anymore.

@ronkorving note that the error comes from the OSX framework itself. kqueue does work with file fds, so FSEvents is probably using kqueue underneath and running into the fd limit anyway. Did raising the limit with ulimit -n 10000 avoid the issue?

The office has closed, so I will have to try with someone tomorrow. We tried to bump it, but it wouldn't let us... I'm sure there's a way, but I don't know that way off the top of my head. Will have to postpone until tomorrow I'm afraid.

No worries.

@ronkorving this is unfixable, OS X has a global OS limit. Sorry!

Ah, wait... This is something different. (Gosh premature commenting)

@ronkorving seems to be ulimit -n problem.

We doubled the ulimit to 2000, and the same errors appear. So it seems unrelated to this error.

What does your code do? Use fs.watch on a thousand different files?
Can you come up with a test case which consists just of core modules?
On Dec 11, 2015 02:10, "Ron Korving"<EMAIL_ADDRESS>wrote:

We doubled the ulimit to 2000, and the same errors appear. So it seems
unrelated to this error.
—
Reply to this email directly or view it on GitHub
https://github.com/libuv/libuv/issues/645#issuecomment-163801174.

I could give it a shot, but right now (for the sake of the project) I'm focused on non-watch fast build solutions in Webpack (which, thank god, exist). What is happening behind the scenes in Webpack exactly, I don't know, but I can look into that.

It seems it's using chokidar behind the scenes. You may be familiar with it?
source: https://github.com/webpack/watchpack/blob/master/lib/DirectoryWatcher.js#L7

No, I'm not familiar with that. I see it uses fs.watch* and fsevents, but I see nothing we can fix from libuv.

We upped the ulimit from 1000 to 3000, and the same errors appear. So it seems unrelated to this error.

Note that the limit applies to the current shell, so if you run ulimit in a shell and start node in another, that limit won't apply.

We ran the whole process in the shell where limit was raised 3000.
In any case, I guess it really is out of the hands of libuv... I'll close the issue and pursue my dreams elsewhere ;) I made an issue over at the Webpack project. We'll see if we can make any progress going from that angle.

Okidoki! Just to discard culprints, you could try the following: create a test which creates a directory and 1000 files insise. Then create a watcher for each with fs.watchFile, and see what happens.

Also, make sure you use a Node version which has libuv >= 1.7.0, which includes this patch: https://github.com/libuv/libuv/commit/7980f1359dd16e8ded20a80e934deaf269d85f03

I used latest Node with #641 merged into it, and the problem didn't go away, so I guess that patch was also a part of it. Over the weekend I explored an alternative for Webpack builds that gives us the same speed, but doesn't require watchers (build-on-demand with caching), so the team is happy again.
I'll create the test you ask for and see if I can replicate the issue though.

Well, I wrote a little test that watches thousands of files and folders, and can't get it to blow up... Not even with stock Node :-/

@ronkorving Oh. I'll tentatively close this then, since there is nothing we can do. If you manage to narrow it down, leave a comment and we can reopen it.

Sounds good.


Fix animation listener docs

Description
Updated animation listener docs(addListener and removeListener) as its real behavior.
Related Issues
Fixes #32114
Tests
None, only docs were changed.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

It doesn't really make sense to notify listeners when the value doesn't change. Instead of updating the docs, we should see if we can fix the behavior to match the docs.


Improve first-run microphone permissions experience and UX

This change improves the first-run experience, and subsequent UX, for working with the microphone.
There are some browser differences in how permissions get handled, but I think I've now covered them all.
On Chrome-based browsers, you can approve the microphone and have it persist over sessions.  Firefox refuses to do this, so you always have to grant it again.  Safari is somewhere in the middle.
I've done the following:

Added a check to see if audio recording and transcription are supported at all in the browser/session
Added a function to check for permissions before we start recording.  If we don't have permission, it tries to get it first before we start recording
Added better error messages when things fail
Updated the status text we show above the prompt for to indicate if we're recording or transcribing
Updated the prompt text to indicate how the mic works
Added help info about the mic and how to use it.

I'm unable to get the browser to not show a "Recording" icon.  This seems to persist for the session where you grant access (i.e., it's not something JS can affect).

https://github.com/tarasglek/chatcraft.org/assets/857083/91285c38-86e5-426a-a3b1-1ec195226a00
Permission dialog still messes us up.

Initial experience frustrates me.
I played with permission checking, ended up with this: https://mic-permissions.console-overthinker-dev.pages.dev/c/chatcraft_dev/55hOzNp8shj_YmOAfEUJW
Only firefox takes us down the "unknown" path. Webkit-based stuff seems to return "prompt", "denied", which is helpful. Can display proper mic icons from get go and not get into mouse-down state if we don't have permissions.
We can then simplify state machine for sane webkit behavior and have a fallback "unknown"  path as it.basically works right now for firefox.

Note this is still an improvement, i'm ok landing this in meantime

Alright, I'm going to land and keep iterating.


Add methods for SimpleGraphs and associate tests

Codecov Report

Merging #3 (9b4a288) into main (6ed35e7) will increase coverage by 2.59%.
The diff coverage is 86.53%.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   70.99%   73.58%   +2.59%
==========================================
  Files           5        5
  Lines         131      159      +28
==========================================
+ Hits           93      117      +24
- Misses         38       42       +4

Impacted Files
Coverage Δ

src/rastergraphs.jl
92.43% <86.53%> (-2.13%)
:arrow_down:

src/structs.jl
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Support expression for latch.

is this ready for review?

No, there is a problem with the namespace. During machine instantiation, we need to change the namespaces to the instantiation point (plus a suffix for the machine). I have the feeling that this could be one in a better way with functions returning constraints and columns.


[stable/external-dns] Add Bitnami team as maintainers.

Signed-off-by: juan131<EMAIL_ADDRESS>What this PR does / why we need it:
stable/external-dns currently lacks of maintainers. This PR adds Bitnami team (@carrodher @tompizmor @jsalmeron @juan131 @sameersbn @prydonius) as maintainers of the chart.
Which issue this PR fixes

fixes #14861

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

cc/ @maorfr

/lgtm


lay-out error in syntax

In first syntax blok 2 parameters on one line
-DomainName [-SafeModeAdministratorPassword ]
should be on 2 lines
-DomainName
[-SafeModeAdministratorPassword ]

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

ID: 5a368613-76f6-7260-de11-c9339dd4747e
Version Independent ID: 4700a39a-5694-1d2d-e166-354704cd19f3
Content: Install-ADDSDomainController (ADDSDeployment)
Content Source: docset/winserver2022-ps/addsdeployment/Install-ADDSDomainController.md
Product: w10
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hmm, I see now there are multiple lay-out errors where there are 2 parameters on the same line in the first block. No wonder it is shorter, please fix them all. ;-)


test: Ignore waitqueue.waitingLoop goroutine leak

We use goleak in certain tests to ensure we do not leak goroutines which might cause unexpected behavior during tests or shutdown in production.
Normally we expect our own goroutines to leak, but since we started using the delayed workqueue, we also leak the waitqueue.waitingLoop. This goroutine does get a shutdown signal when hive stops, but it isn't guaranteed to have exited before hive does so it sometimes triggers in CI.
This PR adds and exception to all goleak invocation that use resource.Resource[T] to ignore the waitqueue.waitingLoop goroutine.
Fixes: #28477
Add workqueue.(delayingType).waitingLoop to goleak exception list

/test

@dylandreimerink looks like v1.14 is also seeing hitting this (https://github.com/cilium/cilium/actions/runs/6850169361/job/18623961162). Any concern about backporting - and if so, how far?

Had not considered this might impact older releases, but backporting this should be easy, adding the label now


pgt-api-server improvements

Hello there!
I have forked your repository and improved the API used by dh-make-golang to create new Salsa project. In the meantime I have fixed almost all TODOs that were in the file, and use a dedicated web framework to ease the development.
Prometheus metrics may be easily implemented now, using an existing plugin.
I need to test the whole flow to confirm that everything's work as before, and rework the logger format.
I don't know if you may be interested in the following PR, just let me know :)
Cheers

Thanks for your PR!
I don’t see the need to adopt a web framework for this tiny service. Which actual issues are you solving with that?
In general, improvements are fine, but please don’t rewrite everything in one giant commit. Instead, send commits which are as small as possible and fix actual issues.
I’m currently running this service, but want to hand it off to someone else. See https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/ for details. To keep ops overhead low, I’d like to minimize changes.

Hi back @stapelberg,
My idea behind the echo refactoring was to introduce a "better/proper" codebase to ease later improvements, it does not solve any issue at all. (I know it sounds overkill)
Using the framework I have written the "repo info extraction middleware" to centralize the logic (was one of your TODO), as well as a middleware for rate limiting, (no more global variables). Echo as built-in support for Prometheus btw, so it may be easier for you to implement it. (Was one of your TODO)
But I do totally understand your point of view, the service is not meant to grow in the futur, and therefore this will refactoring will more painful than anything else.
I just wanted to know if you were open to these kind of improvements. I have just started contributing for Debian, and want to help refactor / improve existing codebase and fixe issues.
Sorry to hear you're leaving Debian, I understand your opinion.

Thanks for the details!
I think it’s great that you want to contribute. Maybe ask on the Debian Go team mailing list what the best thing to contribute to is right now? :)


run all repro tests in different CI job

Component
Forge
Describe the feature you would like
A lot of repro tests make use of forking and can lead to stalled CI
TODO

add new nextest run job that only runs repros
exclude them in the existing runner

cc @Evalir do you want to try this?
this is how filters are set:
https://github.com/foundry-rs/foundry/blob/dd58c32c2c153d5d9cde55d03b8830a44321d4ba/.github/workflows/test.yml#L90-L90
Additional context
No response

yup happy to take this on!


[cm] list continuation indentation

Current state

We add styles so that continuation lines are indented in lists.
The markdown extension adds the space after the list mark to the beginning of the following Paragraph node; we subtract 0.25em to account for this, but this causes the cursor and selections to be indented incorrectly.

  1.
   Hello world

Question

Can we modify the markdown parser so that the space following the - list item is included into the token parsing?
It might be better if a list mark "-" that isn't followed by a space is not parsed as a list mark. E.g., I've tried modifying the parser to achieve this, but haven't been able to do this?

UPDATE

I have things working as desired by changing the decoration ranges so that the whitspace is removed; I'm a little uneasy that the decoration ranges are now not aligned with the token ranges. Things seem to be stable, but it might be working against the intended system?

https://github.com/dxos/dxos/pull/7680
    const newParser = parser.configure({
      parseBlock: [
        {
          name: 'ListItem',
          parse: (cx, line) => {
            // Check if space after -- but what to return?
            return true;
          },
        },
      ],
    });

I'm a little uneasy that the decoration ranges are now not aligned with the token ranges.

No that's absolutely not a problem.
I did not really manage to understand the initial source of the issue here. But if you've found a workaround maybe that's not relevant anymore anyway.


Make public?

Would be great to:

Open source this
Add an example to https://github.com/mapbox/mapbox-react-examples that uses this
As a follow up from https://blog.mapbox.com/mapbox-gl-js-react-764da6cc074a write a blog post on syncing React, Redux, and Mapbox GL JS.

Reopening for these security checks, per https://github.com/mapbox/open-source/issues/18:

[ ] Check README and documentation for any Mapbox-isms with sensitive information
[ ] Check code for sensitive information (e.g. hard coded credentials, comments with sensitive info)
[ ] Check tests

[ ] Check for any fixtures using live data
[ ] Check for any testing or debug URLs

[ ] Check open AND closed issues for any sensitive information
[ ] Check open AND closed PRs for any sensitive information
[ ] Check code, tests, and documentation on other branches


OpenCDMS App layout

The initial application should follow the layout in the image below. Theming, including colour choice and icon sets can be decided later.

The png image below contains the current logo with transparent background (the white text can only be seen on darker backgrounds)

Closed by #6


Uml 190 store user in session

Depends on 189.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #107   +/-   ##
=========================================
  Coverage          ?   57.82%
  Complexity        ?      423
=========================================
  Files             ?       52
  Lines             ?      946
  Branches          ?        0
=========================================
  Hits              ?      547
  Misses            ?      399
  Partials          ?        0

Impacted Files
Coverage Δ
Complexity Δ

...ervice-front/app/src/Common/src/ConfigProvider.php
0% <ø> (ø)
4 <0> (?)

...nt/app/src/Common/src/Service/ApiClient/Client.php
0% <0%> (ø)
30 <0> (?)

service-front/app/src/Common/src/Entity/User.php
100% <100%> (ø)
7 <7> (?)

...ce-front/app/src/Common/src/Entity/UserFactory.php
100% <100%> (ø)
1 <1> (?)

...src/Common/src/Service/User/UserServiceFactory.php
100% <100%> (ø)
1 <1> (?)

...nt/app/src/Common/src/Service/User/UserService.php
69.56% <100%> (ø)
9 <6> (?)

...ont/app/src/Actor/src/Handler/LoginPageHandler.php
93.33% <80%> (ø)
5 <0> (?)

Continue to review full report at Codecov.

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


searx Agent support

Thanks for publishing this, I started to read the codebase for Marvin and langchain a few days ago and was in desperate need of something simpler.
If you take requests for agents I would like to kindly ask for searchx support. It can be self hosted, or given that searx is a python package even just imported to avoid the network call! By doing that we could have access to a lot of plugins like Github and Wolfram without writing all those agents.

Maybe you can write a pull request with a tool which implements searchx?
Happy to add it then.


Pass environment

As requested in https://github.com/github/octocatalog-diff/issues/35, this pull requests adds the ability to compare compiled Puppet catalogs by varying the environment used for compilation.
Details are in the added document: https://github.com/github/octocatalog-diff/blob/1d5a238350282d1bcab628091c433d4eaf2d8ba6/doc/advanced-catalog-validation.md
Fixes https://github.com/github/octocatalog-diff/issues/35.

Hey @tobias-urdin this is for you (the feature you requested, with some other stuff merged into it that will be released soon).
Can you take a look at https://github.com/github/octocatalog-diff/blob/1d5a238350282d1bcab628091c433d4eaf2d8ba6/doc/advanced-catalog-validation.md and try this out to see if it'll do what you need?


document e-mail setup (smtp)

Mailgun differs from the SMTP option. Mailgun uses API keys (panel.email.key) and does not use the username and password fields.

Ok, i'll document that too

Changed it from SMTP setup guide to e-mail setup guide
Added mailgun-specific instructions


Documentation about Third Party Libraries

I think it would be valuable for the community if we have a dedicated page within the rxjs docs for third-party tools. So that we have a recommendation for tools like:

rxjs tslint
rxjs spy
redux observables
...

I think we can collect via https://github.com/ReactiveX/rxjs/discussions/categories/show-and-tell . Not sure that'd be suffecient, or we want separate pages.

I think we can collect via https://github.com/ReactiveX/rxjs/discussions/categories/show-and-tell . Not sure that'd be suffecient, or we want separate pages.

Closing because we now have: http://rxjs.xyz/


Grenade! (huge reformat of the source code)

This is a once-in-a-lifetime move, source-code wise. It's
necessary to start enforcing good coding practices but we
won't be able to pull this off even once more, as future
patches will be an horrible mess to read.
This means you are hereby given the great task and
responsibility to follow and enforce the coding practices
that have been chosen. Make us proud!
Please note the formatting to complies to LLVM standards and not Mozilla's, see my latest comment on issue #14

looks nice!


Initial support for local schema file

This patch improves the gems GraphQL efficiency two:

Reuse the scheme produced in previous calls
Keep a local copy of the schema's JSON (Optional)

NOTE: PR #525 takes a similar approach, but may offer safe multi-session support.
Problem
The current implementation of ShopifyAPI::GraphQL.new results in a download of the Shopify API GraphQL scheme for each call to new. The schema is 2.5MB. The data must be parsed into a GraphQL object. An example of the download/parse behaviour:
client = ShopifyAPI::GraphQL.new
# wait 15 - 30 seconds as the Shopify server streams the JSON to the client, and client parses
client = ShopifyAPI::GraphQL.new
#  repeat everything from the top

The patch keeps the parsed schema as a class attribute. Therefore, the the network request is performed once.
# calls server for JSON schema. Saves results into a class attribute
client = ShopifyAPI::GraphQL.session(shop.name, shop.token)

# Uses the class attribute to avoid network request.
client = ShopifyAPI::GraphQL.session(shop.name, nil) # Uses class

Store the schema on local filesystem
Further performance improvements can be made by storing a copy of the schema's JSON on the local filesystem. Set the  ShopifyAPI::GraphQL.schema_file class attribute to a file. If the file does not exist, it will be created when the schema downloads. If the file does exist, the class will load the file and parse its contents into the GraphQL schema.
Session 1: Download schema and keep a local copy (assumes file does not exist).
ShopifyAPI::GraphQL.schema_file = "local_schema.json"
client = ShopifyAPI::GraphQL.session(shop.name, shop.token)
exit

Session 2: Use the local file. Avoid download.
ShopifyAPI::GraphQL.schema_file = "local_schema.json"
client = ShopifyAPI::GraphQL.session(shop.name, shop.token)

Limitations
There may be a need for a Mutex around two pieces. One is the schema download. The other is around the Session.active.

Can you please add more to the PR description. Both the reason why you need this and how you implemented this.

cc @Shopify/api-patterns-team

Thanks for the great start on this @raydefy. Before reviewing the code in depth my main concern is around the API being exposed. Currently we recommend people created a new ShopifyAPI::GraphQL client after the usual session management:
shopify_session = ShopifyAPI::Session.new(domain: "SHOP_NAME.myshopify.com", token: token, api_version: api_version, extra: extra)
ShopifyAPI::Base.activate_session(shopify_session)

client = ShopifyAPI::GraphQL.new

SHOP_NAME_QUERY = client.parse <<-'GRAPHQL'
  {
    shop {
      name
    }
  }
GRAPHQL

result = client.query(SHOP_NAME_QUERY)
result.data.shop.name

Right now with this PR it would be:
client = ShopifyAPI::GraphQL.session(domain: "SHOP_NAME.myshopify.com", token: token)

SHOP_NAME_QUERY = client.parse <<-'GRAPHQL'
  {
    shop {
      name
    }
  }
GRAPHQL

result = client.query(SHOP_NAME_QUERY)
result.data.shop.name

This might be confusing introducing another thing named session which is a wrapper around the existing one; except it also has less functionality right now. Is it possible to keep the existing functionality by just instantiating a client via new? Or maybe introduce a new method like client_from_session(shopify_session).
My other question is for the schema_file attribute. It's overloaded with two concerns right now:

local filename to save when the dynamic schema is fetched
local filename to use as the cached schema

Two separate attributes might be clearer. Something like:
ShopifyAPI::GraphQL.save_schema_file = true
ShopifyAPI::GraphQL.schema_file_path = 'schema.json'

This provides an explicit opt-in/out.


[ISSUE #3303] [type: refactor] refactor shared thread pool

this PR only refactor shared thread pool.

Codecov Report

Merging #3315 (db88ec5) into master (dfd5cb3) will decrease coverage by 0.19%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3315      +/-   ##
============================================
- Coverage     64.40%   64.21%   -0.20%
+ Complexity     5178     5169       -9
============================================
  Files           742      743       +1
  Lines         20957    20960       +3
  Branches       1919     1919
============================================
- Hits          13498    13459      -39
- Misses         6183     6217      +34
- Partials       1276     1284       +8

Impacted Files
Coverage Δ

...enyu/common/concurrent/MemoryLimitedTaskQueue.java
0.00% <0.00%> (ø)

...yu/common/concurrent/ShenyuThreadPoolExecutor.java
0.00% <0.00%> (ø)

...org/apache/shenyu/common/concurrent/TaskQueue.java
0.00% <0.00%> (ø)

...b/configuration/ShenyuThreadPoolConfiguration.java
0.00% <0.00%> (ø)

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.25% <0.00%> (-9.58%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
78.04% <0.00%> (-5.70%)
:arrow_down:

...he/shenyu/plugin/grpc/client/ShenyuGrpcClient.java
8.00% <0.00%> (-4.00%)
:arrow_down:

...yu/common/dto/convert/rule/Resilience4JHandle.java
71.60% <0.00%> (-3.71%)
:arrow_down:

... and 42 more

Continue to review full report at Codecov.

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


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 9d532cb, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 9958 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in 1304030.


WebGPU: Fix bug introduced by #14378

A render target format has been removed by mistake in #14378, making the highlight layer (and probably other things!) fail.

Snapshot stored with reference name:
refs/pull/14384/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14384/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14384/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14384/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14384/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14384/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14384/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14384/merge#BCU1XR#0


dynamically allocate num_gpu

When running a model on a system with a gpu available dynamically set num_gpu to load a reasonable amount of layers to gpu (based on mem required).

Resolved in #454 and #591


doc: boards: arm: nrf52840_pca10059: fix instructions for flashing

The instructions for flashing the board using nrfutil were incorrect.
CC: @jhedberg

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b0c71af). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #13529   +/-   ##
=========================================
  Coverage          ?    52.5%
=========================================
  Files             ?      318
  Lines             ?    46527
  Branches          ?    10755
=========================================
  Hits              ?    24429
  Misses            ?    17199
  Partials          ?     4899

Continue to review full report at Codecov.

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

@carlescufi could you take a look and see if this can be merged?


[Question] parseData gives unexpected notification element

We installed some modules on sysrepo containing the following snippet:
module my-types {
  identity APP-TYPES {
  	description "Application types.";
  }

  identity CLIENT {
    base APP-TYPES;
  }

  identity INTERNAL {
    base APP-TYPES;
  }

  typedef app-types {
    type identityref {
      base APP-TYPES;
    }
  }
}

module my-module{
  ...
  import my-types { prefix "my-types"; }

  notification application_new {
    container application {
      leaf app_type {
        type my-types:app-types;
      }
    }
  }
}

during some tests we tried to create a notification from a json file
std::string json(R"({
  "my-module:application_new": {
    "application": {
      "app_type": "my-types:CLIENT"
    }
  }
}
)");
    auto node = session.getContext().parseData(json, libyang::DataFormat::JSON);

This leads to a crash with the following error:
libyang[0]: Unexpected notification element "application_new". (path: Schema location "/my-module:application_new", line number 2.)
FAIL!  : TestAgentQt::TestBuildNotifString() Caught unhandled exception

Using newPath()/newPath2() to create the notification node by node works, but receiving the data as json objects would be easier to parse them.
Am I missing something?

These have to be parsed in a special way, via libyang's lyd_parse_op(). We have a wrapper for this (Context::parseOp and DataNode::parseOp), but so far we've only wrapped these for XML-serialized RPCs and their replies. Let me look into this.

Can you try this patch? https://gerrit.cesnet.cz/c/CzechLight/libyang-cpp/+/6416

Thank you for your fast reply.
I downloaded and applied the patch but seems it doesn't build.
The problems seems to be that OperationType::NotificationRestconf called at line 188 of Context.cpp is missing form OperationType enum class in Enum.hpp at line 52.
Added this I could build the repo and use it.
I still get
libyang[0]: Invalid argument parent (lyd_parse_op_()).

but it might be a bad format of the notification by my part, I'm currently checking it.
I need a clarification though, if I want to send the notification with sysrepo on session.sendNotificaton() a DataNode is required. Is this the tree or the op field of the returned ParsedOp?

Oops, it's actually a series of patches, you'll need:

https://gerrit.cesnet.cz/c/CzechLight/libyang-cpp/+/6415/1
https://gerrit.cesnet.cz/c/CzechLight/libyang-cpp/+/6416/2
https://gerrit.cesnet.cz/c/CzechLight/libyang-cpp/+/6418/1

Nice timing, i pushed these just a minute ago :). Can you please check the doxygen comments in these patches and report back if it's all clear now? You can find some extra information and usage patterns in the test suite, but please let me know if the docs can be made any clearer.

Also, the error path is probably wrong, there's very likely a memory leak. But I need CESNET/libyang#2077 fixed first to actually test the exception handling. In the meanwhile, I would not run this on untrusted input :).

Thank you for your time, with the new patches all our tests pass now.
The documentation seems perfectly clear.
You just gained a new follower. :)

Quick note.
Given the following notifications:
{
    "ietf-restconf:notification" : {
        "test:eventTime" : "2013-12-21T00:01:00Z",
        "test:application_new": {
            "application": {
                "app_type": "my-types:CLIENT"
            }
        }
    }
}
{
    "ietf-restconf:notification" : {
        "test:application_new": {
            "application": {
                "app_type": "my-types:CLIENT"
            }
        },
        "test:eventTime" : "2013-12-21T00:01:00Z"
    }
}

the first gets parsed while the second throws an exception.
Since the JSON represents the same data I would expect that they would be both parsed without problems.
Is this a bug or a feature? Is there some kind of parameter order enforcing that I'm not aware of?

Your example has test:eventTime instead of the eventTime (which is a sohrthand for ietf-restconf:eventTime) -- but apparently that doesn't matter. Anyway, this is not a bug in the C++ bindings, it's something form the C library. I filed this at CESNET/libyang#2080.


sbom: drop sha1 file checksums

Melange Pull Request Template
This drops sha1 from generated sbom checksums.
I don't know if this works, and if this still passes the ntia scanner audit.
This still keeps sha1 usage in the verifcation code which is specified as sha1.
Functional Changes

[ ] This change can build all of Wolfi without errors (describe results in notes)

Notes:
SCA Changes

[ ] Examining several representative APKs show no regression / the desired effect (details in notes)

Notes:
Linter

[ ] The new check is clean across Wolfi
[ ] The new check is opt-in or a warning

Notes:

Hahaha

checksums must contain a SHA1 algorithm checksum, but only contains: [<ChecksumAlgorithm.SHA256: 3>, <ChecksumAlgorithm.SHA512: 5>]

Spdx 3 deprecates lots of things so will be dropped then.


Javadoc?

Is the case of publishing Android libraries and its javadoc supported?

Of course, it is supported. You have to define javadocsJar task with dokka or javadoc task and have to add to artifacts
publications {
            mavenAar(MavenPublication) {
                from components.android
                    artifact LazyPublishArtifact(javadocsJar)
                    artifact LazyPublishArtifact(sourcesJar)
            }
}

@warnyul Thanks for the quick reply!
We have a specific case that I will try to explain which makes this problematic.
We want to upload both snapshot versions and release versions. Our build script applies different configs depending on whether the build is of variant DEBUG och RELEASE.
Using your approach, we noticed, leads to the artficats always applying the RELEASE config.
This is our conf that works for us (but it doesn't upload the javadoc):
 ```

publications {
android.libraryVariants.all { variant ->
"maven${variant.name.capitalize()}Aar"(MavenPublication) {
from components.findByName("android${variant.name.capitalize()}")
groupId project.group
artifactId 'cliq-connect-sdk-android-' + project.name
version project.version
}
}
}

@alixwar - You'd just take this section from waryul's comment and add it to your own:
 artifact LazyPublishArtifact(javadocsJar)
artifact LazyPublishArtifact(sourcesJar)

So it'd come out as something like this:
publications {
    android.libraryVariants.all { variant ->
        "maven${variant.name.capitalize()}Aar"(MavenPublication) {
            from components.findByName("android${variant.name.capitalize()}")
            groupId project.group
            artifactId 'parent-project-' + project.name
            version project.version
            artifact LazyPublishArtifact(javadocsJar)
            artifact LazyPublishArtifact(sourcesJar)
        }
    }
}

@Nunnery that doesn't work

org.gradle.internal.metaobject.AbstractDynamicObject$CustomMessageMissingMethodException: Could not find method LazyPublishArtifact() for arguments [task ':core:javadocJar'] on object of type org.gradle.api.publish.maven.internal.publication.DefaultMavenPublication.

Note: These are the tasks that I have defined:
tasks.withType(Javadoc) {
    options.addStringOption('Xdoclint:none', '-quiet')
    options.addStringOption('encoding', 'UTF-8')
    options.addStringOption('charSet', 'UTF-8')
}

task sourcesJar(type: Jar) {
    from android.sourceSets.main.java.srcDirs
    // https://discuss.gradle.org/t/how-does-property-class-work-in-build-configuration/30320
    archiveClassifier = 'sources'
}

task javadoc(type: Javadoc) {
    source = android.sourceSets.main.java.srcDirs
    classpath += project.files(android.getBootClasspath().join(File.pathSeparator))
}

task javadocJar(type: Jar, dependsOn: javadoc) {
    from javadoc.destinationDir
    // https://discuss.gradle.org/t/how-does-property-class-work-in-build-configuration/30320
    archiveClassifier = 'javadoc'
}

artifacts {
    archives javadocJar
    archives sourcesJar
}

Then remove the LazyArtifactPublish wrapper or add the import for it.
On Fri, Mar 29, 2019, 12:25 PM Alix<EMAIL_ADDRESS>wrote:

@Nunnery https://github.com/Nunnery that doesn't work
org.gradle.internal.metaobject.AbstractDynamicObject$CustomMessageMissingMethodException:
Could not find method LazyPublishArtifact() for arguments [task
':core:javadocJar'] on object of type
org.gradle.api.publish.maven.internal.publication.DefaultMavenPublication.
Note: These are the tasks that I have defined:
tasks.withType(Javadoc) {
options.addStringOption('Xdoclint:none', '-quiet')
options.addStringOption('encoding', 'UTF-8')
options.addStringOption('charSet', 'UTF-8')
}
task sourcesJar(type: Jar) {
from android.sourceSets.main.java.srcDirs
// https://discuss.gradle.org/t/how-does-property-class-work-in-build-configuration/30320
archiveClassifier = 'sources'
}
task javadoc(type: Javadoc) {
source = android.sourceSets.main.java.srcDirs
classpath += project.files(android.getBootClasspath().join(File.pathSeparator))
}
task javadocJar(type: Jar, dependsOn: javadoc) {
from javadoc.destinationDir
// https://discuss.gradle.org/t/how-does-property-class-work-in-build-configuration/30320
archiveClassifier = 'javadoc'
}
artifacts {
archives javadocJar
archives sourcesJar
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wupdigital/android-maven-publish/issues/35#issuecomment-478062013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmGUtBIx6KwDraNrTQgJhucJVf3Za4hks5vbj6VgaJpZM4cSQsQ
.

@Nunnery I'm not sure that I understand what you mean by removing LazyArtifactPublish wrapper. Then it's exactly as before (doesn't work). Also, adding an import statement doesn't work. The IDE think it's completely redundant:
        import org.gradle.api.internal.artifacts.dsl.LazyPublishArtifact

        publications {
            android.libraryVariants.all { variant ->
                "maven${variant.name.capitalize()}Aar"(MavenPublication) {
                    afterEvaluate {
                        from components.android
                        groupId project.group
                        artifactId 'parent-project-' + project.name
                        version project.version
                        artifact LazyPublishArtifact(javadocJar)
                        artifact LazyPublishArtifact(sourcesJar)
                    }
                }
            }
        }


Ctrl + Enter doesn't detect boundaries of a query for some sql operators if there is no ; at the end of the previous query (Blank line is statement delimiter = Smart)

Description
Use this code:
select *
from film_actor

SHOW SEARCH_PATH;

I expected to execute only the first query, but the application tries to execute both.
Adding symbol ; at the end of the first query fixes the issue.
DBeaver Version
Community Edition <IP_ADDRESS>407122322
Operating System
Windows 10
Database and driver
PostgreSQL 16
PostgreSQL JDBC Driver 42.7.2
Steps to reproduce
https://github.com/user-attachments/assets/d07122cf-fa04-4c03-90c0-659c1dd04483
Additional context
No response

Did you try changeing the "Blank line is statement delimiter" to always?

Thank you for bug report.


Update jinja2 compiler syntax

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks!

We should probably also remove this legacy bit.
https://github.com/conda-forge/libdb-feedstock/blob/a6d8d8815ac5444fcab4ae742249fe040e1958a1/recipe/build.sh#L3-L10


Multiple active steps not working

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Multiple active Step components(enabled with active prop on Step component) inside Stepper should expand all Steps
Current Behavior

Multiple active Step components inside Stepper activates only one Step.
This works on Material-UI upto v3.1.1, but does not work in v3.1.2 onwards
Steps to Reproduce

Links:

v3.1.1 demo(working) - https://codesandbox.io/s/rj5k2w6jo
v3.1.2 demo(not working) - https://codesandbox.io/s/2vxjl116zy

Context

I'm trying to show all details inside stepper in one view, without expanding step manually
Your Environment

Tech
Version

Material-UI
v3.1.2

React
16.5.2

Browser
Chrome 69

OS
Linux(Ubuntu)

I think setting active on all Steps is a hacky way to achieve what #12948 is asking for. The change was caused by #13023.
The fix is pretty simple. Changing the order in https://github.com/spirosikmd/material-ui/blob/89f6c30fbf38e0ce87cd6bb5554bd460ef343e25/packages/material-ui/src/Stepper/Stepper.js#L88
should be sufficient. Do you want to work on it?
From a semantic point of view I don't see a reason to allow multiple active steps so I would say that you relied on a bug. The active prop on StepConnector should be controlled by the Stepper component.  On the other hand the fix would give some control back to the user.
This would be no issue if we could get rid of the cloneElement pattern and let users control this via render props. See #12921 for more information.

I have just spotted the issue too looking into #13130. We miss a unit test :)

Thanks for looking into this @eps1lon. Shall I submit a PR with those changes? @oliviertassinari


Web App Connector cannot add Home page url

Description of the bug
When creating or editing a web app connector, you cannot change the App Home Page URL field
Steps to reproduce the bug:

Create a new Web App Connector (name does not matter)
Type a valid URL into the metadata field "App Home Page URL"
Click on the Save Changes button
See error

Expected behavior
Saves metadata and Save successful message appears on top of screen
Additional information
First noticed Apr. 20th, may have to do with the iRods upgrade that occured on Apr. 19th.

@henrichsen can you verify that this is the error you encountered? Thanks

Yes this is the error encountered
On Mon, Apr 25, 2022 at 12:16 PM Devin Cowan @.***>
wrote:

@henrichsen https://github.com/henrichsen can you verify that this is
the error you encountered? Thanks
[image: image]
https://user-images.githubusercontent.com/17934193/165123582-3cac80dd-7810-4890-94a5-eebd9ad770bd.png
—
Reply to this email directly, view it on GitHub
https://github.com/hydroshare/hydroshare/issues/4597#issuecomment-1108889085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ3FIWGH5A62JGKDVIBCMFTVG3OPDANCNFSM5T47ADQA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Neither a lofty degree of intelligence nor imagination nor both together go
to the making of genius. Love, love, love, that is the soul of genius.
-Wolfgang Amadeus Mozart


Add Maks Litskevich as RC

I am nominating or self-nominating a Recognized Contributor.
Name: Maks Litskevich
GitHub Username: @Zzzabiyaka
Projects/SIGs:   WAMR
Nomination
I nominate Maks because of his many contributions to WAMR.
Optional: Endorsements
Marcin Kolny (@loganek)
I have read and understood the qualifications for a Recognized Contributor

Thanks @xwang98 for the nomination and @loganek for the endorsement.
It matters a lot to me! Looking forward to make even more contributions!

We discussed this in the last TSC meeting, and all agree that your contributions are worthy of recognition in the BA. Thank you for all the hard work!
@Zzzabiyaka, to finalize the addition, please send an email to<EMAIL_ADDRESS>to let us know which address to use for communicating with you as a Recognized Contributor, and to confirm that you accept the nomination.
That address will be added to our RCs mailing list, which receives community and project updates every few weeks or so.
Once we've received that email, we'll add you to the mailing list and merge this PR. Thank you!


set up vagrant envi

Set up vagrant environment.
Now you can run our application via
vagrant up
vagrant ssh
cd /vagrant
FLASK_APP=service:app flask run -h <IP_ADDRESS>
You will see "Hello Supplier!" under "/" path.

@Luolingwei should we add the VagrantFile in .gitignore?