passing in an external Cheerio instance to x-ray

Is it possible to pass-in an external cheerio instance? e.g.: $.
Use-case: I'n authenticating using Request + Cheerio (following this tutorial), since authentication using x-ray is not that easy (1).
Noew I've done var $ = cheerio.load(body);, leaving me with the correct cheerio context after logging-in. It would be great if I could easily pass this cheerio context to x-ray so I could leverage x-ray.select etc.
Is that possible?
1): I've seen this issue with the rec to use phantomJS and try to authenticate through Nightmare. I didn't have much luck going in that direction. Besides it would be great not having to resort to this for performance reasons, having to build phantomJS on a system just for the need if authentication, etc.

@gebrits you need a browser to interact with the page, store/set cookies, how would you do it without PhantomJS? Plus x-ray-phantom is an opt-in solution, you don't have to use it if you don't want to.

@olivierlesnicki

You don't need a browser to store/set cookies. It's just passing http headers/cookies
I don't need to 'interact' with a page. If with that you mean that the page should react to something like click-events. Instead I just need to scrape server-side rendered pages. (so no client-side/javascript generated code) The latter being an excellent use-case to use PhantomJS, but for a lot of other stuff it's overkill.
I realize I don't have to use Phantom as a plugin to x-ray but atm it seems the advised workaround to authenticate. However, authentication (setting some headers, and remembering cookies) in essence has little to do with the reason to use PhantomJS. Or in other words, using PhantomJS purely for the reason to authenticate seems overkill.

@gebrits OK I see your point there

@gebrits You could create a plugin for it and register it with .use(plugin).
The plugins have access to the xray instance and can overwrite the xray.request method which is used to access the page (you could set headers) and collect the HTML content.

Ahh yes, that would be a good way. Thanks @olivierlesnicki

Something along the lines of (don't copy/paste the code I've probably made 1,000 mistakes):
var request = require('request');
var cheerio = require('cheerio');
var xray = require('x-ray');

function driver(credentials) {

  return function plugin(xray) {

    xray.request = function(url, fn) {
      request.post({
          uri: 'http://yourwebsite.com/login',
          headers: {
            'content-type': 'application/x-www-form-urlencoded'
          },
        body: require('querystring').stringify(credentials)
      }, function(err, res, body){

        if(err) return fn(err);

        request(url, function(err, res, body) {

          if(err) return fn(err);

          return fn(null, body);

        });
      });
    }

    return xray;

  }

}

xray('http://yourwebsite.com/login')
  .use(driver({
    username: 'kevin',
    password: 'secret'
  }))
  .select()

Thanks @olivierlesnicki , will give this a try soon. Looks good on the outset. Only thing that seems to be missing at a glance is needing to set jar: true to save cookies for subsequent requests. Will update with complete example once I get around to it. Thanks again.

@olivierlesnicki works nicely! Here's the slightly altered snippet I'm using:
    function driver(credentials, jar, isLoggedIn) {

     function reqFN(url, fn){
         request({
            url: url,
            jar: jar,
          }, function(err, res, body) {
            if(err) return fn(err);
            return fn(null, body);
          });
      }

      return function plugin(xray) {
        xray.request = function(url, fn) {
          if(isLoggedIn(jar)){
            reqFN(url, fn);
          }else{
            request.post({
                jar: jar,
                followAllRedirects: true,
                uri: 'https://mysite.com/login',
                headers: {
                  'content-type': 'application/x-www-form-urlencoded'
                },
              body: require('querystring').stringify(credentials)
            }, function(err, res, body){
              if(err) return fn(err);
              reqFN(url, fn);
            });
          }
        };
        return xray;
      };
    }

    var myJar = request.jar();

    //'https://www.odesk.com/o/jobs/browse/'
    xray("https://mysite.com")
      .use(driver({ //These credentials should match the intput names on the login form
         username: 'username',
          password: 'password'
      }, myJar, function(jar){
        //A custom function to signal based on looking at the cookies when a user is logged in or not.
        //This is used so we don't need to login for all subsequent requests.
        return (jar.getCookieString("https://mysite.com").indexOf("<loginneedle>") !== -1);
      }))

      .select([{
        //stuffz
      }])
      .paginate('.paginate')
      .limit(10)
      .write(process.stdout);

thanks @ol

@gebrits Your code didn't work with me. It kept saying that xray has no method 'use' or has no method 'select'. Does it work with older versions of xray? Could you also add a valid website and all the require statements please.

+1

It looks like the API has changed significantly since this was an acceptable solution, which has broken this solution. Perhaps we could open this issue again?
It would be useful if in the x-ray-crawler repo there were some example of how to use drivers with the newer, functional API?
I understand that @matthewmueller, you might not have the time to fix things but without examples, the ROI on having to grok your code before using the library is pretty terrible. It's a lot of effort for little gain.

@jasper-lyons sorry for your frustration, turns out designing a scraping API that works on every website out there is a pretty difficult undertaking. There are more breaking changes on the horizon once this lands: https://github.com/segmentio/nightmare/issues/200. But we should be one step closer to our goal.
Often times looking at tests is a good place to find examples, including how to pass a cheerio instance in.

It can be easily achieved with new APIs
let superagent = require('superagent');
let Xray = require('x-ray');

logIntoYourSiteWith(agent).then(() => {
  let x = Xray().driver(driver(agent));
  x('http://somewhere', 'scope', [{}]);
});

function driver(opts) {
  return function http_driver(ctx, fn) {
    console.log(ctx.url);
    agent
      .get(ctx.url)
      .set(ctx.headers)
      .end(function(err, res) {
        if (err && !err.status) return fn(err)

        ctx.status = res.status
        ctx.set(res.headers)

        ctx.body = 'application/json' == ctx.type
          ? res.body
          : res.text

        // update the URL if there were redirects
        ctx.url = res.redirects.length
          ? res.redirects.pop()
          : ctx.url

        return fn(null, ctx)
      })
  }
}

Hey, so I had this same problem. I was a bit confused, bug dig some digging. So to add some color to @heycalmdown 's answer... the function he posted is copied from the default driver that x-ray already uses. But if you want to pass some auth headers, for example, you'll have to tweak it slightly. You can do it like so...
modules.export = driver
var superagent = require('superagent')

function driver(opts) {
  return function http_driver(ctx, fn) {
    console.log("Fetching...", ctx.url);
    superagent
      .get(ctx.url)
      .set(_.merge(ctx.headers, opts.headers))
      .end(function(err, res) {
        if (err && !err.status) return fn(err)

        ctx.status = res.status
        ctx.set(res.headers)

        ctx.body = 'application/json' == ctx.type
          ? res.body
          : res.text

        // update the URL if there were redirects
        ctx.url = res.redirects.length
          ? res.redirects.pop()
          : ctx.url

        return fn(null, ctx)
      })
  }
}

var cookies = {Cookie: cookieVal}
var driverWithAuth = driver({headers: cookies});
x = Xray().driver(driverWithAuth);
// Go about your day with xray.
x(yourUrl)

This worked for me.


fix #14

This PR adds an option to indicate that the function a rule is defined for is mutating its input argument.
Closes #14

Looks good to me @mohamed82008 - Please check if you find the time, I assigned you for review :-)

I think the test failures are related to ImplicitDifferentiation 0.4 changing their API using 3 arguments instead of 2. The tests need to be updated but it's not related to this PR.

bump

Sorry for delay, I merged #17 first, so we can see if it's running now.


Test Binder does not work with Spring Boot 3.3.2 any more

After upgrading to Spring Boot 3.3.2 it seems that the OutputDestination does not yield any messages but null any more. If I go back to SB 3.3.1 everything is fine again.
Version of the framework

Spring Boot 3.3.2
Spring Cloud 2023.0.3

Additional context
I found this question on SO which seems to address the same issue.

Can you please provide a small sample? We have tests that are currently running so I am a bit surprised

@olegz Of course: https://github.com/kschlesselmann/spring-cloud-stream-2988
Just change the SB version to 3.3.1 to make the test pass.

Wondering if it is Kotlin specific. Just tried it with Java and all is good


chore(fx-2377, fx-2371): remove old fair apps; redirects

Closes: FX-2377, FX-2371
Deletes the old apps, simplifies the redirects to always happen instead of using the env vars.

I'm curious about what the fair_info app is — it looks like that can be removed as well (but can be addressed in a separate PR)?

(Whoops removed empty readme, no longer needed)

(Whoops removed empty readme, no longer needed)


There are no "Create Virtual Machine..." and "Create Virtual Machine... (Advanced)" actions for focused "Virtual machines" node

OS: Win 10
Build Version: 20230525.1
Regression: Not a Regression
Repro Steps:

Click "Focus Group" icon to focus the "Virtual machines" node.
Right click the "Virtual machines" node.
Check the context menu.

Expect:
There are "Create Virtual Machine..." and "Create Virtual Machine... (Advanced)" actions in the context menu.

Actual:
There are no "Create Virtual Machine..." and "Create Virtual Machine... (Advanced)" actions in the context menu.

This is a bigger issue in resources that we are tracking as well.

I fixed this in Functions via https://github.com/microsoft/vscode-azurefunctions/pull/3732. The same fix needs to be applied here.


chore: avoid false-positive kotlin-stdlib vulnerability

PR summary
This PR adds a .cveignore entry to avoid the kotlin-stdlib false positive vuln.
I also bumped up the java core version to the latest.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.22.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Base package liblas-dev should be libblas-dev

