Dockerize heartbeat

I'm leaving this one as draft. I have moved the extractor heartbeat stuff to its own folder alongside backend and frontend, with the idea that it will run as a separate service.
This means that inside of that folder I am copying some of the code from backend. I have also added this in the docker-compose.dev.yml file, but so far it does not appear that it connects to rabbitmq from inside there. It does connect to rabbitmq when it is run outside of docker.
Could use some feedback on this.

@tcnichol @max-zilla I think we can move heartbeat_listener_sync.py to the main app folder and have a separate Dockerfile for it that only includes that file and required dependencies. This will avoid duplicating code and make sure that the dependencies are always in sync.

I did a little code cleanup and merged in main - @tcnichol please give it another try, it looks like it is creating exchange and listening to RMQ properly now, but I didn't test sending actual heartbeat.
Also agree with Luigi about not needing a separate folder with repeated models etc.

I'll move it back inside the app folder and then I will test.

I'm currently getting this error when I try to run the docker container:
  File "/code/./app/heartbeat_listener_sync.py", line 8, in <module>     from models.extractors import (   File "/code/app/models/extractors.py", line 4, in <module>     from app.models.mongomodel import MongoModel ModuleNotFoundError: No module named 'app'

I merged main into this branch since the extractor registration is now fixed on main.
I don't think I have permission to push the docker image though, but I also didn't know if I should push it until it's tested and we know it works. You can build a local docker image by doing
docker build -f heartbeat.Dockerfile -t  clowder/clowder2-heartbeat:latest  .

I fixed the runtime error. Added PYTHONPATH to the heartbeat.Dockerfile and now the imports are working.
There seem to be new build errors now, looks like when doing the pytest it can't connect to keycloak.


Calculater in C

hi @sherigar ,I want to add calculator in C language so please assign this issue to me with hacktoberfest label.
Thanks !

can u assign me this if it is a part of hactober fest

Can you please assign this issue to me.

Hello. Please can you assign this issue to me. I would like contributing to this issue.

Calculator.zip  i have changed


Add ScrollTo props to fixed grid elements in MultiGrid

Thanks for contributing to react-virtualized!
Here is a short checklist of additional things to keep in mind before submitting:

Please make sure your pull request description makes it very clear what you're trying to accomplish. If it's a bug fix, please also provide a failing test case (if possible). In either case, please add additional unit test coverage for your changes. :)
Run tests locally (npm test) to ensure that your change did not break linting or functionality.
Be sure you have notifications setup so that you'll see my code review responses. (I may ask you to make some adjustments before merging.)

Hi,  I'm using MultiGrid wrapped in an ArrowKeyStepper element (in 'cells' mode).  This is working well but currently only the bottom right grid receives scrollToColumn & scrollToRow props from the parent MultiGrid.  Therefore, if navigating with ArrowKeyStepper in the TopLeft/BottomLeft/TopRight grids they do not receive render events and it is not possible to manage focus.
I've run npm test against this and it's all good.  Thanks

Can you add a test (that fails without this change and passes with it)?

@bvaughn probably we shouldn't add features which will be removed or deprecated in major release?

@bvaughn, I've never written tests before but I can try.  As the grids in question don't have the scrollTo props at the moment I assume that creating a failing test should be easy enough.
@TrySound, based on your comments, should I be taking a different path here before I consider utilising this functionality in our project?  Is there a change pending that I may not be aware of?

@MarkBarbieri We gonna use props as default values and manipulate scroll with component methods.

OK.  if you'd prefer not to merge this then in the short term I can probably try and manage this issue via cellRangeRenderer or through forceUpdate() if scrollToColumn/scrollToRow indexes fall into the fixed columns/rows and force rendering and focus.
Sounds like this might be a good use case to test scrolling with component methods, so I'd be more than happy to help test it in this project when you have a working model.
Just to make sure we're on the same page, this is for tracking the row/column of the focused cell when MultiGrid is wrapped in an ArrowKeyStepper component.

I'm not sure why it was closed. Is this something that will be fixed in the upstream?


Will it update offest?

As the title.

You have to update them yourself

Where are they? i cant seem to find the offsets in the project?
might have overlooked them.

Updated.


ubnt:fw - Added rule and action extractions for UDM based logs

Forgot to bump the version in app.manifest


Should result validation be optional

Regarding the validation
As far as I can understand the validation function validateAndCoerceTypes() is called twice?

On the request - taking the query overrides, schemaKey and moduleName into account
On the response from Yahoo - taking the result from the response and schemaKey into account

Am I correct in saying that if the validation would fail it'd throw an error and cause the application to "fall over"? Ofcourse the
developer could handle the error and do something else, but I'm getting to the point below.
I'm not worried about the first case 1) On the request since that's something that's stable and in our domain. However, since > case 2) On the response from Yahoo is outside of our domain, I was thinking...
Would it make sense to let the developer using this library decide if they would like to turn on/off validation? The user story for > this would be:
As a developer
I want to know that node-yahoo-finance2 library will perform the requests I tell it to regardless of what response Yahoo gives us
So that I know that the app won't throw an error and fall over

Originally posted by @pudgereyem in https://github.com/gadicc/node-yahoo-finance2/issues/13#issuecomment-773482644

Well, it's all about your last line:

So that I know that the app won't throw an error and fall over

Say I have some typical code like:
function calculateStockHoldingValue(symbol) {
  const { qty } = await db.holdings.findOne({ symbol });
  const { price } = await yahooFinance.quoteSummary(symbol, { modules: "price" });

  return qty * price.regularMarketPrice;
}

Say qty = 50 and unexpectedly, price.regularMarketPrice is undefined.
const result = 50 * undefined; // NaN
In the best case scenario, this will crash my app somewhere else.  In the worst case scenario, the NaN will be used with other calculations, which will also be NaNs, which could then crash all other unrelated parts of my app.
Or with dates:
const { price: { regularMarketTime }} = await yahooFinance.quoteSummary('AAPL');

// Uncaught TypeError: Cannot read property 'getTime' of undefined
regularMarketTime.getTime();  //  "But it worked fine in development!!"

// Even worse is it IS defined, but is not a Date.  That *won't* throw an error in my code,
// instead, I'll be making a comparison that will be true when it should be false, etc.
const goodTimeToTrade = regularMarketTime > anotherDateObject;

Having said all that, if these options happen frequently, we could at least make all fields optional, and allow additional properties (at least then typescript won't allow you to use a property that could be undefined without a check).  My preference however is to have a bit more pain now and then have pain-free development and production ever after - but let's see what the next few days look like :)
Don't forget, the user can and should be catching these errors:
let result;
try {
  result = await yahooFinance.search('gold');
} catch(e) {
  // do nothing with invalid result
}
// Everything below here will be safe and won't throw unexpected errors
$('input').value(result.Result[0].name);

However, I will add a way for the user to still get access to the result and errors to figure out if they want to regardless, understanding of the risk, say: (not possible yet)
let result;
try {
  result = await yahooFinance.search('gold');
} catch(e) {
  // i'll take responsibility for this
  result = e.result; // maybe
}
// and will do my own validation
if (result && isArray(result.Result) && result.Result[0] && typeof result.Result[0].name === 'string')
  $('input').value(result.Result[0].name);

Hey @gadicc, thanks a lot for creating a separate issue for this and nice writeup.
I agree with you that strict schema validation is great since it would prevent errors as in the examples you provided above.  But I don't think I'm a big fan of having strict schema validation on the response from a third party that in theory could change / add to their response whenever.
Let me give you an example of where strict schema validation on the response is unwanted, in my humble opinion.
Example of where strict schema validation on the response is unwanted
Let's say that I want to get the stock symbol for a listed company, but I only have the company name at hand.

My code could look something like this:
import yahooFinance2 from "yahoo-finance2";
import { show } from "./utils";

const getSymbolForCompanyName = async (companyName: string) => {
  // 1. Search for the company name to retrieve the stock symbol
  let searchResult;
  try {
    searchResult = await yahooFinance2.search(companyName);
  } catch (e) {
    throw e;
  }

  // 2. Throw an error if the search didn't return any quotes
  if (searchResult === undefined || !searchResult.quotes.length) {
    throw new Error(`Could not find any quotes for the search`);
  }

  // 3. Filter out the quotes to only include "stocks"
  const onlyQuotesWithQuoteTypeEquity = searchResult.quotes.filter(
    (searchQuote) => {
      if ('quoteType' in searchQuote && searchQuote.quoteType === 'EQUITY') {
        return true;
      } else {
        return false;
      }
    },
  );

  // 4. Get the symbol (type guarded)
  let symbol;
  if (
    'quoteType' in onlyQuotesWithQuoteTypeEquity[0] &&
    'symbol' in onlyQuotesWithQuoteTypeEquity[0]
  ) {
    symbol = onlyQuotesWithQuoteTypeEquity[0].symbol;
  } else {
    throw new Error(`The quote we found din't have a symbol`);
  }

  return symbol;
};

show(async () => {
  // Please change the companyName below
  const companyName = "Apple";
  const symbol = await getSymbolForCompanyName(companyName);
  return `We searched for company name ${companyName} and found the symbol: ${symbol}`;
});

You can see and interact with the code in this CodeSandbox demo I created.
What could happen that's "out of our control" that would break this code when not necessary?
First, let's set the scene for this particular use case

The only request we make in this case to Yahoo is search
The response we get back from Yahoo we assume to be SearchResult and it's strictly validated with JSON schema here
We are only interested in looking at a particular subset of this response, namely SearchResult.quotes

So, let's ask ourselves; what could happen to the response from Yahoo that would case our validation to throw an error when in reality it wasn't needed?

If Yahoo decide to add an additional property to the response SearchResult
If Yahoo decide to change (or add) what they return in quotes[]
If Yahoo decide to change (or add) what they return in news[]

The first issue I believe can be avoided by setting additionalProperties  to true. This could be done for the other types, e.g SearchQuoteYahooEquity  as well.
However, the other two issues, where Yahoo could possibly decide to change (or add) to quotes or news are harder to account for. For example, they could possibly add another type of "News Object", which doesn't affect my code at all, but would still cause the request to throw an error.
Closing thoughts

I think "Strict schema validation" on the response is AWESOME to have in development, because this way we can keep the Types and the Schema up to date as time goes on.
However, I think that "Strict schema validation" is not something I'd like to have in PRODUCTION. I'd rather deal with the validation that is relevant to my "case", as I did above, see The quote we found din't have a symbol.
For some, strict schema validation might be great tho - which is why I think this should be something that you can opt in/out for

