What are some cool iOS code examples to checkout?

Replicating UIScrollView’s deceleration with Facebook Pop
Animating a scroll view ... from scratch.

Lots of control ideas at Cocoa Dev Blogs!

https://twitter.com/cocoadevblogs


Indexed DB getAll(), openKeyCursor() and objectStoreNames

There are a handful of new methods/attributes in the Indexed DB "Second Edition" with implementations in both FF and Chrome that we'd like feedback on. These are additions of new methods to existing interface objects in the API, and do not change the behavior of any existing methods. All can be feature detected.
IDBObjectStore.getAll()
IDBObjectStore.getAllKeys()
IDBIndex.getAll()
IDBIndex.getAllKeys()
Like get()/getKey(), these take a query (null or key or key range), but also an optional count, and yield a JS Array with all matching results. The alternatives today are issuing multiple parallel get() calls (if keys are known) or iterating a cursor over the range (if keys are not known). Avoiding multiple event dispatches can be a significant performance improvement and reduce main thread contention, as well as simplifying application logic.
IDBObjectStore.openKeyCursor()
IDBIndex has openCursor() and openKeyCursor(), where the latter avoids fetching values and saves on the transport/deserialization overhead when only existence testing is known, e.g. for joins. This gives IDBObjectStore the same lighter-weight option in addition to the existing IDBObjectStore.openCursor()
IDBTransaction.objectStoreNames
This is a convenience attribute that yields the stores in the scope of the transaction, as specified when starting the transaction. For upgrade transactions it yields the same thing as db.objectStoreNames. This attribute has shipped (unprefixed, not behind a flag) in FF for many versions.

NOTE: There are other additions marked "new in this edition" in the ED; we are not as far along with design/review/discussion of those. Also, there are discussions around integration with Promises, improvements to indexes and transactions, more powerful queries, and a several other additional features - see https://github.com/w3c/IndexedDB/issues - that haven't made it into the ED. So right now we're hoping for feedback on just the subset above.

Questions!
IDBObjectStore.getAll(), IDBObjectStore.getAllKeys(), IDBIndex.getAll(), and IDBIndex.getAllKeys() look great. Glad they're being added!
The fact that these methods return an Array is interesting from the perspective of ES6 Iterators, Generators, and the protocol they expose. It seems like cursors are, in some way, a userland version of these (in much the same way that IDBRequest is sort of a user-land Promise). Has any thought been given to some form of unification and/or methods that return ES6 iterators (perhaps instead of the current Cursor)?
IDBObjectStore.openKeyCursor() looks good.
IDBTransaction.objectStoreNames similarly seems useful.

Cursor iteration is async, so we're awaiting guidance on Observables or whatever the latest thinking in ES-land is there. Since that's unsettled it seems premature to tackle that now.
Likely we'll tackle Promisifying the existing API first - e.g. via what's proposed at https://github.com/inexorabletash/indexeddb-promises - then tackle async iteration when the path forward is clearer.

Hey @domenic and @littledan: what's the latest on async iteration and generators and what would you recommend for this case? Reifying all the results seems a bit obnoxious if we don't need to.

It advanced to stage 2 at TC39 yesterday. My take on the room is that although the spec is done, a number of people in the room (@dherman most notably) would like to see it bake for a while in Babel and other places before advancing it. I can't recall any specific criticisms of the API though, just a general feeling of unease from a few members. The editor, @zenparsing, also made the good point that since async functions are still at stage 3, it's better to wait for those to get some implementations before trying to push async iterables too fast.

My take is that async iterables seem to be moving along pretty smoothly, and we have a pretty natural protocol proposed for it. It's nice to have this use case in mind in evaluating the proposal, which you can read about here: https://github.com/tc39/proposal-async-iteration . Streams do a pretty good job of exposing something that's sorta like async iterables, but more ergonomic to use directly, which can go and upgrade to them later, but waiting also seems like a fine strategy. Observables are still in more flux, with a pretty radical possible idea for doing them in terms of Promises and callbacks on the table.

Taken up on TAG telecon 20-07-2016.

@inexorabletash see our minutes here: https://pad.w3ctag.org/p/20-07-2016-minutes.md - is there any more recent info or thinking you can share with us on this? we'd like to get feedback sent out...

The specific methods mentioned in the issue shipped in Firefox and Chrome several months ago now, as the simple "give me a bunch of results" was such a clear performance win.
I'm continuing to look at integrating IDB with Promises, and Observables make sense for cursor-type operations. I don't think there is anything actionable here for the TAG at this time.

On Jul 20, 2016, at 2:32 PM, Daniel Appelquist<EMAIL_ADDRESS>wrote:
@inexorabletash see our minutes here: https://pad.w3ctag.org/p/20-07-2016-minutes.md - is there any more recent info or thinking you can share with us on this? we'd like to get feedback sent out...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Oh!
https://developer.mozilla.org/en-US/docs/Web/API/IDBObjectStore/getAll
https://developer.mozilla.org/en-US/docs/Web/API/IDBObjectStore/openKeyCursor
According to the articles, these return IDBRequest (iterator), rather than an Array type.