I've seen some errors in cfncluster ubuntu-based AMI's related to the package 'liblas-dev'. I think this is a typo on https://github.com/awslabs/cfncluster-cookbook/blob/master/attributes/default.rb#L114 and the intended package is 'libblas-dev'. Unfortunately liblas-dev is also a valid name for a different package..

Package: liblas-dev
State: installed
Automatically installed: no
Version: 1.7.0+dfsg-4
Priority: extra
Section: universe/libdevel
Maintainer: Ubuntu Developers<EMAIL_ADDRESS>Architecture: amd64
Uncompressed Size: 700 k
Depends: liblas2 (= 1.7.0+dfsg-4), libtiff-dev, libgeotiff-dev, libgdal-dev (>= 1.10.0~)
Conflicts: liblas-dev
Description: ASPRS LiDAR data translation library - C++ development files
libLAS is a C/C++ library for reading and writing ASPRS LAS versions 1.0, 1.1 and 1.2 data. The LAS format is a sequential
binary format used to store data from sensors and as intermediate processing storage by some LiDAR-related applications.
LiDAR (Light Detection and Ranging) is an optical remote sensing technology that measures properties of scattered light to
find range and/or other information of a distant target. The prevalent method to determine distance to an object or surface
is to use laser pulses.
This package contains the development files to build applications in C++.
Homepage: http://liblas.org/
Package: libblas-dev
State: installed
Automatically installed: no
Version: 1.2.20110419-7
Priority: optional
Section: libdevel
Maintainer: Ubuntu Developers<EMAIL_ADDRESS>Architecture: amd64
Uncompressed Size: 1,221 k
Depends: libblas3 (= 1.2.20110419-7)
Conflicts: libblas-dev
Provides: libblas.so
Description: Basic Linear Algebra Subroutines 3, static library
This package is a binary incompatible upgrade to the blas-dev package. Several minor changes to the C interface have been
incorporated.
BLAS (Basic Linear Algebra Subroutines) is a set of efficient routines for most of the basic vector and matrix operations.
They are widely used as the basis for other high quality linear algebra software, for example lapack and linpack.  This
implementation is the Fortran 77 reference implementation found at netlib.
This package contains a static version of the library.
Homepage: http://www.netlib.org/blas/

Is liblas-dev the correct base package? I see non-debian platforms are installing blas-devel. I can submit a PR to change this if needed.

Good catch. Should be for BLAS.
On Thu, Mar 2, 2017 at 07:08 Adam Kraut<EMAIL_ADDRESS>wrote:

I've seen some errors in cfncluster ubuntu-based AMI's related to the
package 'liblas-dev'. I think this is a typo on
https://github.com/awslabs/cfncluster-cookbook/blob/master/attributes/default.rb#L114
and the intended package is 'libblas-dev'. Unfortunately liblas-dev is also
a valid name for a different package..
Package: liblas-dev
State: installed
Automatically installed: no
Version: 1.7.0+dfsg-4
Priority: extra
Section: universe/libdevel
Maintainer: Ubuntu Developers<EMAIL_ADDRESS>Architecture: amd64
Uncompressed Size: 700 k
Depends: liblas2 (= 1.7.0+dfsg-4), libtiff-dev, libgeotiff-dev,
libgdal-dev (>= 1.10.0~)
Conflicts: liblas-dev
Description: ASPRS LiDAR data translation library - C++ development files
libLAS is a C/C++ library for reading and writing ASPRS LAS versions 1.0,
1.1 and 1.2 data. The LAS format is a sequential
binary format used to store data from sensors and as intermediate
processing storage by some LiDAR-related applications.
LiDAR (Light Detection and Ranging) is an optical remote sensing
technology that measures properties of scattered light to
find range and/or other information of a distant target. The prevalent
method to determine distance to an object or surface
is to use laser pulses.
This package contains the development files to build applications in C++.
Homepage: http://liblas.org/
Package: libblas-dev
State: installed
Automatically installed: no
Version: 1.2.20110419-7
Priority: optional
Section: libdevel
Maintainer: Ubuntu Developers<EMAIL_ADDRESS>Architecture: amd64
Uncompressed Size: 1,221 k
Depends: libblas3 (= 1.2.20110419-7)
Conflicts: libblas-dev
Provides: libblas.so
Description: Basic Linear Algebra Subroutines 3, static library
This package is a binary incompatible upgrade to the blas-dev package.
Several minor changes to the C interface have been
incorporated.
BLAS (Basic Linear Algebra Subroutines) is a set of efficient routines for
most of the basic vector and matrix operations.
They are widely used as the basis for other high quality linear algebra
software, for example lapack and linpack. This
implementation is the Fortran 77 reference implementation found at netlib.
This package contains a static version of the library.
Homepage: http://www.netlib.org/blas/
Is liblas-dev the correct base package? I see non-debian platforms are
installing blas-devel. I can submit a PR to change this if needed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/cfncluster-cookbook/issues/20, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACUVitjP-NtKxDcDOUwMD7jGS2od5WeSks5rhttdgaJpZM4MRGq8
.


Add link to Chrome web store in GitHub repo URL

There is a link to install the repo from the web store in the readme, but we can make use of the URL next to the repo description on the top. This could make it easier for new people to go the web store and install it to try it out.
https://chrome.google.com/webstore/detail/refined-github/hlepfoohegkhhmjieoechaddaejaokhf
@sindresorhus Only people able to edit the repo settings can edit the repo description and URL.

:+1:

Done


Slackbot API for Security Monkey Custom Alerting

Adding a Custom Alerter - SlackBot API to send custom alerts, posting auditor/watcher changes on a slack channel. Fully integrates with automated scheduler, posting to slack channel when watchers/auditors are ran. Note: make sure you have it integrated as a custom alerter so it is called by watcher.py and auditor.py!

Please fix the unit tests and I will merge this in.

Ok I will


Issues with git sv tag

git sv tag just hangs for all my repos. Even with git sv --log-level debug tg I don't get any output.
v1.0.5
git sv rn and git sv cgl work fine. Example repo

Cant reproduce:
❯ git tag
v1.0.0

❯ ~/Devel/golang/projects/git-sv/dist/git-sv rn
## v1.0.1 (2024-10-30)

### Maintenance

- add git-sv templates (15b815c)
- update READMEs (bef84fd)
- migrate git provider (8970647)
- remove release-helper workflow (c149e49)
- add license (218b8e7)
- update pre-commit hooks (6f243a4)
- update renovate prefix (2f1c59d)

### CI

- also run lint on tag events (03152b8)
- create tag with v prefix (d3c7266)
- add changelog and release workflows (79cdcdc)

❯ ~/Devel/golang/projects/git-sv/dist/git-sv tag --local
v1.0.1

❯ git tag
v1.0.0
v1.0.1

Skipping --local:
❯ ~/Devel/golang/projects/git-sv/dist/git-sv tag
Username for 'https://gitlab.com':

So from what I can see it works as intended up to the tag push asking for the auth data.

Thanks for checking! I'll investigate again, couldn't get any return after multiple minutes on multiple tries.

Have you found something?