Eager to hear your thoughts on this @gadicc 💯

@gadicc also, here's my thoughts on your suggestion on what you said about allowing the developer to opt out of the validation.

However, I will add a way for the user to still get access to the result and errors to figure out if they want to regardless, understanding of the risk, say: (not possible yet)
let result;
try {
  result = await yahooFinance.search('gold');
} catch(e) {
  // i'll take responsibility for this
  result = e.result; // maybe
}
// and will do my own validation
if (result && isArray(result.Result) && result.Result[0] && typeof result.Result[0].name === 'string')
  $('input').value(result.Result[0].name);

At a first glance I don't like this approach, because in the developers opinion it's not an error. It's an active choice to don't validate the response. I'm not sure what the best way is, but one way would be to pass an argument to the request itself, pseudo code below.
// search for gold but don't validate the response
const result = await yahooFinance.search('gold', { validateResponse: false});
// and will do my own validation
if (result && isArray(result.Result) && result.Result[0] && typeof result.Result[0].name === 'string')
  $('input').value(result.Result[0].name);

Hey @pudgereyem
Thanks for writing all this up.  I'm up for making it possible to opt-out out of validation.  I don't believe on forcing anything on developers as long as the risks are clear.
Your proposal looks good, let me play around a bit and see what it looks like.

@gadicc awesome! Is there anything I could help out with? I had a quick look at https://github.com/gadicc/node-yahoo-finance2/issues/8 and I'm definitely up for adding another module.
I was thinking that my approach could be:

Create a new issue for a particular module, e.g recommendations by symbol
Write up a proposed solution
Get your thoughts
Create a PR

Thoughts?

Think we're good!  You can go check it out.
Just note from https://github.com/gadicc/node-yahoo-finance2/blob/devel/docs/validation.md that it's a moduleOption and not a qqueryOption, so:
const result = await yahooFinance.search('gold', {}, { validateResponse: false});

Is there anything I could help out with? I had a quick look at #8 and I'm definitely up for adding another module.

That would be amazing!!
You could probably just take a stab at the code and submit a PR...  it's pretty modular now with moduleExec.

@gadicc sweet! Will try it out later tonight and look into a new module as well! 💯

@pudgereyem thanks, let me know if you have any issues with it and i'll re-open.  And of course feel free to open issues on anything else.

@gadicc sweet! I spent the weekend offline mostly but will have a look now! Hope you had a nice weekend.

Yes, sure, no pressure at all from my side!  Just wanted to tidy up a bit :)
I aimed to spend the weekend offline but didn't have strong enough willpower to avoid working on a few more things :sweat_smile: But it's probably for the best as I'll have a lot less time to work on this this week.
Thanks!


Allow filtering by address state when fetching all addresses

Issue Number
#356
Overview
I have:

[x] Modified the listAddresses API server function to filter by the optional state query parameter.
[x] Added a parseOptionalArg function to module Cardano.CLI.
[x] Added an optional state filter argument to the cardano-wallet address list CLI command.

Comments

Rebased on latest master to resolve merge conflict.

Looks fine, though the sooner we get rid of docopt the better.

@rvl As soon as we are done with Jormungandr's integration, I think this one will be good to have in the pipeline.


Can not load a dataset from a Hugging Face repository

System Info
lerobot

Information

[X] One of the scripts in the examples/ folder of LeRobot
[ ] My own task or dataset (give details below)

Reproduction
can not load datasets from HF when doing: python lerobot/scripts/visualize_dataset.py     --repo-id lerobot/pusht     --episode-index 0, or python -u example/1_load_lerobot_dataset.py
error: dataset = LeRobotDataset(repo_id)
ConnectionError: Couldn't reach 'lerobot/pusht' on the Hub (ConnectionError)
Expected behavior
help me download the datasets from HF

Hi, thanks for reporting.
I'm unable to reproduce, are you using a proxy?
Also, can you try if this minimal code works?
from datasets import load_dataset
from lerobot.common.datasets import video_utils

dataset = load_dataset("lerobot/pusht", split="train", download_mode='force_redownload')

Hi, thanks for reporting. I'm unable to reproduce, are you using a proxy?
Also, can you try if this minimal code works?
from datasets import load_dataset
from lerobot.common.datasets import video_utils

dataset = load_dataset("lerobot/pusht", split="train", download_mode='force_redownload')

Thank you for your reply. Yes I am using a proxy, i get the List of available datasets ... but get the ConnectionError: Couldn't reach 'lerobot/pusht' on the Hub (ConnectTimeout). Also the minimal code doesn't work , same connection error.

Hi, thanks for reporting. I'm unable to reproduce, are you using a proxy?
Also, can you try if this minimal code works?
from datasets import load_dataset
from lerobot.common.datasets import video_utils

dataset = load_dataset("lerobot/pusht", split="train", download_mode='force_redownload')

What should I modify to reproduce if I manually download the PushT dataset from HF URL?

Okay, maybe try that (fill in you actual proxies first):
from datasets import DownloadConfig, load_dataset
from lerobot.common.datasets import video_utils

download_config = DownloadConfig(proxies={"https": "<your proxies>"}, force_download=True)
dataset = load_dataset("lerobot/pusht", split="train", download_config=download_config)

Okay, maybe try that (fill in your actual proxies first):
from datasets import DownloadConfig, load_dataset
from lerobot.common.datasets import video_utils

download_config = DownloadConfig(proxies={"https": "<your proxies>"}, force_download=True)
dataset = load_dataset("lerobot/pusht", split="train", download_config=download_config)

Thanks god, I finally make it work by using hf-mirror. Thank you very much for your reply!

Awesome!

Okay, maybe try that (fill in your actual proxies first):
from datasets import DownloadConfig, load_dataset
from lerobot.common.datasets import video_utils

download_config = DownloadConfig(proxies={"https": "<your proxies>"}, force_download=True)
dataset = load_dataset("lerobot/pusht", split="train", download_config=download_config)

Thanks god, I finally make it work by using hf-mirror. Thank you very much for your reply!

hi please can you share how to change the code .


negative test : Attaching and Detaching of Volume with replica deletion

negative test : Attaching and Detaching of Volume with replica deletion
Item number 6 from https://confluence.suse.com/display/LON/Negative+Testing
Steps to run tests :

enter into directory e2e
run command : ./run.sh -s ./tests/attach_detach_volume_with_replica_deletion.robot

Results :
./run.sh -s ./tests/attach_detach_volume_with_replica_deletion.robot
==============================================================================
Attach Detach Volume With Replica Deletion :: Negative Test Cases
==============================================================================
Write Volume And Attach and DeAttach Volume With Replica Deletion     | PASS |
------------------------------------------------------------------------------
Attach Detach Volume With Replica Deletion :: Negative Test Cases     | PASS |
1 test, 1 passed, 0 failed

For local setup use below settings.ini file :
[DEFAULT]
RETRY_INTERVAL = 5
SSH_CONFIG_PATH = ~/.ssh/config
CLOUD_PROVIDER = local
K8S_DISTRO = rke2
LONGHORN_CLIENT_URL = http://<IP_ADDRESS>:7000/
KUBECONFIG_PATH = ~/.kube/local

@nitendra-suse I'm planning to remove the config, cloud_provider and aws related code. So if you're struggling to understand/deal with these code, just feel free to modify and have your temporary solution. I'll refine this and have a more clear picture of how it should work.

@nitendra-suse suggests moving to draft and restart this when the ground work is ready by @yangchiu . Please follow up on the status with @yangchiu .

@yangchiu @nitendra-suse do we still need this? Probably @nitendra-suse need to reupdate this based on the current implementation.
cc @khushboo-rancher


Don't split tuples the same way as maps, lists, and friends

Right now tuples are formatted multiline when they don't fit:
{
  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
  bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb,
  ccccccccccccccccccccccccccccccccccccc,
}

Personally I never use this convention nor have I seen it in any code that I can recall. However, I am not sure how to proceed here. Thoughts @josevalim @lexmag?

For now multi-line only for key-value data structures.

@uohzxela this should be a easy one to tackle. :)

@whatyouhide I think we are still using multiline tuples in some cases if i'm not wrong, like the example you gave recently in a PR: https://github.com/uohzxela/ex_format/pull/67#discussion_r132835054 and also issue: https://github.com/uohzxela/ex_format/issues/48 :P

@uohzxela those are not considered tuples but tuple calls. I'm talking about tuple literals.

@whatyouhide since we already implemented multi-line tuple literals, why not we keep them as we are using them as an abstraction for multi-line tuple calls? Also, if some user unwittingly has a very very long tuple, it can get split into multiple lines however unusual it may be. But if you really want to eliminate multi-line tuple literals, I can rewrite the code accordingly. :)

We just never write multiline tuples in real-world Elixir code, so yes let's rewrite to make tuples not go multi-line (except for tuple calls). 👍

No problem @whatyouhide, I'll create an issue for this.

Reopened because of this example I found in Elixir source:
:ets.insert(table, {
  doc_tuple,
  line,
  kind,
  merge_signatures(current_sign, signature, 1),
  if(is_nil(doc), do: current_doc, else: doc)
})

Right now this is formatted as a very long single-line tuple. In light of this example, should we bring back splitting for tuples? @whatyouhide

IMO, we should highlight it as:
:ets.insert(table, {doc_tuple, line, kind,
                    merge_signatures(current_sign, signature, 1),
                    if(is_nil(doc), do: current_doc, else: doc)})

if someone doesn't like it much, then you can just put the other expressions in variables and then it should concisely fit a single line. The rationale for this choice is because the one per line looks really verbose when they are all variables:
:ets.insert(table, {
  doc_tuple,
  line,
  kind,
  signature,
  doc
})

And using only variables is arguably the most readable code, so I would rather make the most readable code look tidy than trying to make non-readable code pretty.
@lpil, am I also correct to say that, if we were using inspect algebra, our options would be between:
:ets.insert(table,
            {doc_tuple, line, kind,
             merge_signatures(current_sign, signature, 1),
             if(is_nil(doc), do: current_doc, else: doc)})

and
:ets.insert(table,
            {
              doc_tuple,
              line,
              kind,
              merge_signatures(current_sign, signature, 1),
              if(is_nil(doc), do: current_doc, else: doc)
            })

?

I like
:ets.insert(table,
            {doc_tuple, line, kind,
             merge_signatures(current_sign, signature, 1),
             if(is_nil(doc), do: current_doc, else: doc)})