Everything in IDB returns an IDBRequest, which populates the result property when the request is completed. (This is what happens when you implement an async API before Promises are added to the DOM, and don't have a time machine handy.) getAll() was specified to yield (via request property) an Array of results.
I think the comments here and in the TAG minutes hint at a handful of inter-related questions.

Q: Why do we need getAll() versus some iterable type? A: That's what IDBCursor is for, but the performance (as designed) is poor for many scenarios since script must explicitly pull the next result via continue() (vs. a push-type async iterator)
Q: Should it be an Array or some other type? Frozen? A: shipped as just Array. Could probably be made FrozenArray. Today, the result on IDBRequest - which can be any cloneable data - is not frozen (etc)
Q: Do we want to be extending the API like this, vs. exploring async iterators A: This was such a common request/clear performance win that it made sense. In parallel, exploring adapting IDB to work with Promises (see https://github.com/inexorabletash/indexeddb-promises) and pursuing Observables for pull-type iteration (i.e. adapting cursors) makes sense as those firm up.

Q: Why do we need getAll() versus some iterable type? A: That's what IDBCursor is for, but the performance (as designed) is poor for many scenarios since script must explicitly pull the next result via continue() (vs. a push-type async iterator)

In parallel, exploring adapting IDB to work with Promises (see https://github.com/inexorabletash/indexeddb-promises) and pursuing Observables for pull-type iteration (i.e. adapting cursors) makes sense as those firm up.

Hmm, this needs serious discussion. As @littledan said upthread, observables are very speculative right now and async iterators are probably a better bet. I also don't understand why you think observables make sense for this use case or are faster: async iterators are strictly more powerful, and if you pull them as fast as possible they should get you results just as fast as a push solution would---with the added benefit that you can control your memory usage and consumption speed, whereas observables are little better than arrays in that they push things to you without any control over the flow rate.

I had an offline sync up with @littledan and understand the async iterator proposal better (I simply hasn't spent any time with it yet). Agreed it's a better fit for cursors. I'll be exploring it soon.

On Jul 20, 2016, at 3:12 PM, Domenic Denicola<EMAIL_ADDRESS>wrote:
Q: Why do we need getAll() versus some iterable type? A: That's what IDBCursor is for, but the performance (as designed) is poor for many scenarios since script must explicitly pull the next result via continue() (vs. a push-type async iterator)
In parallel, exploring adapting IDB to work with Promises (see https://github.com/inexorabletash/indexeddb-promises) and pursuing Observables for pull-type iteration (i.e. adapting cursors) makes sense as those firm up.
Hmm, this needs serious discussion. As @littledan said upthread, observables are very speculative right now and async iterators are probably a better bet. I also don't understand why you think observables make sense for this use case or are faster: async iterators are strictly more powerful, and if you pull them as fast as possible they should get you results just as fast as a push solution would---with the added benefit that you can control your memory usage and consumption speed, whereas observables are little better than arrays in that they push things to you without any control over the flow rate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

To clarify, I don't want to have an observable vs async iterator debate (neither is at Stage 3 yet), but I think async iterators, for one, would be a good fit here. As a transitional possibility before async iterators are there, it would be possible to do something analogous to streams and give cursors a .next() method which returns a Promise of an IterationResult. In my opinion, this is fairly clean to use directly, and it has a clear upgrade path to async iterables. I'm looking forward to hearing more from @inexorabletash 's exploration.

And also to clarify, I'd updated my comment after @domenic started replying (hence, my text and his quote differ). Cursors need a pull-type model, which is indeed a better fit for async iterators.
The proposal at https://github.com/inexorabletash/indexeddb-promises shows how cursors+promises already get a non-terrible syntax with the rest of the proposal (search for "fetch all keys in a range using a cursor") but aligning that with async iterators makes sense. I've got @littledan nearby if I have questions. (And feedback on that repo is welcome)
...
So... is there anything actionable here or should I close out this issue?

Noted.


Marathon kills container when requests increase

I deploy Docker containers on Mesos(0.21) and Marathon(0.7.6) on Google Cloud Engine (Ubuntu 14.04)
I use JMeter to test a REST service that run on Marathon. When the concurrent requests are less than 10, it works normal, but when the concurrent requests are over 50, the container is killed and Mesos start another container. I increase RAM, CPU but it still happens.
This is log in mesos slave:
E0116 09:33:31.554816 19298 slave.cpp:2344] Failed to update resources for container 10e47946-4c54-4d64-9276-0ce94af31d44 of executor dev_service.2e25332d-964f-11e4-9004-42010af05efe running task dev_service.2e25332d-964f-11e4-9004-42010af05efe on status update for terminal task, destroying container: Failed to determine cgroup for the 'cpu' subsystem: Failed to read /proc/612/cgroup: Failed to open file '/proc/612/cgroup': No such file or directory

Marathon only kills tasks, when it has health checks defined and they fail consecutively for the configured amount of time.  Could you please post the relevant log lines?

I solved this issue by increase the RAM for container


catch and log exceptions thrown in waiters added to KafkaFuture

This PR is based on the changes in #4033 so we can hopefully merge them together as part of KAFKA-6018
Exceptions thrown in actions added with KafkaFuture.addWaiter(...)
could prevent other waiting actions from executing, possibly breaking
KafkaFuture.allOf(), so it seems advisable to wrap actions to catch
and log exceptions before making this API public.
cc @cmccabe @ijuma @hachikuji

So, just to give a little more context here, I generally wanted to follow the APIs laid down in CompletableFuture when writing KafkaFuture.  However, I was unable to do this with the BiConsumer stuff, because it relies on a JDK1.8+ exception, CompletionException.  That's the main reason why I never implemented KafkaFuture#whenComplete and similar APIs... they would be confusingly different from the corresponding CompletableFuture APIs, since we don't have CompletionException.
On the whole, I think exposing addWaiter is not a bad solution.  It's clear that it's different from CompletableFuture, so it will be obvious what we need to change when we switch over to CompletableFuture (hopefully).
Please do not add logging to KafkaFuture, though.  It's not our job to log user's exceptions or future completions.  The standard Java classes don't, and for good reason: we don't know what users are doing or why, which makes reasonable logging impossible.  KafkaFuture users can easily add their own context-appropriate logging if needed.
Also, all waiters should get any exception from the future, if there is one.  Otherwise, the waiters may wait forever.

@cmccabe and I discussed this offline, there was a misunderstanding about which exceptions I was talking about. We also came to the conclusion that logging wasn't great but probably still better than swallowing the exception.
Based on the ongoing KIP-218 discussion, I decided to rebase my fixes on top of Steven Aerts' changes in https://github.com/apache/kafka/pull/4033 so hopefully we can merge those two PRs together as part of KAFKA-6018 @cc @steven-aerts

Yes that would require addWaiter return a new future that can be completed exceptionally in case the action throws an exception. The original future would still be completed normally in both cases though.
My main objective was to fix the exception handling before the api is public to ensure bad acting actions don’t break the expectation that every waiting action is invoked once. This is especially important for KafkaFuture.allOf to work properly in all cases.

@steven-aerts added a short test for actions throwing exceptions

@xvrl: Thinking about it a little bit more, I think implementing whenComplete is a more elegant solution.  How about something like this? https://github.com/apache/kafka/pull/4316 ?

@cmccabe sounds reasonable, they're essentially the same if you choose the ignore the returned future, but having the option to know the result can be useful. I would have thought we would need to worry about having to propagate any cancellation back up the chain, but apparently CompletableFuture pretty much just ignores that problem, so we're good.

closing in favor of https://github.com/apache/kafka/pull/4316, which is getting incorporated into  https://github.com/apache/kafka/pull/4033


Stop supporting bower in a version 2.0?

We used bower in the days where npm didn't have flatten dependencies support. This has changed a long time and people has moved towards npm for package management for some time by now.
The goal of this issue is to collect community feedback (if any) about moving this path forward.

Its time, as bower itself tells users: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

Apparently closed by #926

@rxaviers I haven't really fully dropped bower, just one package. So this should stay opened for a bit

Thanks


Use Alt/Az when selecting neighboring runs

Issue: The find_run_neighbours() method uses ICRS coordinate system when selecting the run neighbors, which may lead to runs with very different zenith distances to be stacked when evaluating the background.
Suggestion: use Alt/Az instead of ICRS in find_run_neighbours():

introduce az_bins and alt_bins keywords to the configuration file with the following behavior: if integers, they will define the Az/sin(Alt) grid to be used when searching for neighbors; if lists, they will define the Alt and Az grid bin edges;
add the alt/az neighboring grid creation in BkgMakerBase.from_config_file();
change the pointing_delta argument of  find_run_neighbours() to neighboring _grid or similar and provide the grid from step 2 here.

I would suggest to follow the LST behaviour here, which is to match in sin(delta) and cos(zenith) where delta is the angle to the magnetic field. See for example https://github.com/cta-observatory/lst-sim-config/issues/2
The only problem with that is that it then becomes nontrivial to define a distance threshold. We usually only select the n nearest nodes, but with no notion of an absolute distance...
One could of course create a grid and group runs that end up in the same cell


Docker file for the prebuilt Docker image

Hello,
I'd like to add pyvips into the Docker image. Would it be possible for you to share the Docker file that was used to build the Docker image here?
Many thanks in advance!

You can access these here https://github.com/TissueImageAnalytics/tiatoolbox/blob/develop/.github/workflows/docker-publish.yml


Ranking Loss

Hi developers,
Looking at the code, I see you use the MarginRankingLoss, while Nogueira et al. suggest to adopt the cross-entropy loss. Is there a specific reason for this choice?

Hi,
Our OpenMatch supports MarginRankingLoss and Cross-Entropy Loss, you can set the task as 'classification' for Cross-Entropy Loss, or 'ranking' for MarginRankingLoss :)
Kaitao

Thank you for your answer, but I did not explain myself clearly.  I was wondering if the ranking loss has some advantages w.r.t. the Cross-entropy. Which should I choose to maximize the performance of BERT?

We found Cross-Entropy Loss is more stable for BERT training, especially in the scenarios when query-doc labels are not sufficient.


Request: refresh button for document content in the Web UI

Request for a small convenience  feature:
When viewing a single document in the ArangoDB Web UI, it would be very handy to have a refresh button to reload the content of that particular document. (E.g. next to the "Add new document" button in the top right section of the page).
E.g. if you're testing and monitoring a specific document for changes, you currently have to:

reload the entire webpage (building up the entire navigation pane, etc.)
click back to the collection and then to the document again

So a "just reload the specific document that I'm viewing right now"-button would be wonderful when developing.

you can have this now already if you run
RETURN DOCUMENT(_key)
in the query pane. But probably still a good idea.

You're right, good point!
I guess that so far I hadn't really thought about it in that way, because in the query pane I'm basically always experimenting with complex queries before integrating them in my code. :smile:

It would already help if one could click on the menu entry or tab that one is currently on in order to refresh the view. This is not possible right now, you have to change to another menu entry or tab and then switch back.


Fix typo in ProblemBuilder

@bot-gradle merge

I've triggered a build for you. Click here to see all failures if there's any.


⚠ 한경주요지수-코스피200 has degraded performance

In 24bdd1b, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 5483 ms

Resolved: 신규상장 performance has improved in 88a98d3.


shorter more precise bars

bars fill up in octets rather than just "empty" and "full"
reduce total bar width by 10 to leave more space for artist name

example here:
https://gist.github.com/casperdcl/41c89c9eab48e7526ed57888a9c38bc0

hey there, thanks for the pr. i'll test and take a look when i can.


bug(dashboard): bad argument #1 to 'randomseed'

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
VIM v0.10.2 Build type: Release LuaJIT 2.1.1713484068
Operating system/version
Ubuntu 22.04
Describe the bug
After updating to commit aebffe5, launching neovim returns the following error:
Error detected while processing UIEnter Autocommands for "*":
Error executing lua callback: ...cal/share/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:10: bad argument #1 to 'randomseed' (number expected, got no value)
stack traceback:
	[C]: in function 'randomseed'
	...cal/share/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:10: in main chunk
	[C]: in function 'require'
	...a/.local/share/nvim/lazy/snacks.nvim/lua/snacks/init.lua:26: in function '__index'
	...a/.local/share/nvim/lazy/snacks.nvim/lua/snacks/init.lua:126: in function <...a/.local/share/nvim/lazy/snacks.nvim/lua/snacks/init.lua:123>

Steps To Reproduce

Update to the latest commit
Try opening dashboard

Expected Behavior
Dashboard opens.
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/snacks.nvim", opts = { dashboard = { enabled = true }, }
    },
    -- add any other plugins here
  },
})

fixed


Remove underscore and clone libs and refactor code using native ES6 functions.

The following files are using functions provided by underscore and clone which can be replaced by native ES6 code.

metadata\evaluator\filter\arrayMetadataFilter.js
metadata\evaluator\filter\defaultMetadataFilter.js
metadata\evaluator\filter\entityMetadataFilter.js
metadata\evaluator\metadataEvaluator.js
metadata\model\modelParser.js
metadata\validator\metadataValidator.js
metadata\MetadataProvider.js

What do you think??, is there a reason to not change unsderscore to native ES6??

I don't oppose to it, I just don't find it a priority. Feel free to do it :smile:

@andrerpena with this we reduce some dependencies, we use native es6 syntax and we could make the code for metadata management even more clear to read and understand.

Great! i will start to do this!


Cannot install extension pack on github.dev even if all extensions it contains are web enabled

Repro

Using github.dev, try installing the Github Markdown Preview extension pack

Bug
I can't install the extension even though the four extensions in the pack are now web enabled:

Seems similar to #131885 but I'm  using the insiders build: df115e761ae11cf87ca569ca1824b7257099553a

We are working with Marketplace team to enable extension packs as web extensions by default. Mean while you can fix this by republishing your pack.


chore: bump swc and helpers

Summary
Bump swc-plugins and swc-helpers
@swc/helpers changes:

https://github.com/swc-project/swc/pull/8076
https://github.com/swc-project/swc/pull/8097

Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

 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.jserfeng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Bug]: Error running puppeteer within GCP Cloud Run jobs

Minimal, reproducible example
const puppeteer = require("puppeteer");