Not yet, still same behavior with 1.0.6 (just tried it again).
Not too urgent, I can also do things manually.
If the next version has more debug/trace logs that would show parts of the process, I could narrow it down better and infer where it is stuck (running with git sv --log-level debug tag doesn't yield any output).

Update: I see this issue on all repos I've tried so far (n=4). Not sure what the possible issues source could be here, maybe it is even OS-specific?
I can try on a Linux server these days to maybe narrow this down in more detail.

Thanks can try it also on my work mac.

Works for me on my mac as well:
❯ ../golang/git-sv/dist/git-sv tag
1.1.0

❯ git version
git version 2.47.1

❯ sw_vers
ProductName:		macOS
ProductVersion:		14.7.1
BuildVersion:		23H222

So I have absolutely no clue what the issue could be.

Strange. Last idea would be the shell. But I already tried with fish and bash.
Super strange. Would be interesting to find out. I guess I'll check out the code and do some debug runs.

Im curious was well. If I can support you somehow, let me know.

While debugging I found that it hangs at this line
https://github.com/thegeeklab/git-sv/blob/bf49aa686d21fcb70c23b69daa62ecfa17e57cfe/app/app.go#L164
when jumping in, it hangs at err := c.Run() in the following bundled go function
func (c *Cmd) CombinedOutput() ([]byte, error) {
	if c.Stdout != nil {
		return nil, errors.New("exec: Stdout already set")
	}
	if c.Stderr != nil {
		return nil, errors.New("exec: Stderr already set")
	}
	var b bytes.Buffer
	c.Stdout = &b
	c.Stderr = &b
	err := c.Run()
	return b.Bytes(), err
}

go 1.23.4 via homebrew
I then installed go via https://go.dev/doc/install assuming it is a homebrew issue but see the same behavior with the non-homebrew install. Weird.

Thats really weird. Whats even more weird is that I can not reproduce it even on the same environment

You could check a few things:

Running with GIT_TRACE=1 environment variable to see detailed git operations
Checking if there are any git hooks in .git/hooks
Verifying git credentials are properly configured

Does git-sv tag --local works for you?

No.

Running git tag manually works without any user interaction?

Yes. That's how I've done it all the time before trying git-sv.

Checking if there are any git hooks in .git/hooks

No hooks.

Given that it hands when executing cmd.run, it looks more like a generic go issue than being related to git-sv. I'd expected other programs making use of this to also hang.
If you search for cmd.run() hangs on macos you'll find a bunch of entries but none of them was really helpful or specific to my issue. At the moment I am lost but it doesn't look like to be an issue of git-sv per se, hence we can also close here. No need for you to debug my go runtime 😅

I would still like to find out, especially as I tried really hard to reproduce it with various mac VMs in different versions without success.

Given that it hands when executing cmd.run, it looks more like a generic go issue

Yeah but cmd.run is also used multiple times for the release notes command that works for you :thinking:

Can you test a build with CGO_ENABLED=0? If you have a arm64 mac you need to adjust GOARCH as well:
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 go build -v -tags 'netgo,osusergo' -ldflags '-extldflags "-static" -s -w' -o dist/git-sv ./cmd/git-sv

Can you test a build with CGO_ENABLED=0? If you have a arm64 mac you need to adjust GOARCH as well:

Same issue.

Yeah but cmd.run is also used multiple times for the release notes command that works for you 🤔

Yes that one works 🤔

Ok lets try another approach:
sudo ktrace trace -S -f C3 -c ./dist/git-sv tag --local

This outputs so much (incl. processes from other programs) that I can't see anything useful or paste the output here.
sudo ktrace trace -S -f C3 -c ./dist/git-sv tag --local | grep git-sv

is a bit reduced but I still don't know what to look out for.
Just an excerpt here (the head looks a bit different)
[...]
2024-12-17 13:03:56.658995 CET          0.5(0.5)         VFS_LOOKUP                           klab/git-sv/Electron                                                99a170             2(AP-E) Electron(77807)
2024-12-17 13:03:56.660168 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/2024-12-17                                              99a16f             1(AP-E) Electron(77807)
2024-12-17 13:03:56.660254 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/2024-12-17                                              99a171             0(AP-E) Electron(77807)
2024-12-17 13:03:56.661013 CET          0.4              VFS_LOOKUP                           klab/git-sv/2024-12-17 13:03:56.                                    99a172             0(AP-E) Electron(77807)
2024-12-17 13:03:56.662146 CET          0.0              VFS_LOOKUP                           klab/git-sv/2024-12-17 13:03:56.                                    99a170             5(AP-P) Electron(77807)
2024-12-17 13:03:56.663016 CET          0.1(0.1)         VFS_LOOKUP                           klab/git-sv/git-sv                                                  99a16f             5(AP-P) Electron(77807)
2024-12-17 13:03:56.663073 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/git-sv                                                  99a171             5(AP-P) Electron(77807)
2024-12-17 13:03:56.679626 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/klab>>>>>>>>>>>>>>>>                                    99a172             4(AP-P) Electron(77807)
2024-12-17 13:03:56.679706 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/klab>>>>>>>>>>>>>>>>                                    99a170             4(AP-P) Electron(77807)
2024-12-17 13:03:56.729394 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/klab>>>>>>>>>>>>>>>>                                    99a16f             6(AP-P) Electron(77807)
2024-12-17 13:03:56.729512 CET          0.0(0.0)         VFS_LOOKUP                           klab/git-sv/klab>>>>>>>>>>>>>>>>                                    99a171             2(AP-E) Electron(77807)
2024-12-17 13:03:56.730436 CET          0.3              VFS_LOOKUP                           klab/git-sv/2024-12-17 13:03:56.                                    99a172             5(AP-P) Electron(77807)
2024-12-17 13:03:56.730512 CET          0.0              VFS_LOOKUP                           klab/git-sv/2024-12-17 13:03:56.                                    99a170             4(AP-P) Electron(77807)

What Im really wondering about is how the heck is Electron involved here? The last col is the process-name and seeing Electron here is kinda weird (and I dont see it in a full trace on my system)


There was an Error it should be "api.search_tweets" instead of "api.search

The api.search was changed in a Tweepy update

Inactive repo


[CU-86934hmxa] return root thread comments use pagination

The current flat structure returns no application value, it is like a journal. And the tree structure does not have pagination function and has no engineering significance
Each descendant comment should record their root comment ID, so that we can perform pagination queries on the root comment and recall the N levels of descendant comments below each root comment。

Is it worth to introduce startWith property if undefined then its root, otherwise take the id of comment to build the nested structure starting with it?

The advantage of this is that it is easy to build a comment view with only two layers. The first layer is the root comment, which is oriented towards the comment object (article), and the second layer is the reply to the comment, with the reply target being the root comment or other reply.
Similar to the following view:
comment:

Tom: What is this article about?

Jack:  I think it should be about love!

Robert > Jack: Hatred is more than love!

James: Great work!

To achieve such a view, we only need to maintain two relationships for comments: the root relationship and the reply relationship.


image encoder image size is too big ,can reduce 1024 to 640/480 for acceleration?

image encoder image size is too big ,can reduce 1024 to 640/480 for acceleration?

Hi @Mediumcore ,
This would require distilling a new model, for this you may be able to follow these steps.

Disclaimer:  I haven't tested these, so let me know if you run into issues.

Step 1 - Register a new model
Register a new model, and ensure that it outputs features of shape 256x64x64 for your desired input resolution.  For example, for an input of size 512x512, your model must have an output stride of 8.
You can register the model similar to here:
https://github.com/NVIDIA-AI-IOT/nanosam/blob/653633614b2eb93b06ba3be9adb2aeffb117bd72/nanosam/models/timm_image_encoder.py#L78
You could try registering a new model with a different stride, and setting the student size to a lower resolution (ie: 512x512).
Step 2 - Train the distilled model
Next, you'll need to train the model on unlabeled images.  Follow the training instructions in the README, but set the "student_size" parameter to the desired size (512).
https://github.com/NVIDIA-AI-IOT/nanosam/blob/653633614b2eb93b06ba3be9adb2aeffb117bd72/nanosam/tools/train.py#L33
Step 3 - Evaluate the distilled model
Follow the evaluation instructions in the README to compare the accuracy for small / medium / large objects.
As a note:  It's worth noting that distillation only applies to the image encoder.  It's worth benchmarking the mask decoder to see if this is worth it, as the image encoding speed is approaching the decoding speed and may no longer be a performance bottleneck.
Hope this helps.  If we end up releasing a lower resolution model I will update this thread, but we have no current plans at the moment.
John

Register a new model, and ensure that it outputs features of shape 256x64x64 for your desired input resolution. For example, for an input of size 512x512, your model must have an output stride of 8.
You can register the model similar to here:
https://github.com/NVIDIA-AI-IOT/nanosam/blob/653633614b2eb93b06ba3be9adb2aeffb117bd72/nanosam/models/timm_image_encoder.py#L78
You could try registering a new model with a different stride, and setting the student size to a lower resolution (ie: 512x512).

Hey there, could I just check which particular layer of convolution the output stride of 8 should be applied to? Also, where is the setting for the student size resolution? I am trying to get a model with an input size of 512x512.
https://github.com/NVIDIA-AI-IOT/nanosam/blob/653633614b2eb93b06ba3be9adb2aeffb117bd72/nanosam/models/timm_image_encoder.py#L42-L57

@Mediumcore Hi, it would be amazing if you could share your ONNX encoder decoder on 448x448 input. I will be grateful


Make true absolute imports relative to source roots work

I asked on SO here https://stackoverflow.com/questions/70888494/configure-true-absolute-imports-in-typescript
But just in case it's not possible, I'm requesting this feature.
Specifically:
import foo from '/foo';

should import {sourceRoot}/foo
where sourceRoot is {pwd}/src
Assuming it's not possible to do this via tsconfig.json already. If so, this is a request for docs.

Oops I think this might have been the wrong project, sorry.

Actually yeah this issue could stay in case TypeScript says "do this in VS Code".

(Honestly sometimes dealing with Microsoft projects is like having a parent say go ask the other parent, back and forth 3-4x.)

This belongs on TS as the same logic would also apply to tsc (but first see if anyone answers on stack overflow because I'm pretty sure this is already possible to configure)

This is possibly a bug in VS Code, see this comment in TypeScript project issue.


The symbol "﷽" isn't properly displayed

How to reproduce:

Paste this text into vim: ﷽﷽﷽﷽﷽﷽﷽﷽
Observe how individual symbols aren't distinguishable, they overlap and don't look anything like in the browser.

vim-8.1.0342 in the xfce4 terminal on FreeBSD-11.2

This is due to the fact that in Vim, one character is one screen cell (or two cells for a "wide" East-Asian character). Now the basmala ligature U+FDFD is one "character" in the Vim sense of the word, but it corresponds to a lot of Arabic "letters", viz. (in some crude Latin letter-for-letter transliteration omitting harakat) bsm allh alrhmn alrhym. There's no way you can pack all this into the screen space meant for one letter and still make it understandable. Browsers, OTOH, use variable-length fonts, especially for highly cursive fonts like Arabic, and they will expand the basmala glyph to use any width it needs.
But don't worry, if you hit ga on that "unreadable" glyph in Vim and it tells you that (in UTF-8 'encoding') it has hex value FDFD, then it is indeed the basmala ligature, even though it is not recognizable in Vim.
Best regards,
Tony.

one character is one screen cell (or two cells for a "wide" East-Asian character)

Why doesn't vim expand this, and allow other characters to occupy two cells, or perhaps 3 cells too?

Mostly history of Vim, and the use of monospace fonts. Vim is not a WYSIWYG text processor, remember, but a plain text editor, which ultimately dates from the time when multi-language was in its infancy, Arabic script rendering was unknown, Chinese was possible but largely reserved to East-Asian editions of the OS. I saw the first steps of the Arabic-in-Unicode module of Vim a few years ago, and AFAIK it still doesn't support Indian-subcontinent scripts like the Devanagari script used for Hindi.
Best regards,
Tony.

one character is one screen cell (or two cells for a "wide" East-Asian character)

Why doesn't vim expand this, and allow other characters to occupy two
cells, or perhaps 3 cells too?

Sorry, these Arabic characters just don't fit in the mono-spaced system,
which is what Vim is using.  Vim doesn't render the glyph, it only tells
the rendering system (often a terminal emulator) to do that, and then
the width is totally unpredictable.  On my Terminal it appears to take
about 10 cells.  We just don't support that.
--
hundred-and-one symptoms of being an internet addict:
114.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

A possible workaround is to manually insert ~10 spaces after Basmala character. Unless you're programming in Whitespace, you should be fine.
Basmala isn't the only extra-wide Unicode characters. There also

Ǆ
‱
௸
௵
꧄
꧅
⸻
𒈙
𒅃 𒈓
𒐪

Maybe Vim can insert "virtual non-existent spaces" (something like :tabstop) after such characters?


🐛 FontSize incorrect in Typography.standard

Typography.standard() does not seem to follow type ramp.
I would expect title to be smaller than subtitle however subtitle is currently much larger.
factory Typography.standard({
    Brightness? brightness,
    Color? color,
  }) {
    assert(brightness != null || color != null);
    color ??= brightness == Brightness.light ? Colors.black : Colors.white;
    return Typography(
      display: TextStyle(
        fontSize: 42,
        color: color,
        fontWeight: FontWeight.w600,
      ),
      titleLarge: TextStyle(
        fontSize: 34,
        color: color,
        fontWeight: FontWeight.w500,
      ),
      title: TextStyle(
        fontSize: 22,
        color: color,
        fontWeight: FontWeight.w600,
      ),
      subtitle: TextStyle(
        fontSize: 28,
        color: color,
        fontWeight: FontWeight.w500,
      ),
      bodyLarge: TextStyle(
        fontSize: 18,
        color: color,
        fontWeight: FontWeight.normal,
      ),
      bodyStrong: TextStyle(
        fontSize: 14,
        color: color,
        fontWeight: FontWeight.w600,
      ),
      body: TextStyle(
        fontSize: 14,
        color: color,
        fontWeight: FontWeight.normal,
      ),
      caption: TextStyle(
        fontSize: 12,
        color: color,
        fontWeight: FontWeight.normal,
      ),
    );
  }

The showed type ramp is the old one. The following is the new one:


Performance - District Boundaries

Having usable / semi-realistic district boundaries would be useful, so might as well make it fast.
Three potential methods:

Current circle point buffers (slow)
Potentially use Voronoi diagrams (fast but inaccurate - straight lines)
Potentially assemble together council wards - likely to be a better representation of how Districts are actually composed

Buffer improvements alone move from ~1 hour to ~30s

Now takes ~640ms for a county. Without spatial transforms (to BNG and back), it takes 30ms, but I couldn't get buffering to work and have already spent a while on this


strange bug when using windicss extractions with unocss

UnoCSS version
0.61.0
Describe the bug
using windicss extractions to dynamicaly render styles causing unexpected animation. even thought i'm  not using any sort of transition or animation
Reproduction
https://stackblitz.com/edit/unocss-unocss-8b5es5?file=app.vue,nuxt.config.ts
System Info
system: windows 10
browser : chrome , firefox,edge,brave
framework : nuxt
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Your code is probably not doing what you want:

Do something like this instead :class="active ? '!text-green-400' : '!text-orange-400'"
Also, I had no idea this even existed, seems handy! https://github.com/unocss/unocss/blob/e3d3b2ed21f02c213351d2d2c1d46ae57cae808b/packages/preset-mini/src/_rules/question-mark.ts


Trim spaces when updating items too

Changing an existing item to only spaces should have the same
effect as deleting all characters, i.e. deleting the item from
the list.
Apologies for not noticing this in yesterday's PR.

Thank you again!


ARROW-13781: [Python] Allow per column encoding in parquet writer

This PR adds a new parameter to write_table to allow parquet encodings to be defined on a per column basis. The encodings currently supported are: PLAIN, BIT_PACKED, RLE, BYTE_STREAM_SPLIT, DELTA_BINARY_PACKED, DELTA_BYTE_ARRAY    .
It is not possible to set PLAIN_DICTIONARY and RLE_DICTIONARY for fallback encoding (those options will already be used by default in the C++ Parquet library).

I think before we expose this we should make sure that Java (parquet-mr) can read "DELTA_BINARY_PACKED, DELTA_BYTE_ARRAY ." I don't think these are well tested (and emitted by default) but I could be misrembering.

I added all review suggestions, the tests are all set. I think this is ready for final review if we decide to expose it.
@emkornfield @jorisvandenbossche where could I check and ask for help on the Java side regarding https://github.com/apache/arrow/pull/11724#issuecomment-977497773?

I think before we expose this we should make sure that Java (parquet-mr) can read "DELTA_BINARY_PACKED, DELTA_BYTE_ARRAY ." I don't think these are well tested (and emitted by default) but I could be misrembering.

@emkornfield those are actually not yet implemented for writing, only for reading, IIRC (so although this PR already allows you to specify it, you still get a NotImplementedError for now)
(and also if we would have the writing ability, I think it would be useful to actually be able to do that from python to make it easier to test this)

There are a few flake8 linting errors:
INFO:archery:Running Python linter (flake8)
/arrow/python/pyarrow/tests/parquet/test_basic.py:377:80: E501 line too long (81 > 79 characters)
/arrow/python/pyarrow/tests/parquet/test_basic.py:386:80: E501 line too long (89 > 79 characters)
/arrow/python/pyarrow/tests/parquet/test_basic.py:393:80: E501 line too long (82 > 79 characters)

If the encodings aren't supported yet, why are we adding them to the API, this just seems like it will disappoint users?

The ones that are already supported are "PLAIN" and "BYTE_STREAM_SPLIT", so the keyword has some use already (but it's certainly true it turned out less useful than we initially thought when starting the PR :-))

The ones that are already supported are "PLAIN" and "BYTE_STREAM_SPLIT", so the keyword has some use already (but it's certainly true it turned out less useful than we initially thought when starting the PR :-))

Yes, I think it will be useful, just want to make sure we don't disappoint users if they see a specific enum then try to use it and get an error thrown immeidately.

Thanks @AlenkaF !


linux_testing_bcachefs: 4.20.2019.02.09 -> 4.20.2019.02.15

Motivation for this change
This fixes koverstreet/bcachefs#16.
Things done

The test is broken on unstable and master, but I'm running this kernel right now without problems, as opposed to the old one.

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-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)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Works fine for me, albeit the expected errors of upgrading a filesystem without reformatting.

I didn't realize it wasn't backwards compatible, maybe it's time to introduce allow pinning a bcachefs version while disk format upgrades are still happening.


dependency bumps

update to non-vulnerable protobuf version
1.22.0 is affected by CVE-2024-24786
replace mergo with copier

replace mergo with copier

Is there any reason to do this? Mergo is a library we have been using extensively and tested throughly, we would need pretty solid reasons + more testing in our repos that are using mergo to switch all of them at once.

I have noticed that it is also used in nnet and nkn/v2.
I am working on those too. Replacing the deprecated gogo and github.com/golang/protobuf is a bit of a bigger chunk though.
copier has no dependencies. mergo needs yaml.
My biggest issue is that mergo declares it's module via a vanity url as dario.cat/mergo instead of github.com/darccio/mergo which causes the issue 248.
And imho there is no reason to that in the first place.


Update fullybrowser to 3.0.10

@arteck
Your GitHub tests are failing (package-lock outdated?).
Please fix.


[rxcpp] Change to new repository

This changes the source repository but not the version.  I also added an upstream patch that allows for find_package(rxcpp CONFIG) to work properly.  This will be in their next release and can be dropped at that point, but for any prior releases it will need to be applied.  I can remove that part of the PR if this is not acceptable.

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


Halftimes

@Adman I guess we'll have to figure this out somehow in the end

My current thinking around halftimes is as follows:

Run the first half
Figure out who kicked off the first in the first half

$ cat The_Blues_vs_The_Yellows-2021-01-02T11:48:24.890235Z.jsonl | grep KICKOFF | head -n 1 | jq .
"Y3"

Add an env variable (something like RCJ_SOCCERSIM_KICKOFF_TEAM) and set to B  in case yellow was kicking off in the first half and Y otherwise
Run the second half similarly to the first one

My current thinking around halftimes is as follows:

Run the first half
Figure out who kicked off the first in the first half

$ cat The_Blues_vs_The_Yellows-2021-01-02T11:48:24.890235Z.jsonl | grep KICKOFF | head -n 1 | jq .
"Y3"

Add an env variable (something like RCJ_SOCCERSIM_KICKOFF_TEAM) and set to B  in case yellow was kicking off in the first half and Y otherwise
Run the second half similarly to the first one

@mrshu I think we can close this one. If we find a better solution we can reopen it later.


Delete artifact links from model version via Client, ModelVersion and API

Describe changes
I implemented delete and delete all functions for Artifact Links inside a Model Version. This can be done via Client, ModelVerison and API from now on.
Endpoint structure validated with @Cahllagerfeld .
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[x] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@coderabbitai review


feat: helm-chart/gateway Apply all labels to pods also

Please provide a description of this PR:
Currently when using the Helm chart for deploying Istio gateway the deployment resource is nicely labelled with all Kubernetes recommended labels, however, the actual pod is only labelled with the selector labels. Would be nice to have all labels on the actual pod also.

Hi @langecode. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@langecode: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
14d3208137b594c658eee62bc3a6f517b8281d6b
link
true
/test release-notes_istio

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

I’ll check up on the as soon as I can find a little bit of time.
fre. 11. mar. 2022 kl. 08.49 skrev Istio Automation <
@.***>:

@langecode https://github.com/langecode: The following test failed,
say /retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
release-notes_istio 14d3208
https://github.com/istio/istio/commit/14d3208137b594c658eee62bc3a6f517b8281d6b
link
https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/37857/release-notes_istio/1502189166815875072
true /test release-notes_istio
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/37857#issuecomment-1064859247, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJPWOUTRL4YRB6MMFRYD4LU7L3IVANCNFSM5QMTSM2Q
.
You are receiving this because you were mentioned.Message ID:
@.***>


onchainkit: fix tanstack query compatibility

Strange, today it works as expected. Looks like I had old version locally. Closing this


Release notes for v1.14.0

Preview: https://deploy-preview-1404--cert-manager-website.netlify.app/docs/releases/release-notes/release-notes-1.14/
Updating release-next with updates to the release notes and installation instructions for v1.14.0.
xref: https://github.com/cert-manager/cert-manager/issues/6591

https://github.com/cert-manager/cert-manager/issues/6591

👍 I like your release notes a lot @wallrj

Thanks both.


Terragrunt is failing on GitHub Actions  and works locally & on Gitlab - Unsure of the reason

Describe the bug
Getting the error when running the terragrunt appy in GitHub Actions. This started happening 2-3 days and the same code was working without any issue.
Error: The variable resource_groups cannot be set using the -var and -var-file
│ options when applying a saved plan file, because a saved plan includes the
│ variable values that were set when it was created. The saved plan specifies
│ "{"dev-rg-common-01":{"location":"centralindia","name":"dev-rg-common-01","tags":{"resource_type":"rg"}}}"
│ as the value whereas during apply the value object with 1 attribute
│ "dev-rg-common-01" was set by an environment variable. To declare an
│ ephemeral variable which is not saved in the plan file, use ephemeral =
│ true.
To Reproduce

Clone the repository https://github.com/cloudutsukpilot/developerportal
Update the azure credentials in Github "Secrets and Variables"

ARM_CLIENT_ID
ARM_CLIENT_SECRET
ARM_SUBSCRIPTION_ID
ARM_TENANT_ID

Run the workflow "Deploy Azure Infrastructure" (infrastructure-deployment.yaml)
Terragrunt should failed while running the apply command for Common resources (does not matter if the resource is created or not)

Expected behavior
Terragrunt apply should work as expected
Nice to have

[ ] Terminal output
[ ] Screenshots

Versions
TERRAGRUNT_VERSION: 0.69.2
TERRAFORM_VERSION: v1.10.0
Additional context
Add any other context about the problem here.

Hey @SakharamS ,
There are known issues around Terraform 1.10+ and saved plans, as described here:
https://github.com/gruntwork-io/terragrunt/issues/3604
Until it's fully supported, you may have to take advantage of workarounds like adding ephemeral to variables or waiting for Terraform to fix the bug with applying saved plans.


3D PLA Animation

Hello, we are trying to implement some 3D Animation into a scene. Our animator program delivered a .fbx file with a .pla folder containing .mc and .xml files. Is there a way to use the information contained in the .pla folder to make the animation work? Or does all 3D animation need to be contained in .fbx files?

Viro does not support pla files. The 3D animation needs to be contained in with FBX or GLTF files.


zero value from the data returned by TIME_SERIES_MONTHLY API

we are facing one critical issue about TIME_SERIES_MONTHLY from the data API.
there's strange "0.0000" value from "low" slot. is this a error?

As above: after several data verification, we have a large number of data samples which have “0” in their “low” price slot. This is critically wrong and causing fatal error in our Apps, as following:
PS: we are pulling the data from the API address:

Hi this is something I can not hielo you with. Sinceramente I have nothing to do with the api endpoint. I hope the people ar Alpha Vantage can help you out.

Sure. I'm closing this ticket. Thanks.


Allowing Dataflow users to provide additional connection configuration.

This should address the configuration requirements of issue #484 to set the datahost.

What is the reason for exposing generic configuration such as Map<String, String>?

Just as I was wading through the code yesterday: What about com.google.cloud.bigtable.dataflow.CloudBigtableConfiguration.toHBaseConfig()? As it has this addtionalProperties, shouldn't that applied there, too?

@kevinsi4508: updated as per your comments.  We're exposing a more generic construct because the likelihood of any configuration change is as likely as the datahost, which is to say not likely, but possibly needed.  PTAL

@derjust: Can you clarify your question?
If you're asking if CloudBigtableConfiguration.toHBaseConfig() was updated, then the answer is: yes, it was updated.

@sduskis ah found it. From what I can envision as a consumer of the library I think the request from #484 is covered in a better/more flexible way :+1:

LGTM


Base manifest path is combined with the key

Vite.AspNetCore v1.8.0
This could just be a configuration issue, but if not, it seems like the Base setting used for manifest base path shouldn't be combined with the key of the chunk in ViteManifest or the base isn't used when accessing the key from the manifest in the tag helper.
Issue Details
appsettings.json:
{
  "Vite": {
    "Base": "./assets",
    "Manifest": "manifest.json"
  }
}

_Layout.cshtml:
    <link rel="stylesheet" vite-href="~/app.ts" asp-append-version="true"/>
    <script type="module" vite-src="~/app.ts" asp-append-version="true"></script>

vite.config.ts:
{
        appType: "custom",
        base: "./", // This is for css files to have the right relative url to any fonts.
        root: "./Assets",
        server: {
            port: appsettingsDev.Vite.Server.Port,
            strictPort: true,
            https: {cert: certificatePath, key: keyPath},
            hmr: {clientPort: appsettingsDev.Vite.Server.Port}
        },
        build: {
            outDir: "../wwwroot/assets",
            emptyOutDir: true,
            assetsDir: "",
            manifest: appsettings.Vite.Manifest,
            rollupOptions: {
                input: "./Assets/app.ts",
                output: {
                    entryFileNames: "[name].js",
                    chunkFileNames: "[name]-[hash].js",
                    assetFileNames: "[name][extname]"
                }
            },
        }
    }

This config allows Vite build to ./wwwroot/assets like pictured below:

With this config, the resulting manifest.json is:
{
  "../node_modules/.pnpm/@fontsource+roboto-condensed<EMAIL_ADDRESS>{
    "file": "roboto-condensed-latin-400-normal.woff",
    "src": "../node_modules/.pnpm/@fontsource+roboto-condensed<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto-condensed<EMAIL_ADDRESS>{
    "file": "roboto-condensed-latin-400-normal.woff2",
    "src": "../node_modules/.pnpm/@fontsource+roboto-condensed<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto-mono<EMAIL_ADDRESS>{
    "file": "roboto-mono-latin-400-normal.woff",
    "src": "../node_modules/.pnpm/@fontsource+roboto-mono<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto-mono<EMAIL_ADDRESS>{
    "file": "roboto-mono-latin-400-normal.woff2",
    "src": "../node_modules/.pnpm/@fontsource+roboto-mono<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-400-italic.woff",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-400-italic.woff2",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-400-normal.woff",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-400-normal.woff2",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-700-normal.woff",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
  "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>{
    "file": "roboto-latin-700-normal.woff2",
    "src": "../node_modules/.pnpm/@fontsource+roboto<EMAIL_ADDRESS>  },
<EMAIL_ADDRESS>{
    "file": "head-support-5c66e606.js",
    "isDynamicEntry": true,
    "src"<EMAIL_ADDRESS>  },
  "_htmx.min-f5bfe0ce.js": {
    "file": "htmx.min-f5bfe0ce.js",
    "imports": [
      "app.ts"
    ],
    "isDynamicEntry": true
  },
  "app.css": {
    "file": "app.css",
    "src": "app.css"
  },
  "app.ts": {
    "assets": [
      "roboto-latin-400-normal.woff2",
      "roboto-latin-400-normal.woff",
      "roboto-latin-400-italic.woff2",
      "roboto-latin-400-italic.woff",
      "roboto-latin-700-normal.woff2",
      "roboto-latin-700-normal.woff",
      "roboto-condensed-latin-400-normal.woff2",
      "roboto-condensed-latin-400-normal.woff",
      "roboto-mono-latin-400-normal.woff2",
      "roboto-mono-latin-400-normal.woff"
    ],
    "css": [
      "app.css"
    ],
    "dynamicImports": [
      "_htmx.min-f5bfe0ce.js",
<EMAIL_ADDRESS>    ],
    "file": "app.js",
    "isEntry": true,
    "src": "app.ts"
  }
}

The keys in the manifest will also differ if you have a different root like so:
 root: "./",
 outDir: "./wwwroot/assets",

In this case, Vite generates keys with the folder name like Assets/app.ts.
But to the first example above, in that case, the root is ./Assets, the key would be generated like app.ts. The ViteManifest class combines them string key = Path.Combine(this._base, chunk.Key); so the tag helper would look for key in manifest that will return null.
Since I have emptyOutDir: true, I should want to avoid setting outDir to ./wwwroot as there may be other content such as favicon, file uploads, other static assets like images used in the views, etc.
Proposals
Some ideas:

The key should not be combined, but not sure how it affects other configurations (there could be a lot of variables with vite.config.ts).
Be able to specify an exact path (within the wwwroot folder) instead of a Base.
In the tag helper, make sure the base is combined with the key when retrieving it.

I had a look at #21. For vite.config.ts, the base (which can only be absolute, ./ or empty string) seems to only affect Vite's asset paths for things like font urls in css files, but not keys in the manifest.

Tried setting the Base in appsettings.json to "assets" (no slashes). Possibly a bug - the key slashes are not normalized.

Hello.
If you want to use a custom directory, the set the Base option in your app settings and also in your vite.config.ta file like this:
https://github.com/Eptagone/Vite.AspNetCore/issues/21#issuecomment-1586316537

It works. Base option to /assets/, Vite base to /assets/ and link in tag helpers must be prepended with ~/assets/.
Thank you!


Tweak Gradle icon

Change style="fill:#02303a" to fill="#02303a" and reduce size a little. Makes more consistent with other icons too.

Good work - thanks!


Investigate hillshade

What would it mean to add hillshade to our map style?
Need available DEM vectortiles, which seems to exist here https://data.maptiler.com/downloads/dataset/hillshade/
These would not be time enabled. Instead, we'd need to see about serving these as static vector tiles as a separate datasource, and show them only at zoom levels where things that change in human time scales (dikes and levees, braided river channels, etc) don't appear obviously in the elevation/shaded relief

YES!!! Thank you @danrademacher - I thought we had a ticket on this already, but clearly not.
If we're going to do this, highly recommend we consider natural landcover, as well:
https://data.maptiler.com/downloads/dataset/landcover/#1.81/29.3/23.9

Proof of concept of hillshade vectors... @danrademacher pointed us to this interesting new vector mapping from Brandon Liu: https://github.com/protomaps/PMTiles, and I was inspired! I had built some test hillshade mbtiles last week, and converted to pmtiles today. Conversion was very quick, then uploaded to GCS, and rendered using Maplibre GL JS. Result looks like this: https://storage.googleapis.com/ee-layers/maplibre_pmtiles_hillshade.html

There are lots of tweaks and some updates to the data to make, but this seems promising

land cover / land use data policy and attribution:

Data policy
The GlobCover products have been processed by ESA and by the Université Catholique de Louvain. They are made available to the public by ESA. You may use the GlobCover land cover map for educational and/or scientific purposes, without any fee on the condition that you credit ESA and the Université Catholique de Louvain as the source of the GlobCover products:

Copyright notice: © ESA 2010 and UCLouvain
Accompanied by a link to our ESA DUE GlobCover website: http://due.esrin.esa.int/page_globcover.php

hillshade data information and attribution:

Citation information:
Originators: U.S. Geological Survey (USGS) Earth Resources Observation & Science (EROS) Center

Title: GMTED2010
Publication date: 2011

Suggested citation:
Danielson, J.J., and Gesch, D.B., 2011, Global multi-resolution terrain elevation data 2010 (GMTED2010): U.S. Geological Survey Open-File Report 2011–1073, 26 p.

Latest draft (live in staging) shifts to raster tiles, so we cancombine land cover - land use with hillshade data with compositing operations and produce one set of tiles.

Testing "full" color land cover / land use raster tiles:

That looks great! Just a note to remind myself and all around that we need to move these tiles to OHM-owned S3 before anything moves into production


lfs_dir_open fails with nested directories

Hi guys!
I am struggeling with this problem for a couple of days now.. I really really hope you guys can help me out :)
First of all, this is my LittleFS setup
static struct lfs_config cfg = {
    // block device operations
    .read  = read_callback,
    .prog  = prog_callback,
    .erase = erase_callback,
    .sync  = sync_callback,

    // block device configuration
    .read_size = 512,
    .prog_size = 512,
    .block_size = 32768,
    .block_count = 466944,
    .cache_size = 1024,
    .lookahead_size = 512,
    .block_cycles = -1
};

I am using an ARM A53 64-bit processor with a 16GB eMMC on which I mounted LittleFS. I don't use an OS, it's baremetal right now. I know read and write sizes are uncommonly big, however I cannot reduce this size as I am using a DMA with 512 bytes a transfer and all of this already setup in the drivers. I have changed the block_size, the block_count, the cache_size and the lookahead_size a million times, however it didn't solve my problem. It seems like the problem lies somewhere else.
My problem is that opening nested directories after they were created successfully fails!
I attached a log file of my running program, which should explain a lot:
lfs_dir_problem_log.txt
IMPORTANT, I changed the code in lfs.c for debugging as follows
(this change is inside the function static lfs_stag_t lfs_dir_find(lfs_t *lfs, lfs_mdir_t *dir, const char **path, uint16_t *id))
// find entry matching name
while (true) {
    printf("name before lfs_dir_fetchmatch: %s\r\n", name);
    tag = lfs_dir_fetchmatch(lfs, dir, dir->tail,
            LFS_MKTAG(0x780, 0, 0),
            LFS_MKTAG(LFS_TYPE_NAME, 0, namelen),
             // are we last name?
            (strchr(name, '/') == NULL) ? id : NULL,
            lfs_dir_find_match, &(struct lfs_dir_find_match){
                lfs, name, namelen});
    printf("name after lfs_dir_fetchmatch: %s\r\n", name);
    if (tag < 0) {
        return tag;
    }

    if (tag) {
        printf("Dir Entry found! tag = %d \r\n", tag);
        break;
    }

    if (!dir->split) {
        printf("No dir entry found! \r\n");
        return LFS_ERR_NOENT;
    }
}

Now I recognized looking at the logfile that the "name" gets corrupted inside lfs_dir_fetchmatch and by that also "path". Do you have any ideas what the problem is or any suggestions what to do next?
I already checked if writing to and reading from the eMMC works. It works perfectly.
Edit:
I need to mention that I can reproduce this corrupted path. The log-file looks exactly the same when the eMMC is erased and the program is restarted, with the only difference that LittleFS uses differents blocks, of course.

This will need a bit of time to look into, though I can say that LittleFS should work with the larger prog/read size without issue (it can get larger on RAM).
There's (unfortunately) a long-lived branch here that has a number of bug-fixes. It may be worth checking if this bug has been fixed on that branch:
https://github.com/ARMmbed/littlefs/pull/372

Thanks for your fast reply! I was very grateful for it and also tested it with the branch you told me. The error was still there, because it was not LittleFS's fault.
Thanks to a great colleague of mine who spent 2 hours debugging with me we found the problem. I created a global variable called mydir in main.c, wich was a self created struct with a char array of 256 bytes which held the directory-path. Then, in a different c-File I created another global variable called mydir, but of the struct type lfs_dir_t. This object I then gave to lfs_dir_open. Then, inside the function lfs_dir_find the line
    dir->tail[0] = lfs->root[0];
corrupted the path inside my mydir object in main.c.
Renaming the global variable mydir in main.c to a different name and calling it static solved my problem. I am very surprised that my compiler didn't give me at least a warning, but oh well, that's just how it is. Thanks anyway and have a good weekend!

Oh interesting, that's a strange bug. Yeah I would have expected the compiler to complain about multiple declarations unless one of the "mydirs" was declared extern.

They were not declared extern, but as I learned now, it's up to the compiler to choose if the global variable is extern or static if it is not specified. GCC chooses extern if it is not specified. Fun fact: A C++ linker would have given me a "multiple definition" error, whereas a C-Linker obviously doesn't.
Now LittleFS works like a charm and it is so much fun! Thanks a lot!


Remove ScalarObservable optimizations for map, filter, reduce, scan, etc?

There is an issue #1140 that just popped up (I was waiting for it).
I'm neither hot nor cold on these optimizations. So let's discuss them:
The Good:

The optimizations only effect observables created like Observable.of(a), but not Observable.of(1,2,3). They only effect ScalarObservables.
The optimizations doubled or tripled the speed of the operators for these Observables.
No one should be doing Observable.of(a).map(toSomethingElse) very often. It's code that only really shows up in demos and playground code normally, and/or it's an anti-pattern usually.
Generally it's a bad idea to mutate outer scoped variables inside of a map or filter handler.

The Bad:

Users trying to leverage map to create side effects might see funky behavior for ScalarObservables
The mapping or filtering functions are effectively no longer "lazy". If they're expensive or they create side effects, unexpected behavior can result.

AGAIN: I don't care if we keep them or remove them
The idea was that we'd implement them and try them out during beta.

I'm in favor of this in general, but this specific  effectively no longer "lazy". If they're expensive or they create side effects, unexpected behavior can result is bit concern. Every user of of(x) need to be aware of behavior if we're going with this.

We should make them lazy. If someone wants to optimize so their ScalarObservable chains are only invoked once, they can multicast with a ReplaySubject.

This all sounds good... I'll let this simmer overnight.
I think we should also try to add some "protips" or something to the docs that say things like "If you're creating chains like Observable.of(a).map(doSomething), you might be doing something weird."

I'm also rather neutral on this one, but I tend to agree with Paul.

Meh. Let's remove them for now. Individuals that want this behavior could always monkey-patch ScalarObservable I suppose.

Just before this is done in response to my issue can I double check that the problem I had is actually what's been discussed? I have a feeling it might just be a bug (see my latest comment on the issue)....
FWIW I do agree though, just not in my name! :smile:

There are two issues: 1. the optimization which were discussing removing here, and 2. an apparent bug in the optimization that needs to be fixed or removed with the optimization.


Update key-vault.md to keep same consistency with storage.md of .NET

Update the Key Vault index pages on docs.microsoft.com for JS with reference to the link
https://docs.microsoft.com/en-us/dotnet/api/overview/azure/storage?view=azure-dotnet

Docs Build status updates of commit 6df4beb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/key-vault.md
:warning:Warning
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)
Details

docs-ref-services/key-vault.md

Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/key-vault/general/overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/key-vault/general/overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/azure/key-vault/general/overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-certificates/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-certificates/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-certificates/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 36: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-keys/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 36: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-keys/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 36: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-keys/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-secrets/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-secrets/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/keyvault-secrets/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 47: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/arm-keyvault/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 47: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/arm-keyvault/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 47: [Warning] Link 'https://docs.microsoft.com/en-us/javascript/api/@azure/arm-keyvault/?view=azure-node-latest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 17dd2b8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

docs-ref-services/key-vault.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@maggiepint @scbedd Please review.

Also, you might want to fix the PR title (valut -> vault) since it will be the commit message unless you change it before you merge.

Docs Build status updates of commit 0948bcf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

docs-ref-services/key-vault.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit b8a6aa7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

docs-ref-services/key-vault.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

On this one too - can we change the file name to key-vault-index ?

Docs Build status updates of commit 86dc72b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

docs-ref-services/key-vault-index.md
:white_check_mark:Succeeded
View (azure-node-latest) View (azure-node-preview) View (azure-node-legacy)

docs-ref-services/key-vault.md
:white_check_mark:Succeeded

[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.
[Warning] Uid(azure.nodejs.sdk.landingPage.services.storagefileshare.detail) has already been defined in docs-ref-services/storage-file-share-readme.md.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Can we add a table with links to the previous version?

Hi @maggiepint ,
We can't find the source code and reference for the old version of keyvault.Do you have any idea or suggestion?

These are just the JS packages, but maybe there weren't older ones? @sadasant?

@heaths , any ideas?

@XuGuang-Yao I can assist with this. You're fine. Let me add a redirect for that file.

Oh. this is the same issue that @DuncanmaMSFT already merged. Thank you Duncan.

Specifically, resolved by these PRS:  master
Live


fix: make all unhandled errors fail tests

Prior to this, if an error was thrown before runTests was called, it would not be handled correctly.  I also made sure all the requires happen before anything else.

Thank you, for this PR, Oliver. It gives a useful output. However, I am wondering if there is an option which can be passed to allow for the the extended output. Something like the opposite of --bail.
Or, to do this through an npm script, would a new env variable have to be used?

So, are you thinking about https://github.com/freeCodeCamp/freeCodeCamp/pull/39024?  I.e. you'd want the option to see all the challenges with the wrong extension?
I think we should avoid adding more variables, at least to .env, since they increase the number of things we need to worry about when building.  However, doing something analogous to "test:full-output":"cross-env FULL_OUTPUT=true mocha --delay --reporter progress --allow-uncaught" seems fine to me.  That way it wouldn't appear in our automated testing, but would be available if someone wants to see all of the failing tests at once.
Does that sound reasonable?

@Sky020 the latest commit seems to do the job reasonably well.

Does that sound reasonable?

This is exactly what I expected. Something useful for debugging whether the error occurs from one problematic challenge, or is a failure on multiple files. Just so the test-challenges file does not need to be edited between tests.

Are we going to change the root  package.json to include the call to the full-output test?
"test:curriculum-verbose": "cd ./curriculum && npm test:full-output && cd ../",

Are we going to change the root package.json to include the call to the full-output test?

Good idea, I've added that.

Should this be added to the Contributors Docs?

Did you mean we should not be adding it? Because the this PR is adding it already here: https://github.com/freeCodeCamp/freeCodeCamp/pull/39477/files#diff-327956bb77017bdc1bbe530632292d2aR320

Did you mean we should not be adding it?

No, I just managed to filter out the .md file, and missed it. Ignore that last comment.


DAO Setup

Changelog
[1.0.2] - 2020-03-26
Added

Basic DAO contracts.
Absolute majority vote contract added.
Contract for freezing tokens (any ERC20 currently).
Global constrains contract.
Proposal voting test script.
Configured contracts list:

Part
Contract name

DAO core
Avatar

_
Controller

_
DAOToken

_
Reputation

Voting
AbsoluteVote

_
VotingMachineCallbacks

Schemes
Agreement

_
ContributionRewardExt

_
Locking4Reputation

_
LockingToken4Reputation

Global constraints
TokenCapGC

Changed

Replaced the contract migration script with our own
Configured work with local blockchain via npm

There is a problem with conflicting files


About relation complement function

Hi @baharefatemi ,
I recently reread your paper, and have some doubts about the relation complement function.
Though I have google some information about complement function, I still can't understand it well, and I'm not quite sure how the complement function of different functions are derived.

Specifically, the function sigmoid plus its complement function is equal to 1, while the function tanh plus its complement function is equal to 0. I don't understand the equation between complement function and its original function.

Hope to get your help, thank you.
Finnhh

Oh, I know this answer.
It's like bringing -x into the function f(x), then u will get f(-x). You can find f(-x) equals to f(x) after some transformation.
It's very interesting.


fix(consensus): await cancelled proposal to propogate panic

This change is

#2873  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 24, 10:12 AM EST: A user started a stack merge that includes this pull request via Graphite.


[Bug]: bal doc gives OOM for module-ballerinax-health.hl7v2

Description
When we generate API docs for module-ballerinax-health.hl7v2, it gives OOM. When we increase the heap memory to 4GB, it generates the API docs.
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> API Docs
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This issue has been solved with https://github.com/ballerina-platform/ballerina-lang/issues/41448 and https://github.com/ballerina-platform/ballerina-lang/issues/41384.


easystar C3 plugin 'diagonal disabled bug'

There's a bug in the original easystar-0.4.1-custom.js

It's a bug inside the EasyStarJS library. The fix is quite simple and is already present in the up-to-date version. However, my plugin use the v0.4.1 version of the library... Until I find the time to update the plugin files, and if you're not afraid to delve into the javascript, you can edit the "easystar-0.4.1-custom.js" file, and correct all 8 calls to isTileWalkable(). You need to add "searchNode" as the 5th parameter.

Fix: change all occurrences of isTileWalkable(collisionGrid, acceptableTiles, searchNode.x, searchNode.y - 1) with isTileWalkable(collisionGrid, acceptableTiles, searchNode.x, searchNode.y - 1, searchNode)

thanks.


Fixes "Artist at Artsy" and "Show link" buttons

Fixes #2195
As discussed in the issue, both buttons were wrapped in an ARNavigationButtonsViewController. Not sure if the buttons could have been added in a cleaner way 🤔 (feedback is welcome).
End result:

cc. @orta @alloy

Thanks a whole lot for taking the time @pedrovereza! 🙌
Unfortunately we’ve been dealing with some other issues that make master unstable, so I’m waiting till we’ve had the time to deal with that (hopefully this week) before merging.

@pedrovereza Thanks so much for the work! You are my personal hero of the day 👏
I’ve updated your PR slightly in #2232, so closing this one in favour of that.

Nice one  - sorry, been on my honeymoon 👯♂


Committees: Committee pages missing Recent Activity

It looks like the "Recent Activity" sections on committee pages are not updating. The last activity is from 11/2017, see Construction Committee for example: https://boardagendas.metro.net/committee/construction-committee-ebbc3e5b8887/
The newest committee, which met for the first time 7/19/18, has no recent activity listed: https://boardagendas.metro.net/committee/operations-safety-and-customer-experience-committee-b28353454c39/

Is it possible to please hide/disable this section on the website until the issue is resolved?

@reginafcompton Is it possible to please hide/disable the "Recent Activity" section on committee pages until this issue is resolved?

It looks like this same issue is occurring on Board Member pages, as well. Examples:
https://boardagendas.metro.net/person/ara-najarian-a9c58166e1da/
https://boardagendas.metro.net/person/jacquelyn-dupont-walker-851703b7b19d/

I spent a little time investigating this issue. It looks like the Legistar API contains some unexpected information. I'll summarize.
The following board reports have actions or histories from 2018. The left column shows the date of the action, and the right column shows its url in Legistar.
Relevant queries
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4846
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4729
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4862
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4945
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4897
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4879
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4759
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4984
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4840
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4600
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4861
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4920
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4847
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4535
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4950
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4898
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4904
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4608
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4882
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/5058
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/5004
 2018-05-24 | http://webapi.legistar.com/v1/metro/matters/4804
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4880
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4793
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4852
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4826
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4750
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4892
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4849
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4860
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4604
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4886
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4639
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4831
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4928
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4827
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4738
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4687
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4839
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4936
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4866
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4806
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4927
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4709
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4709
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4796
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4746
 2018-04-26 | http://webapi.legistar.com/v1/metro/matters/4798
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4784
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4783
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4856
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4757
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4692
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4820
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4739
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4493
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4734
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4743
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/3631
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4857
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4720
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4823
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4704
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4853
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4736
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4822
 2018-03-22 | http://webapi.legistar.com/v1/metro/matters/4748
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4708
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4726
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4521
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4574
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4522
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4617
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4624
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4546
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4603
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4583
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4605
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4612
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4705
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4640
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4541
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4545
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4632
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4730
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4412
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4523
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4581
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4627
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4631
 2018-01-25 | http://webapi.legistar.com/v1/metro/matters/4728

All these actions seem to come from the same organization, the Board of Directors, i.e., they all have ocd-organization/42e23f04-de78-436a-bec5-ab240c1b977c as their related organization id.
The MatterBodyName for these entries, however, is not always the Board of Directors. So, what's going on?
The MatterHistoryActionBodyName on their respective histories page points to "Board of Directors - Regular Board Meeting." For example, http://webapi.legistar.com/v1/metro/matters/4546 has "Planning and Programming Committee" as the MatterBodyName, http://webapi.legistar.com/v1/metro/matters/4546/histories has the "Board of Directors"
as the MatterHistoryActionBodyName.
Our scrapers determine the organization responsible for an action by looking at the MatterHistoryActionBodyName. This has worked well for previous legislative sessions.
@shrayshray - did something change about how Metro enters data about actions in 2018?

@shrayshray - sure, we can disable. I can do that on Monday.

@reginafcompton I'm going to do my very best to confirm your observations and hopefully give a clear explanation!
The MatterBodyName is the committee which first receives the report. The process for Board Reports is they first go to a Committee meeting, and after review, the Committee determines whether the Report should go to the full Board of Directors, at a Regular Board Meeting, for a vote. The Regular Board Meeting is where the Final Action takes place (Approved/Failed/No Action, etc.), as recorded in the Minutes History.
When Legistar was first implemented in 2015, the Minutes History was not being utilized. The Board Secretary's office has recently started going back and entering Minutes Histories on reports, starting in 2015 and working forward, chronologically.
So, in this example, you can see there's a full history recorded from "Finance, Budget and Audit Committee", to "Executive Management Committee", to "Board of Directors".
The MatterBodyName should be "Finance, Budget and Audit Committee", but I'm not sure what the MatterHistoryActionBodyName holds? Is it just the final action from "Board of Directors", or are there multiple entries, one for each action recorded?
What's going on with the reports on your list, from 1/2018-5/2018?
My guess is during that time the Board Secretary's Office was entering the Final Action (whatever happened in the Regular Board Meeting) consistently, but was not entering in History the actions taken in Committees prior to going to the full Board; perhaps focusing instead on getting the backlog of missing Histories entered. Though it looks like they haven't been entering Final Actions consistently since 5/2018 either.
Omar is going to speak with them about this next week.
Does the above make sense otherwise?

@shrayshray - I disabled the "Recent Activity" view for affected committees, e.g., https://boardagendas.metro.net/committee/operations-safety-and-customer-experience-committee-b28353454c39/
Your explanation makes a great deal of sense (particularly, "the Board Secretary's Office ... was not entering in History the actions taken in Committees prior to going to the full Board") - this explains why I only see histories related to the Board of Directors. Can you let me know if your suspicion is accurate?
The MatterHistoryActionBodyName holds the name of the organization responsible for the action. So, given your explanation, all board reports should have at least two actions (or "histories"): one by the committee, one by the board.
Your above cited example in the Legistar API - this has ALL the expected actions!
Another example in the Legistar API - this has just the action from the board.

@hancush @jmithani Could you please also disable "Recent Activity" display on the Planning and Programming Committee, Finance Budget and Audit Committee, Executive Management Committee and Construction Committee? It looks like only the Operations, Safety ... Committee had this section disabled, but all the other committees are also showing the most recent activity as 2017.

@shrayshray sure thing! how would you like us to prioritize this with the existing milestone issues?

@hancush do you think you could get to it before 9/12? It would be nice to have it removed before the next round of agendas are posted, which will happen on 9/13.

sure thing, i can actually get on it this afternoon! will update.

changes are live on the staging site: https://lametro.datamade.us/committees/
if the committees all look ok to you, @shrayshray, i can deploy in the am!

@hancush looks great! yes, please deploy!

done! i'll leave this issue open, since we didn't address the root data issue, but i'll move it back into the icebox on our project board for now.


Planning of CranSurvey

What is CranSurvey?
CranSurvey can help you collect the answers of the survey in your website.  Users can complete the survey within a prompt window on the website with just a few clicks.
In the future, CranSurvey may collect performance and visitors data to help the website manager improve their website.
Planning of CranSurvey
The first alpha version of the test may be released in September 2023, and there will be a stable version in December.
Actually, we are still working on it and have a lot to do. We welcome contributions.

to follow the updates/announcements for CranSurvey, join our Discord channel: https://discord.gg/KXSRqpWZTB

[ ] /dash/index
[ ] /dash/surveys
[ ] /dash/users
[ ] /dash/edit
[ ] /dash/results

there is a preview link: https://csur-preview.vercel.app


Can't login with admin/123 use latest docker image version(casbin/casdoor v1.67.0)

from  1.63.0  - 1.67.0  can't login :
Uncaught (in promise) SyntaxError: Unexpected end of JSON input
at AuthBackend.js:62:22

db version : postgres:14-alpine

@bobhu2k is v1.62.0 OK?

@Abingcbc @ComradeProgrammer

meet same issue in latest version of casdoor

@ComradeProgrammer

Commit https://github.com/casdoor/casdoor/commit/b4bf734fe82df908bede10b1a554d56bd221255e add cors filter.  After 1.63.0 image, you need to set origin in app.conf, make sure the headorigin is same as origin in app.conf https://github.com/casdoor/casdoor/blame/master/routers/cors_filter.go#L34-L37. Or you can choose not to fill it in and there will be no origin judgment.

@leo220yuyaodog  got it,tks!

@leo220yuyaodog but when i config origin(eg: http://localhost:3000) ,how to use admin to login in (http://localhost:8000)?

@leo220yuyaodog but when i config origin(eg: http://localhost:3000) ,how to use admin to login in (http://localhost:8000)?

See the document https://casdoor.org/docs/basic/server-installation#production-mode. You can build the frontend.

the origin config  support multiple domain？

This issue just happened to me. Following a binary search, I found the fix to be setting copyrequestbody = true in the app.conf. Apart from the DB settings mentioned in the setup guide, I didn't change anything.


Kubernetes secrets provider is documented

The documentation in:

[ ] the GitHub repo
[ ] the website

are updated to include information on the Kubernetes Secrets provider.

This issue was moved to cyberark/secretless-docs#93


fix(fiatconnect): fiat details screen button updates

Description

Change button text to "Submit & Continue"
Include button as part of scroll view (this doesn't make a difference currently, but if / when there are more input fields, it scrolls correctly to the field in focus)

https://user-images.githubusercontent.com/5062591/184046220-a9769403-b3fc-4677-a6de-b4e2dfa778df.mp4
Other changes
N/A
Tested
Manual, unit tests
How others should test
Navigate to fiat details screen and ensure button is "Submit & Continue"
Related issues

Fixes ACT-181

Backwards compatibility
Yes

Hey @MuckT, We have verified above task on Latest Android Alfajores Build V1.39.1 & updated status in test rails.

"Submit & continue" button appears at the bottom when user navigates to the "Enter Bank Information" screen.

Test rail links:
Android 11: https://valoraapp.testrail.io/index.php?/tests/view/61285
Devices: Samsung Galaxy F41(11.0)
CC: @satish-ravi
Thanks..!!

Hey @MuckT, We have verified above task on Latest iOS Alfajores Build V1.39.1 & updated status in test rails.
Observation :

"Submit & continue" button appears at the bottom when user navigates to the "Enter Bank Information" screen.

Test rail links:
iOS 15: https://valoraapp.testrail.io/index.php?/tests/view/61841
Device: iPhone 13 mini(15.1.1)
CC: @satish-ravi
Thanks..!!


[KAFKA-7038] Support AdminClient Example

Add AdminClient Example
include describeCluster , createTopics , listTopics , describeTopics and deleteTopics .
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc ~ @ijuma

@darionyaphet Thanks for your patch. https://github.com/apache/kafka/commit/47933088decc1bb33374b020e8f23ab7947285f2 offered the Admin example by the java documentation. Is that enough to be a tutorial? If not, how about writing this patch as java documentation?


SecurityError: Operation is insecure

We have started seeing Operation is insecure in our bugsnag error reporting. We use amplitude with next js 13
Expected Behavior
Ability to use amplitude client without the Security Error
Current Behavior
Amplitude client "@amplitude/analytics-browser": "^2.3.2" is not able to access local storage.
Possible Solution

Steps to Reproduce

Environment

JS SDK Version: "@amplitude/analytics-browser": "^2.3.2",
Installation Method: Yarn
Browser and Version: Chrome Mobile 126.0, Mobile Safari 16.6.0, Mobile Safari 17.5.0

Hi @ashishkpoudel<EMAIL_ADDRESS>should fix this issue.

Hi @ashishkpoudel<EMAIL_ADDRESS>should fix this issue.

Thank you for the fix


"select_multiple" additional pivot parameters

Hello,
I have a table http://prntscr.com/g48995
In my controller the logic of this table is here: http://prntscr.com/g489ne
How can I pass additional parameters to this table? For example I want to append Poll to my article, and I need that the type of this poll will be "article".

Hi @VilmantasSaulys ,
There's no solution for this already built, sorry.
Cheers!

@tabacitu Wondering if this ever got implemented?