the most.
More than :ets.insert(table, {doc_tuple, line, kind, variant (my second favourite) because it makes less empty space on the left side, and subjectively makes mental parsing of that huge second argument easier. :bowtie:

I believe that any of the above could be implemented with algebra, just varying levels of fiddy-ness :)

Sounds like using Inspect.Algebra is the way to go for very long tuples, thanks all for the discussion!


excel-report-template select by user id

Code is not commited. What is excel file change for?

my mistake I was committing the wrong file

Another thing:  "templates/export/" + "/summary.xlsx");


Grammar and place holder corrections, review the outline model.

Description
Describe the changes that were made in this pull request. When possible start with the motivations behind the change. Be sure to also include the following information:

Motivation for change?
What was changed?
Link to relevant issues?

Checklist

[ ] Conventional commits were used
[ ] New links to files and images were verified
[ ] For fixes/refactors: all existing references were identified and replaced
[ ] Style guide was reviewed and applied
[ ] Clear code samples were provided
[ ] People were tagged for review

closing and moving to https://github.com/hirosystems/docs/pull/552


Can't select multiple notebook cells at once

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
It seems like I cannot select more than one notebook cell, either by clicking on the left padding/gutter next to the cell or by trying to select text in multiple cells with my mouse. In Jupyter Classic (and I think Lab) you can hold shift and select multiple cells with the left padding/gutter and then use actions like cut/paste/move up/move down on the group.
Repro:
Open any notebook with multiple cells, and click on the left padding next to the cell. While holding shift, try and select more cells.
VS Code Version
Version: 1.70.0 (user setup) Commit: da76f93349a72022ca4670c1b84860304616aaa2 Date: 2022-08-04T04:38:16.462Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.22000
Jupyter Extension Version
v2022.7.1002181843
Jupyter logs
No response
Coding Language and Runtime Version
Python 3.7.12
Language Extension Version (if applicable)
v2022.12.0
Anaconda Version (if applicable)
conda 4.13.0
Running Jupyter locally or remotely?
Local

shift+click should work to select multiple cells. What happens when you do that?

shift+click should work to select multiple cells. What happens when you do that?

Ohhhhhhhhhhh I just realized what was happening. The selection works, but the UI only shows the selection frame around the last one clicked. There is no indication that other cells were still selected 🤦♀ So probably not a bug, but UI feedback 👍


As a user, I want to view the apps so that i can view a list and select the app i wish to see

Expected behavior
http://server-ip:port/pixieapps should let me review and use the apps
Actual behaviour
Takes me to a sign in page and asks for User Id and password.

The default userid is admin and default password is "" (blank). You can change these values via standard jupyter settings if running locally or through deployment.yaml if running on a kubernetes cluster.
Bear in mind that the pixieapps page is part of the pixiegateway admin console and therefore must be protected. If you are looking for a user facing page that list all the deployed pixieapps, then you can always create it yourself and associate it with the url of your choice via standard tornado mechanism.

Thank you for the reply. I was able to access the pixieapps. Another issue I faced once I was here was that delete didn't seem to work. Any pointers @DTAIEB


Staff Page - When create staff it shows phone number already exist

Describe the bug

When there is phone number with diffrent country code then also it shows phone number already exist

https://www.berrycast.com/conversations/8a6450c7-002f-572a-bec5-2a8b3ca14516

Yes, Currently we donot check for Country Code, as Some of clients data is not correct
later on we will correct this
Currently only phone number matching is ON


Disallow bypass when vpn is lockdown

Allowing network bypass on a vpn that's running in lockdown mode
causes it to lose internet connectivity. Prevent the vpn from entering
such a state at least on vpn-start / vpn-restart.

A slightly better implementation would check for vpn lockdown on every network_change event, and restart the vpn to disallow / allowBypass accordingly. Android doesn't broadcast change in vpn's lockdown mode, and so even checking on every network_change event doesn't cover all cases either. In RethinkDNS (an intra fork), we check for vpn lockdown mode changes on every new tcp/udp conn  (wasteful, but... :shrug:).
https://github.com/celzero/rethink-app/blob/46f08da505e234c098626208682f2b12dce21920/app/src/main/java/com/celzero/bravedns/service/BraveVPNService.kt#L1103
Prior art: https://github.com/Jigsaw-Code/Intra/pull/24#discussion_r597377493
Ref: https://github.com/celzero/rethink-app/issues/92

gh pr checkout 420

https://github.com/celzero/rethink-app/blob/46f08da505e234c098626208682f2b12dce21920/app/src/main/java/com/celzero/bravedns/service/BraveVPNService.kt#L1103-L1117

https://github.com/celzero/rethink-app/blob/46f08da505e234c098626208682f2b12dce21920/app/src/main/java/com/celzero/bravedns/service/BraveVPNService.kt#L1103-L1117

https://github.com/celzero/rethink-app/blob/46f08da505e234c098626208682f2b12dce21920/app/src/main/java/com/celzero/bravedns/service/BraveVPNService.kt#L1103-L1117

https://github.com/celzero/rethink-app/blob/46f08da505e234c098626208682f2b12dce21920/app/src/main/java/com/celzero/bravedns/service/BraveVPNService.kt#L1103-L1117

https://github.com/Jigsaw-Code/Intra/pull/24#discussion_r597377493


Fixes #1915 to make http_no_cache services support origin ports

Change how the Origin FQDN is parsed so it will properly split out the origin port if present.'
This should fix #1915

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1192/
Test PASSed.


feat: update command-line options processing

PR summary
This commit updates the CLI processing funtion
within the valiator, along with associated tests.
Specifically, the "debug" and "print-validators"
options were removed.
Signed-off-by: Phil Adams<EMAIL_ADDRESS>PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[x] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

:tada: This PR is included in version 0.0.2-rc.1 :tada:
The release is available on npm package (@v1-rc dist-tag)
Your semantic-release bot :package::rocket:


about Audio2Mouth model using own datasets

now i want to train Audio2Lip. i just use the APC_encoder model to extract the audio features.Then I make a set of audio vectors corresponding to a frame of lip images by slicing the audio feature vectors in order. However, I found that there are no consecutive sets of audio vectors to predict a frame of lips image. Will this not be able to play the role of LSTM? The model I use is Audio2Mouth, but I changed 253 to 363 according to the actual situation. But the prediction effect is not ideal. And with muted audio, the lips
doesn't close.Can you tell me how long it takes to train a character, and how long can it be effective? thank you very much.
I used Chinese audio to predict the corresponding lips video
https://user-images.githubusercontent.com/41277638/156123996-e0e92826-de13-46b4-ba86-c729f46d8e42.mp4

Sorry, I don't understand what are you talking about. Please describe your problem clearly.
The proposed method is a person-specific model, and you need to train all models except the audio feature extraction model on novel persons. In my experiments, 5 minutes length video is enough to achieve a good result.
If you want your generated lips closed when inputting muted audio, first check whether your training videos contain such cases.


Prepare for release v32

This PR is in preparation for the release of v32.0.0.

@wesleimp , @z0mbix , @andrew-waters - you are all welcome to review this one as well.  Thank you!

Thank you, @z0mbix!


[editor] add telemetry for more events

[editor] add telemetry for more events
As discussed offline, we want to enable telemetry in the local editor for the following events:

RUN_PROMPT_START
RUN_PROMPT_CANCEL
RUN_PROMPT_ERROR
RUN_PROMPT_SUCCESS

This diff implements the logging telemetry for those events.

Add mode "local" to all telemetry sent from local editor in prod mode
Send telemetry log events after dispatching rather than before, so that the client render action gets called first.

This technically shouldn't matter since these are all async calls.

Note: This only implements logging for Local Editor. Next up is to add the datadog initialization to Gradio Workbook

Testplan

yarn build -> run editor in 'prod' mode
run prompt, cancel, rerun to success. Check telemetry sent to datadog.

https://github.com/lastmile-ai/aiconfig/assets/141073967/52043456-3682-4dd7-b95b-846ad7480019

added model to Run events. It wasn't straight forward to find the model so did some logic using stateaiconfig -> getPrompt -> getModelName
rebase


feat(system_error_monitor): delete system error monitor

Description

remove system error monitor from launch and config
Related links

autoware universe PR
Tests performed

Comfirmed no problem in launching Psim or Lsim.
Notes for reviewers

Interface changes

ROS Topic Changes

ROS Parameter Changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.
[x] The PR has been properly tested.
[x] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Should there be any announcements done in GitHub Discussions and explain about how it was replaced with diagnostic_graph_aggregator?

@mitsudome-r
There is its discussion!


darktable: 4.8.1 -> 5.0.0

Things done
Changelog: https://github.com/darktable-org/darktable/releases/tag/release-5.0.0
cc @flosse @mrVanDalo @paperdigits @freyacodes

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] 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

[x] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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.

Add a :+1: reaction to pull requests you find important.

When updating from the stable 4.8 series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 4.8.
You are strongly advised to take a backup first.

This may be concerning. What about 5.x be darktable_5 for some time?

This should not be concerning, this is the case on every major version upgrade.
Make a backup of your sqlite dbs before upgrade.
On December 22, 2024 5:59:27 AM PST, Lucas Eduardo @.***> wrote:

When updating from the stable 4.8 series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 4.8.
You are strongly advised to take a backup first.

This may be concerning. What about 5.x be darktable_5 for some time?
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/367238#issuecomment-2558465932
You are receiving this because you were mentioned.
Message ID: @.***>

The database schema gets updated each version and is generally backward incompatible. The project does not test backward compatibility.
You can argue with the general approach all you want, but its been like this for a long time. If you'd like to do the dev work and testing needed to change the behavior that'd be great.
On December 22, 2024 10:01:40 AM PST, "Gaétan Lepage" @.***> wrote:

This should not be concerning, this is the case on every major version upgrade.

I don't know darktable very well, but I would argue with this general approach.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/367238#issuecomment-2558539452
You are receiving this because you were mentioned.
Message ID: @.***>

Gotcha, I def read your message incorrectly, sorry.
On December 22, 2024 11:51:42 AM PST, "Gaétan Lepage" @.***> wrote:

The database schema gets updated each version and is generally backward incompatible. The project does not test backward compatibility. You can argue with the general approach all you want, but its been like this for a long time. If you'd like to do the dev work and testing needed to change the behavior that'd be great.

I am not sure to get what you mean, but in my original, I meant that I agree with you. I don't feel like we should duplicate versions of packages in nixpkgs as soon as a major / breaking-changes release happens.
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/367238#issuecomment-2558576211
You are receiving this because you were mentioned.
Message ID: @.***>

@NixOS/nixpkgs-merge-bot merge

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 367238

x86_64-linux