async function webscraper () {
    const browser = await puppeteer.launch({
        headless: "new",
        args: ["--no-sandbox", "--disable-setuid-sadbox"],
        // args: ["--window-size=1920,1080"],
      });
      const ibContext = await browser.createIncognitoBrowserContext();
      const page = await ibContext.newPage();
      await page.setViewport({width: 1920, height: 1080});

      await page.goto("https://www.forex.com/en-us/market-analysis/economic-calendar/", {waitUntil: "load"});

      await page.waitForSelector(".icon-filter").then(() => console.log("Found the filter"));
      browser.close();
    }

    webscraper().catch(err => {
  console.error(err);
  process.exit(1); // Retry Job Task by exiting the process
});

Error string
Waiting for selector... failed: Waiting failed: 30000ms exceeded at Timeout.
Bug behavior

[ ] Flaky
[ ] PDF

Background
Originally, I deployed a webscraper via Google Cloud Functions. Recently, this functionality stopped working and instead producing the above error.
I found a way around this by upgrading to the newest puppeteer & node 18. But this resulted in a new error noting that the instance could not find chrome. Checking the puppeteer docs, I found that implementations with cloud functions are not entirely recommended. Instead, they ask that we use CloudRun to ensure that all dependencies are installed in order from launching the chrome browser.
If I download the debian dependencies listed here[1], I get an error noting that the browser could not be launched. Even building my job with the base image of "ghcr.io/puppeteer/puppeteer:20.8.2", I receive an error noting that the chrome browser cannot be found:
======================
If I add an ".puppeteerrc.cjs" file to my job directory, I finally received the 30 second timeout:
------error below------
TimeoutError: Waiting for selector .icon-filter failed: Waiting failed: 30000ms exceeded at Timeout. (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WaitTask.js:71:32) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7)
------EOF------
-----My dockerfile-----
FROM ghcr.io/puppeteer/puppeteer:20.8.2
COPY package*.json ./
RUN npm i
COPY . .
ENTRYPOINT ["node", "index2.js"]
-----EOF-----
-----Also tried-----
FROM ghcr.io/puppeteer/puppeteer:latest
USER root
RUN apt-get update
&& apt-get install -y apt-utils ca-certificates fonts-liberation libasound2 libatk-bridge2.0-0 libatk1.0-0
libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 libgcc1
libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1
libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1
libxss1 libxtst6 lsb-release wget
RUN apt-get -y install sudo
RUN sudo apt-get install -y xdg-utils
COPY package*.json ./
RUN npm install -g<EMAIL_ADDRESS>RUN npm i
COPY . .
ENTRYPOINT ["node", "index.js"]
-----EOF-----
------Packages.json-----
{
"name": "jobs",
"version": "1.0.0",
"description": "Node.js sample for Cloud Run jobs",
"main": "index.js",
"scripts": {
"start": "node index.js"
},
"author": "Google LLC",
"license": "Apache-2.0",
"dependencies": {
"firebase-admin": "^10.2.0",
"puppeteer": "^19.2.0"
}
}
------EOF-----
[1] GCP Puppeteer example: https://codelabs.developers.google.com/codelabs/cloud-starting-cloudrun-jobs#3
MinimumRepro.zip
Expectation
I expect the script to run on GCP using the puppeteer base image as it does on my local computer.
Reality
I receive an error 30 seconds after job execution.
Puppeteer configuration file (if used)
No response
Puppeteer version
20.8.2
Node version
18
Package manager
npm
Package manager version
9.5.1
Operating system
Windows

Apologies for the misguiding link. I grabbed the dependencies from the troubleshooting links in puppeteer docs
https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#chrome-headless-doesnt-launch-on-unix

Could you please format the issue properly? it's difficult to read. Also, make sure that after you modify the docker image, that you install the app into the folder where Puppeteer is installed and switch back to the same non-root user.

Thanks I will try this and update soon. Apologies for the formatting, I believe markup may have reformatted my issue text.

waitForSelector is clearly a different issue and the most likely the element does not exist (for example, the  URL you test with is only available locally or if it is a third party website they block/render differently for your server script). Please double check that the content of the page that you expect is actually there.


Don't show Foxx documentation for services without controllers

When installing a Foxx util (e.g. users-local), the service page in aardvark shows

Info
Documentation for this service is not yet configured.

because there are no routes.
In this case it should simply show the README instead and not show the API docs at all.

The "swagger" service has a controller, but also shows this message.

Bug fixed. Readme is now rendered first if no documentation is available. Toggle button is disabled if no documentation is available.


How to create Meteor RESTful Authentication ?

Hello i want implement REST with username & password for user authentication.
I Have read this source https://github.com/534N/apitest. But i dont sucess with that.
Please help. Thanks

I suggest that always use token based authentication.
You need to provide an authenicate function: https://github.com/xcv58/meteor-collectionapi#custom-authenticate-function  this will send the token to you.
About how to get the token: you can provide web UI for this. Or you can implement a RESTful endpoint for this. The before function can help you to check whether it's correct user.

Thanks for your informations


Anomaly Content Retheme

Anomaly Incidents
Anomaly Structures
Anomaly Creatures

Obviously certain anomaly rewards will need looking at (serums, bioferrite, etc almost entirely useless at a tribal/medieval level, so will start a new issue for recipe ideas etc that could make the anomaly stuff a bit more useful)

First pass complete, entity codex, categories, and races complete, with the exception of placeholders for fleshbeast subtypes.
To-do:

Incident def labels
Building def labels (void monolith)

Removed from project, on branch, needs completely redoing to the extent it might as well be a seperate project


Feature/diagnostics

Diagnostics for frequency of the image publishers.

@reinzor, thank you for this!
I tested it and it looks very good.
There is one little change that need to be done. I will write it in the review summary.


GridSpec.tiles produces multiple tiles unexpected

Test code:
from odc.geo.gridspec import GridSpec
from odc.geo import BoundingBox
bb = BoundingBox(left=1200000.0, bottom=-3720000.0, right=1320000.0, top=-3600000.0, crs='EPSG:3577')
grid_spec = GridSpec(crs='EPSG:3577',
                     tile_shape=(4000, 4000),
                     resolution=30)
idx_bounds = grid_spec.idx_bounds(bb)
gbox = [gbox for _, gbox in grid_spec.tiles(bb)]

Outputs
idx_bounds

BoundingBox(left=10, bottom=-31, right=11, top=-30, crs=CRS('EPSG:3577'))

gbox

[GeoBox((4000, 4000), Affine(30.0, 0.0, 1200000.0,
        0.0, -30.0, -3600000.0), CRS('EPSG:3577')),
 GeoBox((4000, 4000), Affine(30.0, 0.0, 1320000.0,
        0.0, -30.0, -3600000.0), CRS('EPSG:3577')),
 GeoBox((4000, 4000), Affine(30.0, 0.0, 1200000.0,
        0.0, -30.0, -3480000.0), CRS('EPSG:3577')),
 GeoBox((4000, 4000), Affine(30.0, 0.0, 1320000.0,
        0.0, -30.0, -3480000.0), CRS('EPSG:3577'))]

Expected outputs
[GeoBox((4000, 4000), Affine(30.0, 0.0, 1200000.0,
        0.0, -30.0, -3600000.0), CRS('EPSG:3577'))]

The cause:
https://github.com/opendatacube/odc-geo/blob/b59a87cda71428b309682f5156b46ae9a11ef034/odc/geo/gridspec.py#L198-L201
The right and top boundary idx was forced +1 as shown above.
The question:
Is it a new convention that BoundingBox upper bound (bottom right) close instead of open now?

Good catch @emmaai, but the problem is not in that loop alone, this is tightly coupled to this code:
https://github.com/opendatacube/odc-geo/blob/b59a87cda71428b309682f5156b46ae9a11ef034/odc/geo/gridspec.py#L148-L163
Basically idx_bounds is under-defined. I think it should return open bound for bottom/right, and maybe not use BoundingBox but a tuple of slices.
Essentially this logic breaks down when supplied bounding box is covering tile exactly. In the code above we should really subtract epsilon from the right and bottom edges when locating bottom-right tile.
ix2, iy2 = self.pt2idx(x2 - eps, y2 - eps).xy

then return
return BoundingBox(ix1, iy1, ix2+1, iy2+1, None)

That bounding box should not really have CRS as it's not using CRS units at this point.
Relevant change:
https://github.com/opendatacube/odc-geo/commit/a96c2244a4e50829eb15a28a1518c022b949daad
Using BoundingBox as output of .idx_bounds() was a mistake, especially with close left/right, because how would you represent a single tile region?


[Doc] configure option configurl is not documented

Is your doc request related to a problem? Please describe or add related issue ID.
ISO installation support to inject remote Harvester config when installing, but there is no document for it.
Describe the solution you'd like
Update the doc and we should explicit it that it support only HTTP (current documented in ISO Installation) or both.

@harvesterhci-io-github-bot don't close my issue :crying_cat_face:


[choreo] [trajoptlib] Use more robust time estimates for intervals and initial dt decision variable

blocked by #820

I can't fully test this until tomorrow, but looks logically correct.

From my testing this has introduced a regression into the Differential generation (it can no longer generate a straight line path)

I think the kinematics for differential generator need to get looked at.

I think the kinematics for differential generator need to get looked at.

The differential generator is fundamentally broken, but this PR caused a regression on top of that


Add travis configuration

Todos:

[x] change humanconnection/webapp to humanconnection/nitro-web
[x] push first image manually

Can I suggest a differen approach? We want to build the docker image on Travis anyways. So how about running tests from within the docker container? If we deploy the image to production, the docker container should be authoritative for the success of the build.

Yeah sure, but what about image size?

Does a command run in the docker container affect the size of the image?? :astonished:

Not the command but don’t we have then reports and so on?

I fixed the linting... will see if its working now.