:white_check_mark: 2 packages built:

darktable
photoprism

The updateScript doesn't eval which then breaks the updateScript fetcher for the nixpkgs-update bot.
$ nix-shell maintainers/scripts/update.nix --argstr package darktable
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:34:12:
           33|
           34|   strict = derivationStrict drvAttrs;
             |            ^
           35|

       … while evaluating derivation 'nixpkgs-update-script'
         whose name attribute is located at /home/zowoq/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:375:7

       … while evaluating attribute 'shellHook' of derivation 'nixpkgs-update-script'
         at /home/zowoq/nixpkgs/maintainers/scripts/update.nix:261:3:
          260|   '';
          261|   shellHook = ''
             |   ^
          262|     unset shellHook # do not contaminate nested shells

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: function 'anonymous lambda' called with unexpected argument 'rev-prefix'
       at /home/zowoq/nixpkgs/pkgs/by-name/ni/nix-update/nix-update-script.nix:6:1:
            5|
            6| {
             | ^
            7|   attrPath ? null,

Ill try to fix it

Fixed, and also there is a new version so the fix is tested.
https://github.com/NixOS/nixpkgs/pull/367780
Em seg., 23 de dez. de 2024 às 23:06, Lucas Eduardo <
@.***> escreveu:

The updateScript doesn't eval which then breaks the updateScript fetcher
for the nixpkgs-update bot.
$ nix-shell maintainers/scripts/update.nix --argstr package darktable
error:
… while calling the 'derivationStrict' builtin
at <nix/derivation-internal.nix>:34:12:
33|
34|   strict = derivationStrict drvAttrs;
|            ^
35|
   … while evaluating derivation 'nixpkgs-update-script'
     whose name attribute is located at /home/zowoq/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:375:7

   … while evaluating attribute 'shellHook' of derivation 'nixpkgs-update-script'
     at /home/zowoq/nixpkgs/maintainers/scripts/update.nix:261:3:
      260|   '';
      261|   shellHook = ''
         |   ^
      262|     unset shellHook # do not contaminate nested shells

   (stack trace truncated; use '--show-trace' to show the full, detailed trace)

   error: function 'anonymous lambda' called with unexpected argument 'rev-prefix'
   at /home/zowoq/nixpkgs/pkgs/by-name/ni/nix-update/nix-update-script.nix:6:1:
        5|
        6| {
         | ^
        7|   attrPath ? null,

Ill try to fix it
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/367238#issuecomment-2560537824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADXXO6AT4U5HQ3GTUEG5A732HC6RRAVCNFSM6AAAAABUBBXGBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGUZTOOBSGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The updater script still fails to eval. Proposed the fix as:

https://github.com/NixOS/nixpkgs/pull/367950

I still tries hard to pull in 5.1.0 (just like nix-update), but at least it does not deserve the package.nix file when it fails.

A working nix update script can be found here:  https://github.com/NixOS/nixpkgs/pull/368007


Move metadata configuration to exporter windows

metadata configuration is its own window now.  We should move it to each of the emit panes so that we can have customized definitions (sql especially) per emitter pane.

Completed for jdbc.  Separate tix per other emitters


scanpy fails in conda env with python 3.9.4

[x] I have checked that this issue has not already been reported.
[x] I have confirmed this bug exists on the latest version of scanpy.
[ ] (optional) I have confirmed this bug exists on the master branch of scanpy.

Apologies if this is issue is already know but I couldn't find it and the doc advertises python 3.6 so I figured I would report it.

Minimal code sample (that we can copy&paste without having any data)
After following Anaconda installation instructions in a brand new conda env created with python 3.9.4:
import scanpy as sc

returns:
Illegal instruction (core dumped)

Another brand new env with 3.7 imports scanpy successfully.
Versions
scanpy 1.7.2

Closing as:

The original issue looks like a numba related problem, which I believe didn't work with python 3.9 at the time.
We're past the 1.7 release series and aren't supporting it anymore

Please re-open this; currently receiving this error with Python 3.9.7 and scanpy 1.8.2. Just in case it's useful, CPU flags including instruction sets are pasted below.
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd ibpb vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

@pranzatelli, could you open a new issue for this? In that issue, could you also report what versions of the dependencies you're using via sc.logging.print_versions()?


Gray out nodes without scripts in the Connect Signal window

It would be a nice QOL improvement, particularly for beginners if all the nodes in Connect Signal dialog window were grayed out, so as to more clearly see which nodes make any sense to select. Currently, if the user selects a node that doesn't possess a script, then an error window appears to say that this was a poor choice. Instead, those nodes shouldn't be selectable in the Connect Signal dialog.

You can connect to functions that are part of the node and not part of the script, so a node doesn't need to have a script for connecting signals to it. In 3.1 alpha 3 (I don't know if it's in the stable version too), the menu will hide the "Make Function" button when you select a node without a script. So at least it's clear that you can't create a new function on the node. But maybe there could be some autocomplete or something so you know what functions are available in the node.

See also #15339 and #24316.

Added in 3.2


Problem with css loader?

I started with an Office Fabric template that uses TypeScript and React and Just. When I tried to add an "import" statement for a .css file into the App.tsx file, I got a compiler error that said I needed a loader. I ended up having to put the following code into my webpack.config.js in order to get it to work. But I'm hoping there is something I did wrong or some simpler setting I can change to get the same effect.
module.exports.module.rules.push(     {         test: /\.css$/,         use: ['style-loader', 'css-loader'],     } );
module.exports.resolve.extensions.push('.css');

The intention is to not force a css style loader by default, but it seems that this is a hindrance to people using this template. I'll add this on by default (css-loader / style-loader)

Thanks! That seems like a great plan!

Thanks so much! Wonderful!

I have almost the same situation. Started with Office Fabric React. Tried to add .scss file and got stuck for half of a day.
Since documentation is almost non-existent and error log for the most part does not provide clear leads I almost give up and was ready to switch to create-app.
Plus, Office Fabric React uses<EMAIL_ADDRESS>and there is that bug with localIdentName (#236). Upon updating to @latest npm run start stopped watching.
I'm sorry for this rant, but it is super frustrating to use Just now. I would gladly contribute to documentation, but I can not even start figuring out how things are intended to work and what is missing.

Faced this this issue updating UI Fabric. Have no idea how to fix without ruining my other changes... Rolling back...

Unfortunately, rolling back become even more painful procedure... So I have tried @mike-barnett approach... And it didn't worked either...
Preparing for another half of the day wasted...


Installer fails to setup deps in termux dev builds

i found an issue with installer in termux-dev builds
it fails to install proot-distro cause of missing repos and finally fails to install udroid tarball

Only happened with latest termux GitHub builds (probably cause of missing repos)

Also found this issue here: https://www.reddit.com/r/Ubuntu/comments/uqe4kq/comment/i8u1j9h/?utm_source=share&utm_medium=web2x&context=3

Its cause of specific mirrors which dont have all the packages
probably add a warning & --force-fix system by scanning present apt mirrors

for later


Include instructions for scene delegate

New projects since iOS 13 include a scene delegate and the provided instructions don't work in such cases.

I'll support OpenURLOptions. #28
Thanks!


epoch system

This PR implements a new format for how piers store their event logs on disk.
Resolves #313.
Design
Existing format:
./zod/.urb/log
├── data.mdb
└── lock.mdb

New format:
./zod/.urb/log
├── 0i0             # epoch dirnames specify the last event of the previous epoch
│   ├── data.mdb    # lmdb file containing events 1-132
│   ├── epoc.txt    # disk format version (this PR starts versioning at 1)
│   ├── lock.mdb    # lmdb lock file
│   └── vere.txt    # binary version this set of events was originally run with
└── 0i132
    ├── data.mdb
    ├── epoc.txt
    ├── lock.mdb
    ├── north.bin   #
    ├── south.bin   # snapshot files (state as of event 132), strictly read-only
    └── vere.txt

The new format introduces epochs, which are simply "slices" or "chunks" of a ship's complete event log. Above, you can see the ship's event log chunked into two epochs: 0i0 and 0i132.
New ships booted with the code in this PR instantiate their log directories with the new format. Existing piers are automatically migrated on boot.
Epoch "rollovers" (when the current epoch is ended and a new, empty epoch is created) occur under three conditions:

The pilot uses the new roll subcommand to manually rollover.
The pilot runs the chop subcommand.
We detect a different running binary version than the one pinned in the current epoch.

Both migrations and epoch rollovers ensure there's a current snapshot before running.
A few TODOs left:

[x] Iron out small kink in migration behavior for previously chopped piers
[x] Make sure correct binary version gets pinned to first epoch of migrated piers
[x] Rollover to new epoch when a new binary version is detected
[x] Make sure manual migration logic is idempotent
[x] Update prep command
[x] Fix chop so it works when there are 3 epochs starting with 0i0
[x] Reproduce and fix partially-deleted epoch 0i0 after chop
[x] Pair with someone to run manual GDB testing for migration idempotency and rollover logic
[x] Take a look at @joemfb's replay code and compare/find overlaps
[x] Document final system design in this PR
[x] Correct epoch naming scheme
[x] Make chop leave the latest two epochs
[x] Better error handling
[x] Better cleanup
[x] Test migration with real ships running on local-networking mode
[x] Test epoch rollover idempotency
[x] Test fresh boot
[x] Handle case where snapshot has been deleted from chk/
[x] Ensure u3_disk_epoc_good() is implemented and used how we want
[x] Ensure u3_disk_epoc_init() is implemented and used how we want
[x] Replay works with urbit play and urbit

@matthew-levan this branch has conflicts with develop.

Thanks, things move fast! Just merged develop again.
On Wed, Jun 21, 2023 at 1:03 PM Joe Bryan @.***> wrote:

@matthew-levan https://github.com/matthew-levan this branch has
conflicts with develop.
—
Reply to this email directly, view it on GitHub
https://github.com/urbit/vere/pull/459#issuecomment-1601240065, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AV2DQRGT7D2Y5FA6AT5IKKLXMMSN7ANCNFSM6AAAAAAZIHMTTY
.
You are receiving this because you were mentioned.Message ID:
@.***>

test

CI failure on linux x86_64: https://pastebin.com/nUAQu4Ap

@joemfb PTAL.  @matthew-levan says it's ready for (hopefully) final review.

I think it's worth having the file extension to keep it separate from other
instances of "vere" in the codebase.
On Tue, Jul 18, 2023 at 1:06 PM barter-simsum @.***>
wrote:

@.**** commented on this pull request.
In pkg/vere/disk.c
https://github.com/urbit/vere/pull/459#discussion_r1267077853:

u3_dire_free(die_u);

return ret_o;
+}

+/* u3_disk_epoc_vere: get binary version from epoch.
+/
+c3_o
+u3_disk_epoc_vere(u3_disk log_u, c3_d epo_d, c3_c* ver_w)
+{

struct stat buf_u;
c3_c* ver_c;
c3_w red_w, len_w;
c3_i ret_i, fid_i;
ret_i = asprintf(&ver_c, "%s/0i%" PRIc3_d "/vere.txt",

but why add .txt? I would just call it vere
—
Reply to this email directly, view it on GitHub
https://github.com/urbit/vere/pull/459#discussion_r1267077853, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AV2DQRAZD3JF6TMLVOL6MU3XQ27ARANCNFSM6AAAAAAZIHMTTY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@joemfb to reapprove

Ravioli, ravioli, give me the formuoli!


typegraphql-prisma is ahead of latest stable prisma release

Official prisma release is currently 2.8.1, yet typegraphql-prisma requires 2.9.0-dev.36
Could typegraphql-prisma separate between stable releases and dev releases?

Could typegraphql-prisma separate between stable releases and dev releases?

No, there's no time budget for separate releases. If there's a bug with stable release, I always upgrade to the latest dev one. If you can't use dev release, wait for another release with newer stable.

Support for release 2.8.1 has been added in 8d92288.
Please watch the repo releases to be notified about publishing the patch release containing the fix.


Dialog component responsiveness

The Dialog component is not responsive. On a mobile screen, it should be full width. But its width and max-width are 40% only on all screens. Please fix it.

I noticed the same thing today.

Hey there,
Please update to v2.0.3 for fixing this issue.
Regards,
Sajad


csharp/adbc/ado.net: AdbcConnection.GetSchema should work more like e.g. SqlConnection.GetSchema

DbConnection.GetSchema has a fairly well-defined contract which isn't really implemented by AdbcConnection.GetSchema.

Catalogs, Schemas, TableTypes, Tables and Columns were implemented by #1317.


⚠ GitLab Server has degraded performance

In b8f76b6, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6536 ms

Resolved: GitLab Server performance has improved in 2debe26.


Implement option to abandon room anytime, and immediate redirection to the dashboard.

done

d063de91, 6d4edc45

d063de91f5745d4e9a8cacd46a5d66a3b51d9743
6d4edc45efb8179f12964eae01da7ae8cbad66ee

d063de91f5745d4e9a8cacd46a5d66a3b51d9743

d063de91f5745d4e9a8cacd46a5d66a3b51d9743


Frame Selection Shortcut (shift+f)  activates "camera fly mode" not "Frame Selection"

Godot version -> http://godot3builds.digitecnology.com/builds/2017-12-06.12:52:48.a8ae46e14/godot-v3.0-osx.fat.zip
Issue description:
Where is the "Zoom to Selection Mode" or Frame Selection

Isn't zoom to selection just "F"?

Isn't zoom to selection just "F"?

Yes, but there is indeed a "Frame Selection" action bound to Shift+F in CanvasItemEditor:

They both act in different viewports so it should be fine, but it's true that I need to press Shift+F twice to get the frame selection (mega zoom-in on the 2D node) to happen in the CanvasItemEditor, so there's something weird happening (which might be a conflict with Freelook toggling).

If a 2D shortcut conflicts with a spatial editor shortcut that could hint a more general issue that shortcuts aren't properly encapsulated...

I'm not being able to reproduce the issue using Debian (8.10)... when i have the 2D node selected, and the canvas item editor with focus, i press SHIFT+F once, and the frame selection occurs with no issues.

They both act in different viewports so it should be fine, but it's true that I need to press Shift+F twice to get the frame selection (mega zoom-in on the 2D node) to happen in the CanvasItemEditor

this is 3d only issue. and no zoom in 3d only pan

it sould be
"F" = focus
"Shift + F" = zoom and focus
"right click" = camera fly mode

So, basically what you are experiencing is, when you press "Shift + F", it does not focus immediately on the selected object, and you can't zoom in or out... you can just look around by moving the mouse, that's correct?

no i can zoom in out with scroll manualy. i want auto zoom like blender

Well, the behavior i described is what i can experience... i click "SHIFT-F" and when using the mouse scroll, it just don't zoom in or out, despite the left distance indicator moves down or up...

Frame selection means fill the viewport. frame selection key is only panning object not zoom (frame selection).
and additionaly key binding is wrong

You cannot remove the shortcut to toggle freelook, it was requested as an alternative to RMB.
Shortcuts should be appropriately chosen.

I'm using the current master, and simply can't reproduce any issue with the SHIFT-F shortcut (the reason this issue was created i think)... both in Frame Selection (CanvasItemEditor) and Toggle Freelook (Spacial Editor).

@Zylann , for what i've seen in other issues, you developed the Freelook feature... when i was trying to reproduce this particular issue, i found that in Freelook mode there is no zoom... i tried to zoom in or out and the zoom just don't work, but there is the left indicator (zoom / distance indicator) in the viewport, that in fact responds to the scroll input... my question is:
is it supposed to have or not zooming while in Freelook mode?

@carlosfvieira there is no zoom in freelook, you just move further or closer with a configurable speed using the mouse wheel. The left indicator shows how fast you move, and if you have "link with zoom" checked, that speed will be adjusted from the zoom level you have in pan/orbit mode.

Oh Great @Zylann , now i see how it works! Thanks for the explanation :)

Zylann:  We cannot remove the shortcut to toggle freelook, it was requested as an alternative to RMB for long-held usages.
Shortcuts should be appropriately chosen/changed.

In that case should be : "F" = focus with zoom
equivalent "F" in Maya
equivalent "." in Blender.


Request: No negative levels

This is a really superb mod and is carrying the torch for bag of tricks superbly.
One feature that I do miss from Bag of Tricks is the ability to disable negative levels for the party. I'd really love to see this implemented if not too difficult.

Addressed in version 1.3.8


Failing to build cargo latest with cargo latest

Problem
   Compiling minimal-lexical v0.2.1
error: Unrecognized option: 'diagnostic-width'

error: could not compile `ff` (lib)
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo v0.82.0 (D:\dev\3rd\rust-lang\cargo)`, intermediate artifacts can be found at `D:\dev\3rd\rust-lang\cargo\target`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Steps
Run this twice on cargo's repository:

cargo install --debug --path . --force
cargo install --debug --path . --force

Possible Solution(s)
No response
Notes
No response
Version
$ cargo version --verbose
cargo 1.79.0 (ffa9cf99a 2024-06-03)
release: 1.79.0
commit-hash: ffa9cf99a594e59032757403d4c780b46dc2c43a
commit-date: 2024-06-03
host: x86_64-pc-windows-msvc
libgit2: 1.7.2 (sys:0.18.3 vendored)
libcurl: 8.6.0-DEV (sys:0.4.72+curl-8.6.0 vendored ssl:Schannel)
os: Windows 10.0.22631 (Windows 11 Professional) [64-bit]

This issue should not be a bug and I can't edit it

@rustbot label +Command-install +A-building-cargo-itself

This is expected, as documented in the Cargo Contributor Guide.

But when cargo is not run via rustup, the toolchain may change based on the directory. Since Cargo changes the directory for each compilation, this can cause different calls to rustc to use different versions.

You can see under ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ff-0.13.0/rust-toolchain the ff crate has a quite old MSRV. It doesn't recognize a relatively new --diagnostic-width option from rustc.
The contributor guide also provides some workaround already. Setting RUSTC or RUSTUP_TOOLCHAIN might be good alternatives.

This is a gnarly problem that rustup and cargo are not a single binary. I don't think it is fixable at this moment, but leave this open for future reference.


QnA Maker bot greets users as "Empty bot"

Create a new QnA Maker bot, and the greeting is "Welcome to the EmptyBot sample"

Version
Version:  1.4.0-nightly.238265.5106247
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

Fixed here: https://github.com/microsoft/botframework-components/issues/895#event-4638342358

Hi, can someone help me please? I'm trying to connect my bot from Bot Framework Composer with my kb from qna maker but i don't understand what i do wrong.

When i try to put the informations from my kb, this message appear.

I'm waiting for your response. Thank you!


Allow access to the output smiles atom ordering from Python

The _smilesAtomOutputOrder property (an std::vector) is not accessible from python via GetProp.

Was this ever added?


Add pick-your-wallpaper extension

Description
This Raycast extension allows you to quickly change your desktop wallpaper by selecting an image from a folder of your choice.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@hugomarf where did you the the wallpapers from third row from 🙂

@hugomarf where did you the the wallpapers from third row from 🙂

They are from this awesome artist I found on twitter.

All the ones in that screenshot are specifically from Wallpaper Pack 2! Can't express how much I like his work.


submenu pathMatch doesn't work at all

Issue type
I'm submitting a ...  (check one with "x")

[ x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Issue description
Current behavior:

I want to highlight the pathMatch 'menu' when user redirect to the child page, but it doesn't work
Expected behavior:

I want to highlight the pathMatch 'menu' when user redirect to the child page
Steps to reproduce:

Here is the menu setting snap:
{
title: 'Order Manage',
icon: 'nb-grid-b',
children: [
{
title: 'Order List',
link: '/pages/order/order-list',
},
{
title: 'Order Detail',
link: '/pages/order/order-detail',
pathMatch: 'order-list',
hidden: true
}
],
},
refer to the above code, the menu 'order-detail' is hidden as expected, but when I redirect to the path 'http://localhost:4200/#/pages/order/order-detail', the menu 'order-list' doesn't be highlighted as expected, please advise. Thanks in advance

Related code:

insert short code snippets here

Other information:
npm, node, OS, Browser
<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular
<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

@JohnnyXuPeng
I noticed that sometimes the page DOM does not get updated accordingly.
Maybe do a ChangeDetectorRef or something like that?
https://angular.io/api/core/ChangeDetectorRef

Hi @JohnnyXuPeng. NbMenuItem.pathMatch works very similar to Route.pathMatch and supports only two options: full and prefix. First means compare NbMenuItem.link property to be exact as URL's path part and latter - URL path should contain NbMenuItem.link.
If I understood you correctly, you want to highlight order-list menu item when the path is /pages/order/order-detail or /pages/order/order-list. You can't assign multiple links to one menu item. But as a workaround, you can add hidden menu items as children of the menu item which should match multiple paths. And when one of the children match path parent menu item will be highlighted as well.
Here is example implementation. Initially, path is pages/order/order-list. Try to navigate pages/order/order-detail and notice that 'Order List' menu item is highlighted. See app.component.ts for the code example of work around described above.
And thanks for help @Prefix1802 👍

For me worked add pathMatch: 'prefix' for parent and every child.

For me worked add pathMatch: 'prefix' for parent and every child.


Live Share doesn't work on Notebooks

Version: 1.61.0-insider (Universal)
Commit: ec40cbe164c59f3d13b6eff5fc7b0231ec0ab7aa
Date: 2021-09-13T05:13:59.036Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0
Live Share Extension Version: v1.0.4836
Target Platform or Language [e.g. Node.js]: Jupyter Notebooks, Python
20:40 of video log
I added a coworker into a project of mine with Notebooks.
She first didn't see any of the files I added locally in my machine that wasn't checked into the repo yet. I also wasn't able to see her cursor nor any of her changes like adding cells and modifying text.
I did see her in the list of people in the session though.

Hey @tanhakabir, thanks for the video of the issue. This looks like a duplicate of #4199 we had a few months ago where users were complaining of a "dropped connection" where coediting suddenly stopped working but with no indication of a desync.
It seemed at the time like an issue with a specific version of Jupyter notebooks. However, this week I have been looking into some issues with disposing our notebook components properly which could be causing this. I'll investigate tomorrow and provide updates here.

I tried to reproduce this issue myself and found following:

I need to run "Follow Participant" explicitly from the Live Share view otherwise the notebook opened on the host side is not opened on the guest side
Output changes are not synced on the guest side by default. I think this is for security but it's not straightforward
Once the guest requests execution permission, execution state and outputs are now synced

@alyssajotice can you help confirm what I saw is as expected
I also see following errors sometimes
CRITI FAILED to destory notebook Error: Cannot register more than one working copy with the same resource vscode-notebook:vsls:/samplenbsandscripts/troublenotebooks/smalltest.ipynb and type .
    at E.registerWorkingCopy (workingCopyService.ts:140)
    at new c (notebookEditorModel.ts:104)
    at f._createInstance (instantiationService.ts:110)
    at f.createInstance (instantiationService.ts:76)
    at d.createReferencedObject (notebookEditorModelResolverServiceImpl.ts:69)
    at processTicksAndRejections (internal/process/task_queues.js:93)
    at async o.resolve (notebookEditorModelResolverServiceImpl.ts:216)
    at async l.$tryOpenNotebook (mainThreadNotebookDocuments.ts:152)

I wonder if Live Share tries to open the same resource with another editor type

@alyssajotice , is this one addressed now?

Yes, closing now.


Custom commands don't work

What would an example of valid customCmds be? I can't get any ftp commands to work:
connected: 220 Microsoft FTP Service
FTPError: 500 Command not understood.
Ftp Upload failed

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

ID: b2ea8b7b-44cb-e315-b086-c4e3361bf59a
Version Independent ID: 5fcdaa72-ca89-2139-a8c9-2eb263b4824e
Content: FTP Upload task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/ftp-upload.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

@crowleysoftware -- thank you for your question. It looks like you're working through an issue with your scenario or implementation. Here are a couple of options where you might consider asking your question:

Azure DevOps Support Bot
Azure DevOps on Stack Overflow

@vijayma -- please look into this issue.


How can i put my own songs in this source code ?

How can i place my own songs in this app ?
Please response

you can play your local storage audio file with this app . What do you mean by place your own song ?

I am about the audio file , where i have to put more audio files for add more songs ?

I can't play local song from this app (flac, or mp3)

Hey. Sorry, but the issues here are intended for problems or feature requests for the Android Universal Music Player, not for general support issues. I'd recommend checking out Stack Overflow and asking your question there.


Grouping multiple unrelated Git repos into a single "affected" entry is confusing

Example: CVE-2020-8927
Multiple unrelated git repos are grouped into a single affected entry, which leads to a confusing "affected versions" list which seemingly only applies to the first git repo (at least in this example - is this guaranteed?).
Perhaps it would be more clear if the git repos were separated into individual entries with their own versions array?

@andrewpollock would be the best person to address this, but he's out-of-office until next week.

Hi @Bo98
I'm sorry you're finding this behaviour confusing.
Do you have any suggestions on what would be helpful here?
An FAQ entry with signposting from the individual vulnerability page?
(please reopen with any concrete suggestions if you have them)

which seemingly only applies to the first git repo (at least in this example - is this guaranteed?)

In short, this is not a correct interpretation, see below.
The relevant code: https://github.com/google/osv.dev/blob/dd9566e0a858e03b552a61cb03f0663f14ab43aa/osv/impact.py#L529-L602
So looking at https://api.osv.dev/v1/vulns/CVE-2020-8927 specifically:
curl -s https://api.osv.dev/v1/vulns/CVE-2020-8927| | jq '.affected[9].versions'
[
  "v0.1.0",
  "v0.2.0",
  "v0.3.0",
  "v0.4.0",
  "v0.6.0",
  "v1.0.0",
  "v1.0.0-rc1",
  "v1.0.0-rc2",
  "v1.0.1",
  "v1.0.2",
  "v1.0.3",
  "v1.0.4",
  "v1.0.5",
  "v1.0.6",
  "v1.0.7",
  "v1.1",
  "v1.1.0",
  "v1.1.0-preview1",
  "v1.1.1",
  "v1.1.2",
  "v1.1.4",
  "v2.0.0",
  "v2.0.0-preview1",
  "v2.0.0-preview2"
]

is derived from the relevant tags present in any of the three of the repos from the relevant ranges:
curl -s https://api.osv.dev/v1/vulns/CVE-2020-8927| jq -r '.affected[9].ranges[].repo'
https://github.com/dotnet/core
https://github.com/google/brotli
https://github.com/powershell/powershell

Proof:
$ git ls-remote -t https://github.com/dotnet/core | fgrep -f <(curl -s https://api.osv.dev/v1/vulns/CVE-2020-8927 | jq -r '.affected[9].versions[]')
1d31854df431523a4699a4a94dc924b76317f47b        refs/tags/v1.0.0
6251598c0087239b392cccda68515cd8c71d7f3d        refs/tags/v1.0.0^{}
6030c481946d683a68cd024d8b600483047783ca        refs/tags/v1.0.0-rc1
247cf6d5c4e91ea2b53182d152aa8eda5754aa1c        refs/tags/v1.0.0-rc2
4222ca3903679bbb680ef44abcde9a260ca97479        refs/tags/v1.0.1
0f3c68d295798951f6d96925f452718721b6f550        refs/tags/v1.0.1^{}
2cfe0ed1939ef93ebc245cc6bf6cbadde578075e        refs/tags/v1.0.10
cedfbca6aa645a550a3e9d221943395c9db7c510        refs/tags/v1.0.11
9bdb9f2628ae2d96fdd4a19aaa7707f1d5ec494f        refs/tags/v1.0.12
22422b4c3fe95777faf8feaebf098230291bd0f4        refs/tags/v1.0.13
ec9ff2d8f486d3ec5ee3c00b122b0c4a5f9eebc8        refs/tags/v1.0.14
9c95f339ba7e29c25cfb6753255bdb5cadea9957        refs/tags/v1.0.15
3dacb1d9cc36f1c9bd0fadb00f56ac356f7469be        refs/tags/v1.0.16
408817dd19dc3effd7e6f9657b1c31022d7a536d        refs/tags/v1.0.2
427b2f13a3b218d5fa309f6a12fa7b8b307ce20d        refs/tags/v1.0.2^{}
6474336beb517e5c5610791a30fa5cd35123dd93        refs/tags/v1.0.3
c6efffe6c7cb220af3819b4a9dabe687023984e0        refs/tags/v1.0.3^{}
1e76df0f0173a04819bfdd5f3f8c49a95e683bf2        refs/tags/v1.0.4
f0bd1c2180483dde5d5283639176f98918d1e3d4        refs/tags/v1.0.4^{}
11f502a023e97148333f90d4800d12d76240ef6e        refs/tags/v1.0.5
aaea89e8d9d2496291ff53396d0eccbca839ae83        refs/tags/v1.0.7
218888387c3e7aff6241f65599529620fb7b4127        refs/tags/v1.1
c00ac07535cc9c37cd8addfc8772e016fe6f5539        refs/tags/v1.1.0
6251598c0087239b392cccda68515cd8c71d7f3d        refs/tags/v1.1.0^{}
6c0b42a5c14815a3c6c66873c769103fe5592f28        refs/tags/v1.1.0-preview1
8b11243b41c6d44ed7f654b55d858001c129e22d        refs/tags/v1.1.1
f0bd1c2180483dde5d5283639176f98918d1e3d4        refs/tags/v1.1.1^{}
22422b4c3fe95777faf8feaebf098230291bd0f4        refs/tags/v1.1.10
ec9ff2d8f486d3ec5ee3c00b122b0c4a5f9eebc8        refs/tags/v1.1.11
9c95f339ba7e29c25cfb6753255bdb5cadea9957        refs/tags/v1.1.12
3dacb1d9cc36f1c9bd0fadb00f56ac356f7469be        refs/tags/v1.1.13
11f502a023e97148333f90d4800d12d76240ef6e        refs/tags/v1.1.2
aaea89e8d9d2496291ff53396d0eccbca839ae83        refs/tags/v1.1.4
8b41c63650f1c1223ce82de5d9040c1f7ff470c1        refs/tags/v1.1.5
d33e85105ecef7814cfff53852e89d7366ff2876        refs/tags/v1.1.6
cedfbca6aa645a550a3e9d221943395c9db7c510        refs/tags/v1.1.7
cedfbca6aa645a550a3e9d221943395c9db7c510        refs/tags/v1.1.8
9bdb9f2628ae2d96fdd4a19aaa7707f1d5ec494f        refs/tags/v1.1.9
f3c64ec2d713c053b20bcf90e962cd7fb161370c        refs/tags/v2.0.0
61c2be531cf5e36940baa5c67233b0a01c51e1dd        refs/tags/v2.0.0-preview1
a6a596009df17884a8260b5575e014fe55846d1a        refs/tags/v2.0.0-preview2

$ git ls-remote -t https://github.com/google/brotli | fgrep -f <(https://api.osv.dev/v1/vulns/CVE-2020-8927 | jq -r '.affected[9].versions[]')
d811b186c5037b434d56ddb831ceccdf5a954687        refs/tags/v0.1.0
7f7a2fb48cec63c0459ec6b6e7260810bfb01819        refs/tags/v0.2.0
98ed7a23a83d64133b0a36a884e489bffb0eb864        refs/tags/v0.3.0
29d31d5921b0a2b323ac24e7f7d0cdc9a3c0dd08        refs/tags/v0.4.0
46c1a881b41bb638c76247558aa04b1591af3aa7        refs/tags/v0.6.0
c60563591a9a86196f19987c81dde4384a088861        refs/tags/v1.0.0
5b4769990dc14a2bd466d2599c946c5652cba4b2        refs/tags/v1.0.1
0ad94eed00420bf1154cb16a289aa27efbb30c01        refs/tags/v1.0.2
533843e3546cd24c8344eaa899c6b0b681c8d222        refs/tags/v1.0.3
c6333e1e79fb62ea088443f192293f964409b04e        refs/tags/v1.0.4
b601fe817bd3217cb144bbb380a43cae8e847388        refs/tags/v1.0.5
6eba239a5bb553fd557b7d78f7da8f0059618b9e        refs/tags/v1.0.6
d6d98957ca8ccb1ef45922e978bb10efca0ea541        refs/tags/v1.0.7
ed738e842d2fbdf2d6459e39267a633c4a9b2f5d        refs/tags/v1.1.0
2a5a088b03ba5fd3aab4f34338c84e2c61d82c49        refs/tags/v1.1.0rc

$ git ls-remote -t https://github.com/powershell/powershell | fgrep -f <(https://api.osv.dev/v1/vulns/CVE-2020-8927 | jq -r '.affected[9].versions[]')
9bcbca3700ded4c2d99f8c5b2ce8b313130b162c        refs/tags/v0.1.0
704704140414dcc7f734e30c7fa1073fff5dd9a3        refs/tags/v0.1.0^{}
42afa34d2e4809f722b28e550aea44c649ebd314        refs/tags/v0.2.0
21401f852ef446d6de41b906b533a385ae83ba1e        refs/tags/v0.2.0^{}
9ec48565842980cb762f84778cb6bbed825d3546        refs/tags/v0.3.0
2629fff55ed6cf6665007fd15ea97d3cd203f465        refs/tags/v0.3.0^{}
43f2223fb24e0163b1a2a16d9bae16d968973aff        refs/tags/v0.4.0
85f45399c3c8bcef2f47f8dd1bc2cb414b0798c3        refs/tags/v0.4.0^{}
89d002d460e6d6dc32e91e97b4d80d04897a4ec1        refs/tags/v0.6.0
43f07425e9e2c92dd14c7d1f823e4aeec91dd56a        refs/tags/v0.6.0^{}

Your example demonstrates the problem a bit.
The v1.1.0 tag is ambigous. You identified it to apply to dotnet/core and google/brotli. However this is not correct as the last affected version is v1.0.7.
Note sure what happened to the powershell/powershell repo as affected range there is v7.0.0 to <v7.0.9 according to the git commit ranges.

The problem really is merging git repos into one entry defeats the purpose of versions. The schema states:

The versions list is generally recommended to always be present, to allow software to easily answer the question “is this specific version affected?” without having to contain code specific to every different ecosystem.

It's impossible to reliably use the versions array here without querying the git repos and thus have code specific to the git ecosystem.
I've updated my code to ignore any vulnerability with multiple git repos. Does mean I lose some CVE coverage but is likely the best I can do here.

Thanks for the feedback @Bo98 !
I think there's a great point to be made here to separate the affected entries by git repo.
That said -- how are you making use of the versions array here? Our intention was for consumers to use the commit hashes for unambiguous matching instead of the version tags.

I have a set of packages/dependencies where I know what git tag is being used but would need to clone the repo in order to do a commit comparison. In particular, I may not even have the git repo cloned.
For example, I may have a brotli dependency that uses https://github.com/google/brotli/archive/refs/tags/v1.1.0.tar.gz. From that I know the git tag - it's v1.1.0. The idea was to use the versions array to know whether this is affected or not. If it were commit hashes instead, I would need to clone the whole repo and do git-specific comparisons I ordinarily would not need to do for other ecosystems. The schema recommends the versions array as the way to do this.
I already use versions array (and semver) for PyPI etc dependencies so the same version comparison code is already used for all non-git ecosystems and it would be useful for git ecosystem to work the same as the others.


Remove fuse mechanism (#97)

This change set removes the Fuse mechanism and solves https://github.com/trivago/gollum/issues/97
Note: the "// TBD: health check?" comments do not mean that a health check should be implemented in exactly that position, they serve as pointers towards implementing health checks in general.

Coverage decreased (-0.6%) to 33.838% when pulling 8eb4b35c4e890a60cc363ea9c25e4a447a865c90 on ghissue-97-remove-fuse-mechanism into 1e2ea95b65e23471d4013b5bbd6405ef6066ada1 on master.

Coverage decreased (-0.6%) to 33.838% when pulling 80e371199a2b93bc446fa31db4c708f1b1357389 on ghissue-97-remove-fuse-mechanism into 1e2ea95b65e23471d4013b5bbd6405ef6066ada1 on master.


[Bug]: Improper behavior

Contact Details
No response
What happened?
Automatic rollover does not happen for me.
Because of this, I tried the \rollover command, but an unwanted thing happened: The daily docs itself were rolled underneath the present day, instead of only the unfinifhed todos, and now those daily docs were permanently moved from the regular daily docs powerup page, and this cannot be undone.

Relevant log output
No response
Code of Conduct

[x] I agree

Thank you!! I'll take a look into this.

Hey @hugomarins! I have a quick question, were you watching the time waiting for them to rollover? Like staying in the app until they rollover? I failed to mention in my initial posting of the plugin that the current functionality is a check system, so when the autoRollover event is triggered it can do the rolling over, but I have not yet made it live update-compatible.
Because of this, I can't exactly reproduce the issue yet, but I think I understand why it may be confusing. So, I'll definitely be considering adding that live-rollover option. It makes sense!

I also can't reproduce the daily docs themselves being moved up into the rem itself. Could you show me what your rems looked like before? Are you able to make that bug happen again?

I'm planning on changing the behavior to portalling rems in instead of actually moving them, so maybe it is a RemNote version incompatibility thing. What are your app specifics?

What I tried to say is that my to-dos never rolled. At first, it was set to 00:00h. After a few days, I saw automatic rolling was not happening. Then I set the time to that time and watched to see if something will happen. But it did not. That's why I tried to force the rolling over using the \rollover command.

I tried to reproduce the bug, but now nothing happens when I use the  \rollover command.

Oh ok. @hugomarins There is a softlock to how many days back it looks, and the default is set to 7 days. Could you try setting the days it looks back in time to a greater value?
I'm going to push a hotfix right now, if you have issues with it further, please let me know.
Methodology to test the automatic time

Set the setting to a time that you can test (it has to be greater than the time currently. for ex. do a minute forward)
run /debug auto rollover
wait for the set time to roll in, then it will roll over.

changing the setting will not tell RTD that it is a new day. if it has already run in the current day, it will not at all for the rest of that day unless the slash command is used.

The issue of not automatically rolling over was resolved in 917ba2f. Please reopen if you are still having issues 😄
have a great day!

Yeap, working perfectly now. The idea of portals was terrific! Thanks for your efforts!


Nexus Project - Review data

Review of data collected on this Desktop Review document

@chpicone @simboss here the spreadsheet for the Data Review. I started by reviewing this site and creating a qgis project to understand how to use the data.
I will continue with the review next week.

@giohappy I add a new data on the spreadsheet and on the geonode istance


book export PDF contents directory link does not work

Describe the Bug
when you click on the hyperlinks in the contents directory on the first page of the PDF book export, they want to redirect you to an html page which is located in file://tmp/... and not to the corresponding page in the PDF book.
Steps to Reproduce

export a book as PDF
click on any page in the exported PDF in the contents directory

Expected Behaviour
that it jumps in the pdf to the corresponding page
Screenshots or Additional Context

Browser Details
No response
Exact BookStack Version
22.04.2
PHP Version
No response
Hosting Environment
as a Docker container from linuxserver

Thanks for reporting @Tusher43, but I'm going to close this off as a duplicate of the existing open issue #2459.


Adding icons to the footer

Is your feature request related to a problem? Please describe.
Adding icons to the footer
also aligning the contact section of footer  in homepage

adding icons like this in footer

Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

The footer related issue was assigned before and he is resolving it.
And we don't want any further updation of footer.
So I am closing this issue.
Please understand.


Remove IAcknowledgedResponse implementation from IRevertModelSnapshotResponse

Relates: https://github.com/elastic/elasticsearch/commit/ac0d9f333e4bc0028b20d9728f44c788d04a1acf

Closing this as added in 7.x in 35b9a7e59f7705c92161f5d62148ab33af02aec5


Unsubscribe event listeners when ghostmode is disabled

Even if we disable ghostmode the client continues to listen to events, including scroll. This becomes problematic when profiling application performance because browser-sync-client pollutes the frames and forces browsers to reflow content by reading window.pageXOffset and window.pageYOffset. See attached screenshot:

Do you think it would be a good idea to subscribe/unsubscribe event listeners when changing options?

Fixed in<EMAIL_ADDRESS>- Thanks :)


TypeScript typings are wrong.

https://github.com/trufflesuite/ganache-core/blob/bda6a4ae07400dc5567aa50776e4432f96d3ae1e/typings/index.d.ts#L1-L48
The TypeScript type definitions for this project appear to be incorrect.  If I do import ganache from 'ganache-core' my project will compile without trouble but will fail at runtime due to ganache being undefined.  However, if I instead do import * as ganache from 'ganache-core' or import { server } from 'ganache-core' I get compile-time errors but the script runs at runtime.
I believe the proper definition should look something like this instead:
declare module 'ganache-core' {
	import { Provider as Web3Provider } from "web3/providers";
	export interface IProviderOptions {
		account_keys_path?: string;
		accounts?: object[];
		allowUnlimitedContractSize?: boolean;
		blockTime?: number;
		db_path?: string;
		debug?: boolean;
		default_balance_ether?: number;
		fork?: string | object;
		fork_block_number?: string | number;
		gasLimit?: number;
		gasPrice?: string;
		hardfork?: "byzantium" | "constantinople" | "petersburg";
		hd_path?: string;
		locked?: boolean;
		logger?: {
			log(msg: string): void;
		};
		mnemonic?: string;
		network_id?: number;
		networkId?: number;
		port?: number;
		seed?: any;
		time?: Date;
		total_accounts?: number;
		unlocked_accounts?: string[];
		verbose?: boolean;
		vmErrorsOnRPCResponse?: boolean;
		ws?: boolean;
	}

	export interface IServerOptions extends IProviderOptions {
		keepAliveTimeout?: number;
	}

	export function provider(opts?: IProviderOptions): Provider;
	export function server(opts?: IServerOptions): any;

	export interface Provider extends Web3Provider {
		close: (callback: Function) => void;
	}
}

Do the current typings actually work for anyone?  If so, how are you doing your imports?  If not, I can submit a PR with the above change.

@CruzMolina and @nicholasjpaterno created these Typings. Can either of your confirm that these typings work where you needed them?

Hey @MicahZoltu! Based on the current typings structure, you'll have to import the Namespace (import Ganache from "ganache-core") to get things working.
Here's an example where we use the typings in one of Truffle's tests: https://github.com/trufflesuite/truffle/blob/develop/packages/hdwallet-provider/test/provider.test.ts
I'm not sure on the completeness of the typings, but so far I haven't run into an issue with them.

The proposed solution of import Ganache from 'ganache-core' does not work for me.  I'm surprised that your solution works because looking at ganache-core/index.js it has module.exports = require('./publicexports.js') and publicexports.js has:
module.exports = { server, provider } // truncated for brevity

Note that it does not have a default export, so import Ganache from 'ganache-core' shouldn't work since that is a a default import.
I do notice that in index.js you are conditionally exporting from a bundle.  I wonder if one of us is hitting the one of the exports, and the other is hitting the other export and they are not the same?

Full Repro
index.ts
import Ganache from 'ganache-core'
Ganache.server()

tsconfig.json
{
	"compilerOptions": {
		"target": "esnext",
		"module": "commonjs",
		"moduleResolution": "node",
	},
}

mkdir test
cd test
# --ignore-scripts to avoid running into problems with node-gyp failing to install unnecessary dependencies
npm install typescript ts-node ganache-core --ignore-scripts
npx ts-node index.ts

Cannot read property 'server' of undefined

@MicahZoltu Can you try doing this? It worked for me.
import ganache from 'ganache-core';

const server = ganache.server();

server.listen(8545, () => {
  console.log('server started');
});

@zemse When importing default exports the name chosen by the importer doesn't matter.  I could do the following and it would be functionally equivalent.
import apple from 'ganache-core
apple.server()

Did you use the same tsconfig.json as I did above?  Were you using a newer version of ganache-core?

@zemse When importing default exports the name chosen by the importer doesn't matter. I could do the following and it would be functionally equivalent.

Oh! I think I forgot this fact in my instincts. Maybe, frequently using the named export in my projects instead of default export did that to me.

Did you use the same tsconfig.json as I did above? Were you using a newer version of ganache-core?

I am using the version 2.10.2 (installed yesterday). This is my tsconfig.json.
{
  "include": ["src/**/*.ts"],
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "outDir": "build/",
    "rootDir": "src/",
    "downlevelIteration": true,
    "strict": true,
    // "moduleResolution": "node",
    "forceConsistentCasingInFileNames": true
  }
}

Can you try using this version?

Closing, as the typings have since been fixed. Please make a new issue if you find this is not the case for you. Thanks!

Closing, as the typings have since been fixed

Have they? I'm using<EMAIL_ADDRESS>and all I get is provider and server in my VSCode auto-complete:

I'm using this tsconfig.json file.

Yes, that's all there is at that level.

I see. And is there no way to import specific types like "IProviderOptions"?

and all I get is provider and server in my VSCode auto-complete

I have observed that when you type next to a : of a var while specifying type, it gives more suggestions.
import Ganache from 'ganache-core';

const variable: Ganache. // gives more suggestions like IProviderOptions

Hope this helps

Yes, IProviderOptions is only type, and doesn't have a corresponding runtime component, whereas provider and server are both types AND have a runtime component (the function). When coding, TypeScript recognizes if you are writing runtime code or type code, and only gives you appropriate hints.
examples:
// runtime
const doesntMakeSense = Ganache.IProviderOptions; // would be `undefined` since this is runtime code, a `IProviderOptions` doesn't have a runtime component

type myType = Ganache.IProviderOptions // works because this is type-level code
let myThing: Ganache.IProviderOptions = {gasPrice: 123456}; // works because this is also type-level code

I'm sure there is a better way of explaining it, but hopefully this helps clear things up for you.