One thing: Does docker run [secure]/nitro-web yarn run lint exit with non-zero code (thus failing the build), if yarn run lint exits with non-zero code in the container? Did you try?


Scene Caching must recognise changes in attributes of objects

Currently, the Scene Caching Mechanism considers three hashes to check if a scene and its contents have changed:

hash corresponding to the arguments passed to scene.play (or scene.wait).
hash obtained with all the mobjects present in scene, including those not in the current play/wait call
hash obtained from camera_config.

However, using just these three hashes is not specific enough in some contexts.
Consider the following test scene:
class Test(Scene):
    def construct(self):
        T1 = TextMobject("M")
        self.play(Write(T1))

After the first render, if the T1 TextMobject is changed to some other letter, say Q, the scene caching mechanism will not recognise this change, and will still show the original animation of the letter M being written.
A possible solution to this would be to also hash the attributes of all the mobjects present in the Scene, or at least those mobjects being animated, and add that to the list of hashes used.
cc-ing @huguesdevimeux

Thanks for the report, and sorry for the answer delay !
The bug you described is super weird. In theory, scene-caching mechanism takes everything (see hashing.py, and more particularly CustomEncoder.default). So this :

A possible solution to this would be to also hash the attributes of all the mobjects present in the Scene,
is already done by manim.

I don't see rn where this comes, but I will take a look at that and try to fix it in a few days.

Thanks for the report, and sorry for the answer delay !
The bug you described is super weird. In theory, scene-caching mechanism takes everything (see hashing.py, and more particularly CustomEncoder.default). So this :

A possible solution to this would be to also hash the attributes of all the mobjects present in the Scene,
is already done by manim.

I don't see rn where this comes, but I will take a look at that and try to fix it in a few days.

I worked such a thing in already. I'm testing it rn :)

What do you mean ? What thing ?

Ok, so currently, the scene caching mechanism takes only the dict of the Animation that's being played/rendered, and does not consider the dict of the Mobjects in the animation.
I have added some code that makes the mechanism recursively get the dict of any objects in it that have a dict.
This way, it will also account for the Attributes of the Mobjects in the animation.

@huguesdevimeux Update:
So my changes fix this issue, but cause a RecursionError when testing with the script in #315
I believe this is because there are so many StreamLines in the AnimatedStreamLines that going through the dicts of each and every one of them occurs more than 1000 times.
Thoughts?

Ok, so currently, the scene caching mechanism takes only the dict of the Animation that's being played/rendered, and does not consider the dict of the Mobjects in the animation.

it does already if I understand correctly. See l.146 hashing.py.

I have added some code that makes the mechanism recursively get the dict of any objects in it that have a dict.

And it does already as well, as json.dumps is by essence recursive.

Ok, so currently, the scene caching mechanism takes only the dict of the Animation that's being played/rendered, and does not consider the dict of the Mobjects in the animation.

it does already if I understand correctly. See l.146 hashing.py.

I have added some code that makes the mechanism recursively get the dict of any objects in it that have a dict.

And it does already as well, as json.dumps is by essence recursive.

Nope. I believe it doesn't do that because of:
https://github.com/ManimCommunity/manim/blob/35e9e05eec4dc091d462ca2dab8b4561497ba0f1/manim/utils/hashing.py#L71-L75
Here, it basically ignores any key in dict if it has a string as its key.
In the __dict__ of the animation (which is obj), the Mobject being animated has the string key mobject, so it, and by extension, it's attributes, are ignored.

Here, it basically ignores any key in dict if it has a string as its key.

It does not ignore it. It let it as it is, and then it's hashed.
To check if the issue is related to that, could you check if the bug with TextMobjext is happening on master ?
I think this is related to the try expect thing, maybe.

It does not ignore it. It let it as it is, and then it's hashed.

To check if the issue is related to that, could you check if the bug with TextMobjext is happening on master ?
Yes, the issue with the TextMobject happens on Master too.

I'll push my changes to a new branch in about 2 mins.

@huguesdevimeux You can see my changes over here : https://github.com/Aathish04/manim/commit/bbf43fc1b35b965f4ebba15243aa90190efdbff1

@huguesdevimeux

It does not ignore it. It let it as it is, and then it's hashed.

Yea, the problem is that it doesn't hash the attributes of the value of mobject...
The hashing mechanism just saw that there was a TextMobject there, and assumed it was the same, and used the Cached file , not recognising that the actual attributes of the TextMobject changed.
The changes I made sort of fix that, but I can't get it to work on the AnimatedStreamLines example I sent, since it throws a recursion error, probably because there are too many StreamLine mobjects to check.

@huguesdevimeux Some Updates:
Commit https://github.com/Aathish04/manim/commit/b90218c835f0d188fcb1269c121aff132146e6e1 fixes the RecursionError, but the problem I mentioned in #302 (the second problem, where the same cached file is used even if the scene is changed),  still persists. At this point I think that it might be unrelated to this issue 🤔 .
Wierdly, if I add a keyword argument to the AnimatedStreamLines(), any keyword argument, the hash changes and it regenerates the cached video file, which means it is checking the attributes of the objects, but can't recognise a change in the four_swirls_function, for some reason...
Also, I was unable to reproduced this bug in the latest master with TextMobject, which was pretty wierd.


Not working with Parsed Text

Referencing issue from
https://github.com/fawaz-ahmed/react-native-read-more/issues/36#issuecomment-897476068

Sample code:
import React from 'react';
import {SafeAreaView, StyleSheet, View} from 'react-native';
import ReadMore from '@fawazahmed/react-native-read-more';
import ParsedText from 'react-native-parsed-text';