Schema accessor

🎉 New feature
Closes #1376
Summary

I've created a script format_sdf.py which reads from the /sdf/1.11 folder and generates/updates the source for all the relevant classes in the src/ and include/ directories as per the suggested implementation.
There were DOM elements navsat.sdf and forcetorque.sdf for which the script does not work and I had to manually edit the script because their naming convention did not match the camel-case conversion (they would need to be nav_sat.sdf and force_torque.sdf respectively to function correctly with the script) This may be undesirable from a code style perspective but may be a breaking change—this is a minor point but I just wanted to point it out.
The code builds successfully, I have not thoroughly tested it but it does seem to work.
I can add tests for the SchemaFile in all the DOM element tests but I thought it might be overkill because the names are hardcoded in the method anyways. I can add it easily with the script if needed.

Test it
Tests can be done manually as mentioned by the OP in #1376 in his code example.
I could also add tests in the DOM element unit tests, but that might be overkill because the values are hard-coded.
Checklist

[ ] Signed all commits for DCO
[x] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@aagrawal05 Looks like there are some style issues and a DCO error. Mind fixing them?

@aagrawal05 Looks like there are some style issues and a DCO error. Mind fixing them?

Hey @azeey sure let me take a look. The style issues look fairly straightforward and I'll shortly submit changes to fix this. Please let me know if anything further is to be done in terms of functionality.

Hey @azeey in attempting to resolve the DCO error through a rebase, it appears that I have accidentally re-committed all the 23 commits from my first changes before the merge to my latest changes...
I believe it may be a bit complicated for me to proceed accurately to revert this from this point. I feel it might be easier to just close PR and create a new PR on a new branch with a single commit (this also has the added benefit of being merged with the latest changes in sdf14).
With regards to the style I believe the errors should be resolved but I need to test with the linter using the workflow.
Please let me know how to proceed.

@aagrawal05 yes, I think I new PR would be cleaner. It would be ideal if you can target sdf15 as well.


install_debian: Some Quality of Life Enhancements

Ubuntu also suffers from this derp now.

Fix the if-else statement.

@windowz414 Done with ❤


Payment status max 6

What this PR made?
Changed the max_length of status, on class Payment, from 2 to 6, because of the max length of word's choice 6 characters. -> PAYMENT_CHOICES = (('made', 'made'), ('missed', 'missed'))

Yes, @cesarbruschetta, I'm sorry. How can I change to development?


Backport 1536

This backports #1536 to the 2-8-stable-branch.
Why
Though mail v2.8 enabled turning TLS/STARTTLS options off (this surfaced as net-smtp's default value for starttls went from false to :auto), it also introduced some new problems:

having ssl false would ignore any starttls-setting
enable_starttls: false ignores the enable_starttls_auto-flag.

These issues were fixed on mainline but I think it's worth to have these in a new 2.8 release as well.
Impact
Possible outcomes:

having either ssl or tls truthy ánd having truthy values for any of enable_starttls*-flags set will now raise an ArgumentError.
While mail is stricter in this regard, net-smtp would already consider this a non-acceptable config.
another scenario: a config with enable_starttls false and enable_starttls_auto true resulted in starttls :auto <v2.8, in v2.8 this resulted in starttls false and would now again be set to :auto.

Did I miss anything?

@ahorek @sebbASF review appreciated.

Merging as this was reviewed/discussed in the master-PR.


Support Google Cloud Container Registry credential helper

Pulling images from the Google Cloud Container registry fails with the following error:
Could not build image: The credentials returned for 'eu.gcr.io' by the credential helper executable 'docker-credential-gcloud' are invalid: there is no 'ServerURL' field.

The reason seems to be because the Username reported by the credential helper is _dcgcloud_token instead of the expected <token>.
This is the extract from the batect log file (replaced the actual secret with "xxx"):
{
    "@timestamp": "2019-05-22T14:50:35.754Z",
    "@message": "Process exited.",
    "@severity": "debug",
    "@source": "batect.os.ProcessRunner",
    "@processId": 14167,
    "@threadId": 14,
    "@threadName": "pool-1-thread-1",
    "output": "{\n  \"Secret\": \"xxx\",\n  \"Username\": \"_dcgcloud_token\"\n}\n",
    "exitCode": 0,
    "command": [
        "docker-credential-gcloud",
        "get"
    ]
}

Hey @tjacoby, thanks for taking the time to report this issue. Looks like the GCP credential helper isn't quite meeting the requirements of a credential helper and this is breaking things. This is a relatively easy thing to workaround though, so I'll take a look and push out a fix shortly.

I've just pushed a fix for this and it should be part of the next release. Thanks again @tjacoby!

Hi Charles,
thanks for picking up my request so quickly. I built batect locally from master and tried the fix but unfortunately it still doesn't work.
It fails with the following error now:
build-env: building image: step 1 of 17: FROM eu.gcr.io/xxx-xxx-xxx/conda:814a9e1654ac16c661ba60f78e81782c26eadf3d

Error: Could not build image from directory '/home/xxx/xxx/xxx/gcp_xxx/docker'.
Building image failed: unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication. Output from build process was:
Step 1/17 : FROM eu.gcr.io/xxx-xxx-xxx/conda:814a9e1654ac16c661ba60f78e81782c26eadf3d
unauthorized: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication

I saw that you are using a PasswordDockerRegistryCredentials for the Google container registry. I tried changing the code to use TokenDockerRegistryCredentials but this still does not fix the issue (and causes the same error message as above).
Does the documentation from Google provide some more hints for you? https://cloud.google.com/container-registry/docs/advanced-authentication
Building the docker file manually from the terminal via docker build .  works without issues.

I tried it with pulling an image directly it was working for me - are you able to try pulling an image directly and see if that works for you?
So instead of build_directory: ..., use image: eu.gcr.io/xxx-xxx-xxx/conda:814a9e1654ac16c661ba60f78e81782c26eadf3d

Yes - pulling the image works

OK, looks like there's an issue with building images - I'll take a look.

I've fixed the issue building images as well, and this will be part of the next release.
If you want to use a version with this fix in the meantime, https://bintray.com/charleskorn/batect/batect should have a pre-release version available with this fix in the next 20 minutes or so.
Thanks again for your feedback @tjacoby!


Add LeetCode 1748. Sum of Unique Elements

Problem Link

Please assign me this issue!

Assigned to @aniket-24