const App = () => {
  return (
    <SafeAreaView style={styles.safe}>
      <View style={styles.root}>
        <ReadMore numberOfLines={3}>
          <ParsedText
            parse={[
              {type: 'url', style: styles.url},
              {type: 'phone', style: styles.phone},
              {type: 'email', style: styles.email},
              {pattern: /Bob|David/, style: styles.name},
              {pattern: /42/, style: styles.magicNumber},
              {pattern: /#(\w+)/, style: styles.hashTag},
            ]}>
            Hello this is an example of the ParsedText, links like
            http://www.google.com or http://www.facebook.com are clickable and
            phone number<PHONE_NUMBER> can call too. But you can also do more
            with this package, for example Bob will change style and David too.
<EMAIL_ADDRESS>And the magic number is 42! #react #react-native
          </ParsedText>
        </ReadMore>
      </View>
    </SafeAreaView>
  );
};

const styles = StyleSheet.create({
  safe: {
    flex: 1,
  },
  root: {
    flex: 1,
    padding: 16,
  },
  textStyle: {
    fontSize: 14,
  },
  url: {
    color: 'red',
    textDecorationLine: 'underline',
  },
  email: {
    textDecorationLine: 'underline',
  },
  phone: {
    color: 'blue',
    textDecorationLine: 'underline',
  },
  name: {
    color: 'red',
  },
  magicNumber: {
    fontSize: 42,
    color: 'pink',
  },
  hashTag: {
    fontStyle: 'italic',
  },
});

export default App;

However, formatting goes away while collapsed:

This issue still exists

Yes, I can explain a bit. Incase you get a chance to fix.
See this method getTextByChildren in file
It re-constructs the paragraph in collapsed state. While doing so it clones the element and that's where it loses the component properties and becomes a regular text component.
If the component can be cloned with it's original state somehow, this issue can be resolved.

This issue is persistent :(


Support for LLAPI cores

Hi,
I would be very happy if we could change the LLAPI cores names to follow the standard core naming convention with an added #LLAPI. I download the LLAPI cores into the standard core directories and as it is now it gets messy with different names for the same cores.
Here are my proposed changes:
Gameboy_LLAPI:      Game Boy/Color #LLAPI
GBA_LLAPI:          Game Boy Advance #LLAPI
Genesis_LLAPI:      Mega Drive #LLAPI
MegaCD_LLAPI:       Mega-CD #LLAPI
NeoGeo_LLAPI:       Neo Geo MVS/AES #LLAPI
NES_LLAPI:          NES #LLAPI
SMS_LLAPI:          Master System #LLAPI
SNES_LLAPI:         Super NES #LLAPI
TurboGrafx16_LLAPI: PC Engine Duo #LLAPI
Pacman_LLAPI:       Namco - Pac-Man #LLAPI
Kind regards,
Carl

Hello @calle81, I am afraid your suggested changes are too long for the 18-Character names.txt-files. The names would start scrolling while the premise of the files here is to not have the names scroll. It is why they were shortened in the first place.
Instead please download and customize the names.txt of your choice to suite your specific needs.

Hello @calle81, I am afraid your suggested changes are too long for the 18-Character names.txt-files. The names would start scrolling while the premise of the files here is to not have the names scroll. It is why they were shortened in the first place.
Instead please download and customize the names.txt of your choice to suite your specific needs.


still doesn't cover removing the plugin from the outlook desktop application

I've been to the Myanalytics page, more than a week ago, and still this Insights button displays.  I can't find a com add-in to disable, and removing it via customizing the ribbon, doesn't remove it permanently, closing and re-opening outlook brings it right back up.  And yes on any given work day I have to close and re-open outlook 3 or 4 times to completely switch profiles I'm using.  (another long time complaint, where outlook use to allow you to have multiple profiles open in specific outlook window instances)

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

ID: 74c447e0-fae6-a016-c6bf-01438701ce17
Version Independent ID: b6d82917-aee4-2808-00ce-df6c20b75766
Content: Insights Outlook add-in - Workplace Intelligence
Content Source: WorkplaceAnalytics/MyAnalytics/Use/add-in.md
Product: mya
GitHub Login: @paul9955
Microsoft Alias: madehmer

Hi RCGms,
I looked into this and found an answer that I hope solves your problem. I added it to our documentation and you can find it here: Opt out of MyAnalytics / If you have multiple accounts.
Please let me know if this does not work for you.
Thank you,
-- paul9955, MyAnalytics documentation

@paul9955, thank you, but no, its the same type of instruction.  accessing your o365 instance and turning off the individual notifications or all notifications.
I did finally get it resolved today, however, because an email came in with a recognized "unsubscribe" option.  I say "recognized" because it triggered a web-add-in that would allow you to click an unsubscribe button that appears as a bar/closed menu section, just a little smaller height-wise than the close/comment buttons here on GitHub.... the section appears inbetween the preview pane's message header (top visible half of message preview pane) and the bottom/body of the message in the preview pane.
to the far right of this "unsubscribe" button was a "get more add-ins" or something, and clicking that took me to the web interface for adding/removing plugins to Outlook.  While looking around, there is a "My - Add ons" section, and looking there, were several different add-ons I would never choose, and surprise .. one for Insight, with it check-marked as installed.
I removed several of these default (defaulted to me) optional plug-ins and this removed the Insite icon from my outlook 2016 desktop app.
The same Web-add-in's web page is now reachable by the "Get Add-ins" ribbon bar button (looks like a 4-pane window box with the upper right pane replaced with a + symbol (hopefully this link comes through:  https://www.dropbox.com/s/nmgmxm8fjhjpybx/Screenshot 2020-05-06 01.14.11.png?dl=0   )
In times past, when I'd click that button there was no plug-in there, perhaps that's a change for Office/outlook recently.
 I wouldn't be so upset if it would allow both methods, simply removing from the Ribbon fails . and that's what sets this whole thing in motion.


crashlytics upload fails on occassion

New Issue Checklist

[X ] Updated fastlane to the latest version
[ X] I have read the Contribution Guidelines

Issue Description
Crashlytics upload fails on occassion. Need a retry flag.
Complete output when running fastlane, including the stack trace and command used
[11:00:12]: Uploading the build to Crashlytics Beta. Time for some ☕.
[11:01:11]: 2016-09-03 11:00:12.894 submit Crashlytics: Crashlytics.framework/submit 1.3.5 (17)
2016-09-03 11:00:29.468 submit Crashlytics: Added Release Notes Successfully 200
2016-09-03 11:00:29.879 submit Crashlytics: Added Testers/Groups Successfully 200
2016-09-03 11:01:11.722 submit Crashlytics: Unable to submit build. Response code: 0
2016-09-03 11:01:11.800 submit Crashlytics: Failed to upload binary

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Not reproducing the entire Fastfile to save time removing all the non-public info. But the following are the two relevant commands that worked dozens of times but once or twice a week fail during the upload phase.
Fastfile:
        gym(
            workspace: 'MyApp.xcworkspace',
            scheme: app['scheme'],
            output_directory: "archives",
            clean: false, use_legacy_build_api:true, include_bitcode:false
        )

        crashlytics(
            #notes: change_log
            notes_path: File.expand_path("beta-release-notes.txt"),
            groups: ['testers']
        )

Environment
fastlane version (run fastlane -v):
1.102.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? no
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? no

Hi @lakamsani Any chance you want to implement this in the crashlytics action? We'd love to see a PR 👍

sure. if someone has a pointer on where to start that might speed things up. In the meantime I will review the code and try to get started. is there any coding guidelines/PR notes for fastlane?

Hi @lakamsani Check out this page for some info on contributing https://github.com/fastlane/fastlane/blob/master/CONTRIBUTING.md. It should have most of the information you need! Thanks!

If it helps at all, a slight workaround I've been doing for the time being is something like this:
    tries = 3
    begin
      crashlytics(
        # Parameters go here
      )
    rescue Exception => e
      tries -= 1
      if tries > 0
        retry
      else
        raise e
      end
    end

However, it goes without saying a retry parameter for the Crashlytics action would be much nicer!  And I'm sure there's a neater version where retry has been implemented in other fastlane actions.

@simonrice Thanks so much for sharing!


Add loaders for Vault compatibility

Adding two loaders to support reading secrets from a path in a Vault. For now, supporting authentication via token (which is what all other auth backends map to) or app role.
I also included a few convenience methods in the token loader, to look up info about the token or renew it. The renewal method could be run periodically by a task or cronjob to keep a running service's token from expiring, in case the service is restarted / secrets need to be reloaded.
Would appreciate input on all of this -- I've been toying with Vault locally, but haven't worked with it in production.

Coverage decreased (-8.2%) to 81.081% when pulling 52e31d3b68ebd47c258014de8f6f150771fc8d9e on cranti:vault into 9ea2dff5949ca6bc7a59acb2f3d942894ab570cd on kensho-technologies:dev.

Coverage increased (+0.6%) to 89.899% when pulling 01ba721b46cc20adbc49723063286cd7a9956ac6 on cranti:vault into 9ea2dff5949ca6bc7a59acb2f3d942894ab570cd on kensho-technologies:dev.

Coverage increased (+0.9%) to 90.18% when pulling 3ed92f795c1a83c80487d3c6ea7c8efef0570217 on cranti:vault into 9ea2dff5949ca6bc7a59acb2f3d942894ab570cd on kensho-technologies:dev.


Picovoice Documentation Issue (/docs/koala/)

`import { KoalaWorker } from "@picovoice/koala-web";
import koalaParams from "${KOALA_PARAMS_BASE64_PATH}";
function processCallback(enhancedPcm: Int16Array) {
// do something with enhancedPcm
}
const koala = await KoalaWorker.create(
"${ACCESS_KEY}",
processCallback,
{
base64: koalaParams,
// or
publicPath: "${MODEL_RELATIVE_PATH}",
}
);
`
I try to using koala but where is MODEL_RELATIVE_PATH or KOALA_PARAMS_BASE64_PATH and Is there no callback func process? I just want to use koala with audio context. to using model turing voice recognize input from microphone (React)

Can you please reopen using the issue template, then I will be able to assist you.

Can you please reopen using the issue template, then I will be able to assist you.

Ok, thank you


is there any way to use custom icon in radial menu ?

since a lot of commands have no preset icon

Hello! Apologies for not answering your question early. I am currently updating the manual as well as the GitHub Issue section.
It seems like there isn't a way to add custom icons in radial menus. I will have to investigate this matter, however, if I manage to find answers on this matter I will let you know here or else update it on the manual!


PostgreSQL: Misconfigured 'Winter\Blog\Models\Post' featured_images relation?

Hi, i figured out a possible misconfiguration of the 'Winter\Blog\Models\Post' featured_images relation. Postgresql reports the following error:
STATEMENT:  select * from "system_files" where "system_files"."attachment_id" in (1) and "system_files"."attachment_type" = $1 and "field" = $2 order by "sort_order" asc

The IN part of the query fails cause of incompatible types (string / integer).
Adding a cast expression seems to fix this error:
'featured_images' => ['System\Models\File',
  'key' => 'CAST (attachment_id as integer)',
  'order' => 'sort_order'
],

I did not check, if this query works in mysql.

I made a quick test and I can commit the fix works on MySQL database.
I run into this error after migrating OctoberCMS to WinterCMS, it was interesting that on the OctoberCMS build 472 the generated statement worked fine without casting => Laravel 6.x?

@envas that's because of some changes made in Laravel 6+ where the keyType can be defined and the type of the attachment_id is technically a varchar (string) but Laravel thinks it's an integer. There was a fix for this in October 1.1.x, but I believe it was reverted because it caused some other issues. It will be fixed properly in Winter once https://github.com/wintercms/winter/pull/216 gets merged though.


adjust vue cli package instructions

I had to use @vue/cli to get vue to be recognised globally. If we do want @vue/cli-service-global perhaps reject this PR and add a note on adding the vue path to bash.

a complete vue project will be setup later.
the init package.json is just a quick demo.


frankenphp: init at 1.0.0-rc3

Description of changes
TBD
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@dunglas FYI ! Once this PR is merged, FrankenPHP will be available through Nix/NixOS !

Thank you @gaelreyrol ! Well done 👍

should we add multiple variations of frankenphp for each php major version?

should we add multiple variations of frankenphp for each php major version?

@shyim We could, it would ease its usage :slightly_smiling_face:

Hi!

Let us know if it's ok for you.

The benefit of having them directly in the nixpkgs would be that the build cache is there 😅

That's true.


Python extension can't show the list of poetry venv in a special situation

Type: Bug

Behaviour
Python extension can't show the list of poetry venv in a special situation
Steps to reproduce:

Create a new python venv and install dependencies with poetry

Add source mirror infomation to pyproject.toml like that

[[tool.poetry.source]]
name = "example"
url = "https://mirrors.example.com/web/simple"

Open this project with vscode

Select interpreter

The poetry venv of current project  exists, but python extension doesn't list it

Resolve it by adding priority = "explicit" (Ensure that no output is sent to stderr)

Perhaps, due to the warning messsages poetry outputs to stderr, python extension raises an error. But poetry still prints environment path as usual,why does python  extension raise an error for the stderr which contains not useful data?

Diagnostic data

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2024-04-10 17:48:23.216 [info] > poetry env list --full-path
2024-04-10 17:48:23.216 [info] cwd: .
2024-04-10 17:48:23.231 [info] Found: /bin/python --> /bin/python3.12
2024-04-10 17:48:23.232 [info] Found: /bin/python3 --> /bin/python3.12
2024-04-10 17:48:23.232 [info] Found: /bin/python3.12 --> /bin/python3.12
2024-04-10 17:48:23.260 [info] Found: /usr/bin/python --> /usr/bin/python3.12
2024-04-10 17:48:23.261 [info] Found: /usr/bin/python3 --> /usr/bin/python3.12
2024-04-10 17:48:23.261 [info] Found: /usr/bin/python3.12 --> /usr/bin/python3.12
2024-04-10 17:48:24.064 [error] [Error: Warning: In a future version of Poetry, PyPI will be disabled automatically if at least one custom source is configured with another priority than 'explicit'. In order to avoid a breaking change and make your pyproject.toml forward compatible, add PyPI explicitly via 'poetry source add pypi'. By the way, this has the advantage that you can set the priority of PyPI as with any other source.

	at /home/theresa/.vscode/extensions/ms-python.python-2024.4.0/out/client/extension.js:2:219366
	at ChildProcess.exithandler (node:child_process:415:7)
	at ChildProcess.emit (node:events:529:35)
	at maybeClose (node:internal/child_process:1098:16)
	at ChildProcess._handle.onexit (node:internal/child_process:303:5)]

Extension version: 2024.4.0
VS Code version: Code 1.88.0 (5c3e652f63e798a5ac2f31ffd0d863669328dc4c, 2024-04-03T13:25:57.039Z)
OS version: Linux x64 6.8.4-200.fc39.x86_64
Modes:

Python version (& distribution if applicable, e.g. Anaconda): 3.12.2
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

User Settings

languageServer: "Pylance"

Installed Extensions

Extension Name
Extension Id
Version

autoDocstring - Python Docstring Generator
njpwerner.autodocstring
0.6.1

autopep8
ms-python.autopep8
2024.0.0

C/C++
ms-vscode.cpptools
1.19.9

C/C++ Extension Pack
ms-vscode.cpptools-extension-pack
1.3.0

C/C++ Themes
ms-vscode.cpptools-themes
2.0.0

CMake
twxs.cmake
0.0.17

CMake Tools
ms-vscode.cmake-tools
1.17.17

Dev Containers
ms-vscode-remote.remote-containers
0.354.0

Doxygen Documentation Generator
cschlosser.doxdocgen
1.4.0

Even Better TOML
tamasfe.even-better-toml
0.19.2

Go
golang.go
0.41.2

Hex Editor
ms-vscode.hexeditor
1.9.14

IntelliCode
VisualStudioExptTeam.vscodeintellicode
1.3.1

IntelliCode API Usage Examples
VisualStudioExptTeam.intellicode-api-usage-examples
0.2.8

isort
ms-python.isort
2023.10.1

JavaScript Debugger
ms-vscode.js-debug
1.88.0

JavaScript Debugger Companion Extension
ms-vscode.js-debug-companion
1.1.2

Jupyter
ms-toolsai.jupyter
2024.3.0

Jupyter Cell Tags
ms-toolsai.vscode-jupyter-cell-tags
0.1.9

Jupyter Keymap
ms-toolsai.jupyter-keymap
1.1.2

Jupyter Notebook Renderers
ms-toolsai.jupyter-renderers
1.0.17

Jupyter Slide Show
ms-toolsai.vscode-jupyter-slideshow
0.1.6

Live Server
ritwickdey.LiveServer
5.7.9

Makefile Tools
ms-vscode.makefile-tools
0.9.10

Markdown Checkboxes
bierner.markdown-checkbox
0.4.0

One Dark Pro
zhuangtongfa.material-theme
3.17.0

Pylance
ms-python.vscode-pylance
2024.4.1

Python
ms-python.python
2024.4.0

Python Debugger
ms-python.debugpy
2024.4.0

Remote - SSH
ms-vscode-remote.remote-ssh
0.110.1

Remote - SSH: Editing Configuration Files
ms-vscode-remote.remote-ssh-edit
0.86.0

Remote - Tunnels
ms-vscode.remote-server
1.5.1

Remote Explorer
ms-vscode.remote-explorer
0.4.3

Table Visualizer for JavaScript Profiles
ms-vscode.vscode-js-profile-table
1.0.8

TODO Highlight
wayou.vscode-todo-highlight
1.0.5

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 2500)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
3, 2, 2

Memory (System)
23.22GB (16.10GB free)

Process Argv
. --crash-reporter-id 59b0364c-98e6-458c-a166-5140ecd75b2d

Screen Reader
no

VM
0%

DESKTOP_SESSION
plasma

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
g1icg217:30999571
0ee40948:31013168

The current detection code assumes that if something is written to stderr that there is an issue. We need to switch this to rely on the error code, and only use stderr to log.


UI - can't determine label from list

What steps did you take and what happened:
Trying to add a Column in Machine Inventory provides a list of labels that are not visible.
What did you expect to happen:
The list should be further left or expanded and the name should be completely visible - of when hovering, we should be able to determine the full label text.
Anything else you would like to add:

Environment:

Elemental release version (use cat /etc/os-release): Staging/Staging
Rancher version: 2.7.0
Kubernetes version (use kubectl version): 1.24.7 for local
Cloud provider or hardware configuration: bare-metal

PR here: https://github.com/rancher/dashboard/pull/8071

All good:


[Feature Request] Add option to see task submits

Description
Add option to see task submits.
Additional Info
No response

Added in 9ac2b9998d73b3d8c2ae2459287fd6ee130f0c51


Chức năng 1: Tìm chuyến đi

Tạo API

API:
Request Mapping: /buss-operation
/findBussPoint, Request Param: desc (String)
/findBuss, Request Param: departureTime (Long), endPoint (Long), startPoint (Long)


⚠ Jellyseerr has degraded performance

In b709901, Jellyseerr (https://jellyseerr.underthere.xyz) experienced degraded performance:

HTTP code: 502
Response time: 18482 ms

Resolved: Jellyseerr performance has improved in a750538 after 2 minutes.


xDhcpServerOption Router option

It seems that the Router option of  xDhcpServerOption must always be set? Is there any way to leave it unspecified? If I leave it unspecified I get the following error:
The variable cannot be validated because the value System.String[] is not a valid value for the Router variable.
    + CategoryInfo          : MetadataError: (:) [], CimException
    + FullyQualifiedErrorId : ValidateSetFailure
    + PSComputerName        : localhost

I second this

The Router property is set to Write in the schema, but has a [ValidateNotNullOrEmpty()] on it that generates that error message. It looks like if that is removed from the parameter the code could work without specifying Router parameter (line 133 could pose a problem).
https://github.com/PowerShell/xDhcpServer/blob/a748ae1965e5a757e4c8916822712b53465670cb/DSCResources/MSFT_xDhcpServerOption/MSFT_xDhcpServerOption.psm1#L97-L98

For the meantime, what is this option meant to control?  Can't find it in the documents

You are correct, it's missing there, that should be resolved too. If I'm not mistaken its used to set gateway addresses.

For those curious, the router option is a really oddly named setting which really corresponds to the default gateway for that DHCP Configuration.  Why isn't this just named 'Default Gateway'

For information. @1RedOne updated the documentation in PR #42, but the main issue still need to be resolved.

The resource xDhcpServerOption was deprecated when the resource DhcpScopeOptionValue was released.  The resource xDhcpServerOption will be removed in the next release.


[postgres] Easiest way to get N rows as a JSON array

I'm trying to figure out the simplest way to sample 100 rows from a table with an unknown schema as a JSON array (ideally serde_json::Value), here is what I'm currently using:
query(&format!(
    r#"
    SELECT JSON_AGG(t)::text "json!" AS rows
    FROM (SELECT * FROM {} TABLESAMPLE SYSTEM_ROWS(100)) t
    "#,
    &table_name
))
.map(|v: PgRow| v.get("rows"))
.fetch_one(&pool)
.await
.map(|v: String| serde_json::from_str(&v))

If you have the json feature of sqlx enabled, you can pull a serde_json::Value out directly using query_scalar, which was designed for use with single-column queries:
let json: serde_json::Value = sqlx::query_scalar(&format!(
        r#"
        -- you don't need to override nullability in a dynamic query like this, it's only for the macros
        SELECT JSON_AGG(t)
        FROM (SELECT * FROM {} TABLESAMPLE SYSTEM_ROWS(100)) t
        "#,
        &table_name
    )
    .fetch_one(&pool)
    .await?;

perfect thanks!


Fix jackson-databind dependency version (#39)

CLA signed.

Tested and merged, thanks for the contribution!


Protocol validation

[ ]   File: src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectProtocolValidator.cs:L178-488
 *does not match
 thanks
[ ]   File: src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectProtocolValidator.cs:L550-584
 no need of conditional checks (validationContext.State ?? "null") here because of the if right above this.
 I need to check if 'validationContext.ProtocolMessage' is null.
 I am referring to the checks in the log message: validationContext.State ?? "null", validationContext.ProtocolMessage.State ?? "null") as they wont be null at this point because of the if statement right above: if(string.IsNullOrEmpty(validationContext.State) || string.IsNullOrEmpty(validationContext.ProtocolMessage.State))
 Yes, I agree with removing the ??, I was just onto something else that caught my attention.
Thanks for noticing the issue.
 Got you. You were talking about not checking validationContext.ProtocolMessage == null at the top.
[ ]   File: src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectProtocolValidator.cs:L551-591
 We should validate the state when RequireState is false but ValidationContext.State and ValidationContext.Message.State exists. Similar to ValidateNonce. If state is sent is the request, it must be present in the response.
 agreed
[ ]   File: src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectProtocolValidator.cs:L551-591
 isNullorEmpty(validationContext.State) ?
[ ]   File: src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectProtocolValidator.cs:L551-591
 can remove the check for validationContext.State.

This pull request is now managed with CodeReviewHub. Refresh.

:shipit:


Implement reverse transposition using Perez-Driesse forward transposition

[x] Closes #1901
[x] I am familiar with the contributing guidelines
[x] Tests added
[x] Updates entries in docs/sphinx/source/reference for API changes.
[x] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

The function works, for anyone who wants to play with it already.  The discussion about suitable function names is now open!

@AdamRJensen Do you think we will have the final form of the paper reference in time for the December release?

@AdamRJensen Do you think we will have the final form of the paper reference in time for the December release?

I'm a bit puzzled that it is not out yet, but I expect it soon. At the very least we can add the doi: https://doi.org/10.1016/j.solener.2023.112093

So to wrap this up I would:

do a global change of "rtranspose" to "ghi_from_poa"
add the DOI to the references

Anything else needed?

Ready to merge?

I guess I'll wait a bit in case more reviews trickle.  It ain't over 'til it's over.

For the reverse transposition example it would be great to incorporate the GTI_DIRINT function, if anything, at least mention that pvlib offers two reverse transposition algorithms.

For the reverse transposition example it would be great to incorporate the GTI_DIRINT function, if anything, at least mention that pvlib offers two reverse transposition algorithms.

I put in a mention and a reference.

I guess I'll wait a bit in case more reviews trickle. It ain't over 'til it's over.

It's over!

@AdamRJensen Do you think we will have the final form of the paper reference in time for the December release?

I'm a bit puzzled that it is not out yet, but I expect it soon. At the very least we can add the doi: https://doi.org/10.1016/j.solener.2023.112093

In case anyone missed it, the link works now.

My plan is to send a thank-you note to NumFocus after this is merged.

A couple updates needed for the new function name but otherwise LGTM, thanks @adriesse!

My plan is to send a thank-you note to NumFocus after this is merged.

Lovely :) This PR is the last deliverable for the NF grant, right?

That's right, on time and on budget.  :)

Thanks @all!!


v3.0.0 to master

v3.0.0

#40

Breaking changes

Only Laravel v10 is supported.
Removed the src/Traits/ActingAsAuth0User.php trait. Use Auth0's new impersonate testing functionality instead.

Codecov Report
Patch coverage: 60.00% and project coverage change: -0.21 :warning:

Comparison is base (0d2cfd2) 94.73% compared to head (6e6e32c) 94.53%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##             master      #41      +/-   ##
============================================
- Coverage     94.73%   94.53%   -0.21%
+ Complexity      100       97       -3
============================================
  Files            17       16       -1
  Lines           380      366      -14
============================================
- Hits            360      346      -14
  Misses           20       20

Impacted Files
Coverage Δ

src/Logging/NewRelicLogger.php
54.83% <60.00%> (ø)

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

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


Network test case

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armnetwork - ci

/azp run go - armnetwork - ci


Focus not taken for "Load URL" field

Makes it hard to Command-L then enter URL.  Would be great if it requested Focus.
Also great if it remembered the last URL entered.

@silvermy Please see my comment here.
There was an attempt to fix this in #212.
Unfortunately, I don't think @JadenGeller wants to maintain this project.
I'd recommend you to switch to my for or to @alexzye's fork, they both have this issue fixed.

Viktor,
Thank you for the response.  I have looked at both your and Alex’s folrks.  I am not an OS X developer so any thing I generate from the sources will be unsigned (re: painful to use) - are there sanctions binaries from either your repo or Alex?
Cheers - Yossie

On May 15, 2017, at 1:24 PM, Viktor Oreshkin<EMAIL_ADDRESS>wrote:
@silvermy https://github.com/silvermy Please see my comment here https://github.com/JadenGeller/Helium/pull/212#issuecomment-299918530.
There was an attempt to fix this in #212 https://github.com/JadenGeller/Helium/pull/212.
Unfortunately, I don't think @JadenGeller https://github.com/jadengeller wants to maintain this project.
I'd recommend you to switch to my for or to @alexzye https://github.com/alexzye's fork, they both have this issue fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JadenGeller/Helium/issues/219#issuecomment-301593811, or mute the thread https://github.com/notifications/unsubscribe-auth/AIMkvPLnaoqZgSTBHKkWuJ0mm11LkGvmks5r6LR0gaJpZM4NZlMR.

I don't know about Alex's fork, but mine has releases section.
They're not signed at all, and I'll probably sign them with free developer license, since I don't have developer account.


Display note annotation "flag" in the editor

Display a "flag" in the editor for the location of annotations that contain project or consultant notes (or any other kind of annotation).

[ ] investigate how commenting works in the lexical playground. We may want to use @lexical/mark instead of creating our own node as outlined below.
[ ] create an annotation node based on an elementNode so that the beginning and end of the node is marked, i.e. an annotation is usually over a selection of text.
[ ] ~the particular "flag" icon type should be specified in the annotation.~
[ ] ~a map of "flag" icon types to icon files should be an input property.~
[ ] ~style the ::before psuedo-element of the node to display the specified "flag" icon if the icon type is defined.~
[ ] also allow highlighting of the annotation text (rather than or in addition to the flag icon).

This isssue is waiting on the outcome of discussions with the USFM/USX standards comnittee.


BPMSPL-295 - added support for json in wid configs - adjusted osgi co…

…nfiguration
This fixes the OSGi tests in droolsjbpm-integration.

+1 to merge


Allow configuring winhighlight for popups

It is already possible to configure borders, but it would be nice to be able to configure NormalFloat or winhighlight directly for popup windows as well:
https://github.com/nvim-neo-tree/neo-tree.nvim/blob/7c6903b05b13c5d4c3882c896a59e6101cb51ea7/lua/neo-tree/ui/popups.lua#L39
If someone gives me a green light, I can work on a pr for this

More control over highlight groups would be good. Should the highlight group be named FLOAT_NORMAL to be consistent with FLOAT_BORDER?

sounds like a good idea

not sure why this wasn't automatically merged by github


Writing canvas to GIF outputs double speed GIF

Not sure exactly how to explain, as it seems to be a somewhat randomized issue - I'm passing a canvas element to my JS via this (as a web worker), and most of the time it's able to output a GIF just fine. Sometimes though, it spits out a GIF that seems 2x or even 3x sped up from the original source canvas (as I am putting a video on the canvas element). I know this is probably a very strange and particular use case, just posting it here in case anyone else had come across this or there was a known fix for something like this.

Hi，I also encountered the same problem, how can I solve it?


Try to figure out what's wrong with the github workflows

[Short description explaining the high-level reason for the pull request]
Additions

Removals

Changes

Testing

Screenshots
Notes

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux

Problem was a stale cache item that caused two versions of numpy headers (Python 3.9 and 3.10 versions) to be found in the venv, which blew up CMake.


Complex Synthetic Feature Generation

Added a suite of functions related to synthetic feature generation and corresponding tests.
Located in outrank/algorithms/synthetic_data_generators
_https://jira.outbrain.com/browse/mm_generators_

HTML docs are yet to be written.

inspectionProfiles -> we don't need that. Please remove all files that are not relevant to the actual PR's content. Also, ccgen_tests.py and cc_generator.py seem same?

Removed .idea, cc_generator and cc_generator_tests are differet files, i've checked.

I'll continue review later. Some comments first.

Sorry for not replying earlier, had implemented the necessary changes with the changelog in my commit description, should have replied to the comments as well. Thank you for all the feedback.


Add variable: repository.escaped_windows_path

An repository.escaped_windows_path variable should be added that escapes the \ character.
Example: d:\\path\\to\\repo
repository.location should also get the same treatment as repository.path: It needs a repository.linux_location and repository.escaped_windows_location.

I know what you mean. But what about:

windows_path_with_ending_slash
windows_path_without_ending_slash
linux_path_with_ending_slash
linux_path_without_ending_slash
uppercase_path_..

etc.
My point its there are always other derivations of a property. Implementing such properties is in my opinion a tradeoff between usability vs cluttering.
At this point, I'm not convinced we should have such property. Especially because the string methods of Scriban can provide

That's a fair point. I'd suggest then deprecating windows_path and linux_path so that repository.path and repository.location are treated equally.
I doubt any Windows app needs linux_path so I'm guessing this is just leftover from RepoZ's MacOS implementation. And if it does, Scriban can be used.

True, but those are already in RepoM and removing them would mean a breaking change and at this moment, I'm not willing to do this.
Don't get me wrong,  you are making a valid point and it's likely to be removed in the future but just not now.
Although it looks like you know your way around the yaml action menu's here is a snippet for your request:
context:
- type: evaluate-script@1
  content: |-
    repository.escaped_windows_path = string.escape repository.windows_path;

action-menu:
- type: just-text@1
  name: '{{ repository.escaped_windows_path }}'
- type: just-text@1
  name: '{{ repository.windows_path }}'


Resume Download issue

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
When i want to download my resume, nothing is happening...
Expected Behavior
No response
Steps To Reproduce
click on pdf download on the footer or on the right side
What browsers are you seeing the problem on?
Chrome
What template are you using?
Pikachu
Anything else?
No response

The server has crashed due to over-use, it has maxed out all CPU, RAM availability so the Docker Stack was stuck in a restart loop.
Please give it a while for it to recoup. Unfortunately, there's nothing I can do to solve this except pour more money into the servers to get a bigger one.

Hi - AmruthPillai, the issue raised by tcastel94 seemed to specifically relate to the self-hosted version, rather than your hosted version. I can also report experiencing the same issue.
Unless pdf rendering is not handled by the self-hosted service and is actually being sent back to your centralised server? In which case that would seem to be against the ethos of self-hosting the package in the first place?


Review from F. Xavier Castellanos

This abstract provides a cogent report on a product. A few minor grammatical problems are noted below (suggested replacement text is underlined):
Intro: “Different tools has been developed to oppose these challenges…” should be “tools have been developed to confront these challenges”
The phrase “…but studies might have slight differences on analysis, that are not covered by such tools” is unclear.  I think the intent is:
“Diverse tools have been developed to confront these challenges, but their analytical results can differ. Addressing those differences is not facilitated by existing tools.”
Approach
“The goal of this Brainhack project was to build
3.1 “it is possible to search for an atlas region…”
Conclusion
“This is an initial version…”
“In our case study, NeuroView facilitates quick… and promotes discussion about them, since the results will inform researchers about their data.
“In future work, we aim to … and support some AFNI features, …” [delete ‘s after AFNI]

I fixed the text based on the Castellanos' points! It is now the HEAD of this repository.

@anibalsolon thanks for updateing.
@ccraddock I have confirmed these suggestions have been incorporated.  Please feel free to close.

Thank you, @nicholsn and @ccraddock !


CI fails sporadically

Today I merged a couple of documentation changes and the builds keep failing sporadically in different Node versions. See https://travis-ci.org/donejs/donejs/builds
@matthewp any ideas why? Looks like it just stops and times out.

Looking into it.

Made an improvement by upgrading the Firefox version in Travis. But let's keep open for now.

After #622 this seems to be solved. I created #623 as a follow-up issue for that.


Coercion of Literal with StrEnum and str is not consistent

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Even though we have 'a' == S.a, only 'a' is acceptable for Literal[S.a], not vice versa. I believe this inconsistency to be confusing. The problem seems related to literal validator. Should I open an issue in pydantic-core? 👀
Related to #9968, #9791, #9276
Example Code
class S(StrEnum):
    a = 'a'

class A(BaseModel):
    a: Literal[S.a]

class B(BaseModel):
    a: Literal['a']

assert 'a' == S.a
assert hash('a') == hash(S.a)

A(a='a')  # ✅
B(a=S.a)  # ❌

Python, Pydantic & OS Version
pydantic version: 2.9.0a1
        pydantic-core version: 2.20.1
          pydantic-core build: profile=release pgo=true
                 install path: D:\pydantic\pydantic
               python version: 3.12.1 (tags/v3.12.1:2305ca5, Dec  7 2023, 22:03:25) [MSC v.1937 64 bit (AMD64)]
                     platform: Windows-11-10.0.22631-SP0
             related packages: mypy-1.1.1 pydantic-extra-types-2.9.0 pydantic-settings-2.3.4 typing_extensions-4.12.2
                       commit: c53c5fb9

I'll note, I think this can be fixed by decoupling our Literal and Enum validators in pydantic-core.

^^ I'm guessing this will fall under the scope of v2.10


ctkRangeSlider customization

Note: I'm using latest 3D Slicer for testing the implementation of these changes.
cc: @sjh26 since you also mentioned dealing with customization of this widget
With master:
window_level = slicer.qMRMLWindowLevelWidget()
window_level.show()

Then upon applying a customization for the disabled color of Sliders, there is no observed change
stylesheet = "QSlider:disabled {selection-background-color: green;}"  # green for visibility of this example
slicer.app.setStyleSheet(stylesheet)

Now with this PR:
By default the slider appears in a (more correct) disabled state look
window_level = slicer.qMRMLWindowLevelWidget()
window_level.show()

Then upon applying a customization for the disabled color of Sliders, you can actually observe a change
stylesheet = "QSlider:disabled {selection-background-color: green;}"  # green for visibility of this example
slicer.app.setStyleSheet(stylesheet)

🍾


C29092: Possible typo box/toolbox

Hello, @mikejo5000,
Translator has reported possible source content issue.
"Linguist comment: "box" is unclear in this context. Could it be Toolbox?"
Please review and merge the suggested proposed file change to avoid this error. If you make related fix in another PR, then share your PR number, so we can confirm and close this PR.
Many thanks in advance.

@v-maudel : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

Thanks @gewarren , if this is not "toolbox", I will need a confirmation so the linguist can translate it accordingly.
Please, let me know if we can use computer instead.
@Mikejo5000

Computer or machine is good. I think computer is preferred.

Thanks @Mikejo5000  and @gewarren


"bulk" should not have changed "by default" to Quarantine

While I'm sure this change was well intentioned, its causing real problems for real businesses-- I had no idea my mail settings had changed and that this quarantine area even existed, have been using this Exchange 365 for 9+ years now.
I only found out after calling up the support line at Brex because I could not get any verification emails from them (literally all their emails were landing in this new quarantine area under the "Bulk" rule which is way too aggressive). Theres NO reason why bulk messages should have been by default changed to Quarantine instead of the Junk Mail folder-- thats the whole point of the Junk Mail folder! Not only did I find Brex's emails, but several newsletters and  verification emails from some other sites I tried to signup/login to were already in there.
I am assuming you guys only intended to 'by default' protect against actual malicious content (phishing, malware etc) but "spam" is not malicious- theres no reason to not let it go to the junk mail folders....
This is absolutely ridiculous guys- I doubt i'm the only one affected, many others probably don't even know (I mean I only found out two months later since it seems this change happened in November..)
Note: I'm posting this under the 'page' feedback because the 'product' feedback link at the bottom of the page is broken.

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

ID: 472b3a0c-7ad8-8245-9b57-29431490370b
Version Independent ID: 8671f04a-b7b3-402c-1e65-59a52c1cdaf5
Content: Secure by default in Office 365 - Office 365
Content Source: microsoft-365/security/office-365-security/secure-by-default.md
Product: m365-security
Technology: mdo
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@thavidu Thank you for your feedback. The product feedback link on the document will be fixed soon. In the meantime to make sure that your feedback gets routed to the appropriate team, please post it on the Microsoft 365 Q&A portal.
Thanks
Sri

Guys, what is the status of this.  Not only is my company domain affected by this, but I have mass clients with this as well.  I can understand actual bulk email "email with more than x recipients" being flagged as bulk.  However, this new algorithm now defaults "bulk" when a user sends a single email to another email.   a single email should never be flagged as "bulk".  Bulk should never be applied below 15 recipients.


Appstudio update test-component-pac-xkba

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-xkba-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
28 seconds
sast-snyk-check

✅ Succeeded
41 seconds
build-container

✅ Succeeded
8 seconds
inspect-image

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
7 seconds
deprecated-base-image-check

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/test-component-pac-xkba-on-pull-request has successfully validated your commit.


MSSQL:An existing connection was forcibly closed by the remote host.

Gitea version (or commit ref): 1.12.5
Git version: 2.29.2
Operating system: Win Server 2012 R2

Database (use [x]):

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

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

[ ] Yes (provide example URL)
[x] No

Log gist:

Description
Can not install with MSSQL 2008 R2, Error info: An existing connection was forcibly closed by the remote host.
Then i try check user sa access, it does not have problem.
I also try to trun on all mssql tcp/ip settings and create a new user, it does not work so.
At last, i try connect another ms sql server (2008 R2 too), not work.
Screenshots

I see a post said because the sql connect use encrypt so it not work, but i do not know how to try it, could you help me? Thanks!

This is wireshark screenshots.

You should set up SP1 of mssql server. see https://github.com/denisenkom/go-mssqldb#known-issues

You should set up SP1 of mssql server. see https://github.com/denisenkom/go-mssqldb#known-issues

@lunny  hi lunny, i have installed SQL SERVER 2008 SP2 Update, but when i try to intall, gitea may crash without no log, and i try to restart it again, but not work, could you give me some advice? Thanks!
C:\gitea>gitea.exe web
2021/01/12 16:42:10 cmd/web.go:108:runWeb() [I] Starting Gitea on PID: 33584
2021/01/12 16:42:10 ...dules/setting/git.go:91:newGit() [I] Git Version: 2.29.2,
 Wire Protocol Version 2 Enabled
2021/01/12 16:42:10 ...es/setting/markup.go:61:newMarkupSanitizer() [W] Skipping
 empty section: markup.sanitizer.1.
2021/01/12 16:42:10 routers/init.go:130:GlobalInit() [T] AppPath: C:/gitea/gitea
.exe
2021/01/12 16:42:10 routers/init.go:131:GlobalInit() [T] AppWorkPath: C:/gitea
2021/01/12 16:42:10 routers/init.go:132:GlobalInit() [T] Custom path: C:/gitea/c
ustom
2021/01/12 16:42:10 routers/init.go:133:GlobalInit() [T] Log path: C:/gitea/log

@lunny  hi lunny, i have installed SQL SERVER 2008 SP2 Update, but when i try to intall, gitea may crash without no log, and i try to restart it again, but not work, could you give me some advice? Thanks!
C:\gitea>gitea.exe web
2021/01/12 16:42:10 cmd/web.go:108:runWeb() [I] Starting Gitea on PID: 33584
2021/01/12 16:42:10 ...dules/setting/git.go:91:newGit() [I] Git Version: 2.29.2,
 Wire Protocol Version 2 Enabled
2021/01/12 16:42:10 ...es/setting/markup.go:61:newMarkupSanitizer() [W] Skipping
 empty section: markup.sanitizer.1.
2021/01/12 16:42:10 routers/init.go:130:GlobalInit() [T] AppPath: C:/gitea/gitea
.exe
2021/01/12 16:42:10 routers/init.go:131:GlobalInit() [T] AppWorkPath: C:/gitea
2021/01/12 16:42:10 routers/init.go:132:GlobalInit() [T] Custom path: C:/gitea/c
ustom
2021/01/12 16:42:10 routers/init.go:133:GlobalInit() [T] Log path: C:/gitea/log

I'm closing this issue as it has been awaiting further feedback for several months. @CHN-STUDENT please open another issue if you are still having problems.


bpfd: release-0.3.0

All the required changes needed to cut the bpfd  v0.3.0 release.
This includes some RELEASE.md fixes, updating cargo.toml's, adding a new examples deployment config, and updating the changelog.
Additionally it add's one for v0.2.1 which I must have forgotten to do last time.

This shouldn't change much I just have some things I want to address tomorrow before this merges 👍

I approved it so you don't have to wait on me, but it would be good if you could make the final change before you make it non-draft and merge it.