Correctly use dtype when computing shared memory requirements of separable convolution

closes #408
An error in the keyword arguments passed to the shared memory calculation is fixed in the first commit here. In the second commit, a second fallback is added in case of any other anticipated compilation failure.

rerun tests

Thanks Greg! 🙏
Happy with merging. Only question would be if we can include a test for the error. Could happen in this PR or after

Only question would be if we can include a test for the error. Could happen in this PR or after

Test case has now been added (values aren't checked, it is just to verify that no compilation error occurs). I verified that without the fix in this MR, the dtype=float64 case fails for the parameterized sigmas 16, 21, 26 and 31 on my system.

@gpucibot merge


Added Australian Government data

#21

@juliawong looks great. Can you please fix the branch conflict? Thanks!

@jdorfman Conflict fixed! :smile:


Import issues when using in Typescript

Something seems to be wrong with this import https://github.com/digitalbazaar/ed25519-signature-2020/blob/main/lib/Ed25519Signature2020.js#L12 when consuming this library in a typescript project. Specifically I'm hitting this error while running tests in jest.
/path-to-project/node_modules/@digitalbazaar/ed25519-signature-2020/lib/Ed25519Signature2020.js:1
    TypeError: Cannot read property 'constants' of undefined

      at Object.<anonymous> (node_modules/@digitalbazaar/ed25519-signature-2020/lib/Ed25519Signature2020.js:14:40)
          at Object.<anonymous> (/path-to-project/node_modules/@digitalbazaar/ed25519-signature-2020/lib/main.js:1)

Just wondering if anyone has seen anything like this and how I could get around it

Hi @JaceHensley!
Best that we could determine, this is happening due to our use of the esm runtime transpiler (which we're using for supporting both CommonJS and ESM import styles). Sounds like it's breaking imports for some Jest and TypeScript users.
We're looking into what we can do instead.

@JaceHensley,
We're looking for a quick fix, but we don't have a test harness for this problem over here. Are you able to share some simple test case code we could run? Alternatively, are you able to easily try temporarily changing that import line in your installed package from:
import suiteContext from 'ed25519-signature-2020-context';

To:
import {constants, contexts} from 'ed25519-signature-2020-context';

And update the lines that referenced suiteContext to use constants and contexts directly -- to see if it improves your situation? We could make a patch that does this if it does.

is there any progress on this?
I'm trying to use this in a frontend app that doesn't allow configuration like @JaceHensley suggests.

@mirceanis not yet. :) We're slowly working on re-writing the dependencies in ESM-only.
But meanwhile, you should use the TypeScript-friendly fork over at https://github.com/digitalcredentials/ed25519-signature-2020 (maintained by me).

No progress yet, but an update is that it's now near the top of the priority list so should be addressed fairly soon.

I believe this has been fixed with the removal of esm.js. Closing -- feel free to re-open if it's still broken for some reason.


PROPOSAL - Add slash commands for submitting standup information.

Is your feature request related to a problem? Please describe.
I'm frustrated that I have to use the UI to submit my stand up but I can configure the tool with slash commands.. I'd like to have both an interactive and a non interactive way to submit the standup using slash commands.
Describe the solution you'd like
/standupsubmit_gui - Opens the current modal dialog without needing to click the extension menu in the UI.
/standupsubmit_cli "some logical format to submit responses in text format" - Ability to drop the report into the system in one line of txt.

Thanks for the suggestion and feedback @skyscooby !
I think I understand the problem taking your hands away from the keyboard just for clicking that button. Keyboard shortcuts rock 🤘.
Opening standup UI via a slash command is an interesting idea and this could speed things up.
We have also been thinking of many more ways of making filling standup a quick process. Things like automatically focusing on the input field so you can just start typing right away, adding keyboard shortcuts for navigating to next and previous tab and one for submitting the standup itself. Will include your suggestion in the discussion as well.
Thanks!

I am sorry for heavy cross-referencing this on multiple places, but I have sketched some idea for the slash command design here: https://github.com/standup-raven/standup-raven/issues/9#issuecomment-491524921
The submit enhancement through the command discussed here is incorporated, of course :)
Thank you.


add an option to hide the action kind

#54
I stumbled upon the proposal and since I've been using it, decided to make a PR.

Thank you very much!


when will put the model and code on the github?

Dear jiatianzhi,
Thanks for your interest. The code will be ready in less than two weeks' time. Model will take a bit longer as we plan to re-train it so that we have one model for all the data, instead of one model per fold. It all should be ready by the end of this month. Please bear with me.
Cristina


The agent run output parser cause error when run a simple quick start

System Info
Langchain: 0.0.222
OS: Windows 11+WSL Ubuntu22
I run a simple test according to the agent document guide page:
https://python.langchain.com/docs/modules/agents/
I just changed the input a little bit, it throw an error about the output parser.
The code is below:
llm = langchain.chat_models.ChatOpenAI(model_name="gpt-3.5-turbo-16k-0613", temperature=0)
tools = langchain.agents.load_tools(
["serpapi", "llm-math"],
llm=llm
)
agentexecutor = langchain.agents.initialize_agent(
tools=tools,
llm=llm,
agent=langchain.agents.AgentType.CHAT_ZERO_SHOT_REACT_DESCRIPTION
)
results = agentexecutor.run("What is the number that the age of Donald Trump's wife in year of 2020 to power to 3?")
print(results)
=========================
The error is below:
[chain/error] [1:RunTypeEnum.chain:AgentExecutor] [40.48s] Chain run errored with error:
"OutputParserException('Could not parse LLM output: I now know the final answer.')"
The full log file attached here.
agent_bug20230704.log.txt
Who can help?
Agent
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
The code is below:
llm = langchain.chat_models.ChatOpenAI(model_name="gpt-3.5-turbo-16k-0613", temperature=0)
tools = langchain.agents.load_tools(
["serpapi", "llm-math"],
llm=llm
)
agentexecutor = langchain.agents.initialize_agent(
tools=tools,
llm=llm,
agent=langchain.agents.AgentType.CHAT_ZERO_SHOT_REACT_DESCRIPTION
)
results = agentexecutor.run("What is the number that the age of Donald Trump's wife in year of 2020 to power to 3?")
print(results)
=========================
The error is below:
[chain/error] [1:RunTypeEnum.chain:AgentExecutor] [40.48s] Chain run errored with error:
"OutputParserException('Could not parse LLM output: I now know the final answer.')"
Expected behavior
The result should be parsed properly.

I found this article and it helps:
https://python.langchain.com/docs/modules/agents/how_to/handle_parsing_errors


CAN ERROR: Check Connection

I have a 2020 sonata. The normal comma.ai works fine, tried installing this and I get that error. Cables and connections are good. Any advice?

I have a new branch that's on 0.8.7, so it should work for it if stock does. Will be replacing stock_additions branch soon


Unhandled exception when fetching snapshot times out

We are hitting this unhandled exception when fetch times out.
Any chance one of you can help me trace where we are lacking putting catch(() => {})?
@chensixx, I think you fixed one such case, this happens on recent bits in ODSP stress tests.
UnhandledPromiseRejection
Error
at createOdspNetworkError (/app/packages/utils/odsp-doclib-utils/dist/odspErrorUtils.js:123:21)
at Object.throwOdspNetworkError (/app/packages/utils/odsp-doclib-utils/dist/odspErrorUtils.js:161:26)
at /app/packages/drivers/odsp-driver/dist/odspUtils.js:82:33
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Object.fetchAndParseAsJSONHelper (/app/packages/drivers/odsp-driver/dist/odspUtils.js:119:62)
at async EpochTrackerWithRedemption.fetchAndParseAsJSON (/app/packages/drivers/odsp-driver/dist/epochTracker.js:109:30)
at async EpochTrackerWithRedemption.fetchAndParseAsJSON (/app/packages/drivers/odsp-driver/dist/epochTracker.js:268:20)
at async /app/packages/drivers/odsp-driver/dist/fetchSnapshot.js:141:30
at async Function.timedExecAsync (/app/packages/utils/telemetry-utils/dist/logger.js:302:25)
at async OdspDocumentStorageService.fetchSnapshotCore (/app/packages/drivers/odsp-driver/dist/odspDocumentStorageManager.js:419:34)

@chensixx is this bug ready to close now that the above pr is in?

no, we did not find the exception, the unit test was to rule out some scenarios. Jatin said we should add telemetry when unhandled exceptions happen. I will follow up when he is back

#7642 changed to awaiting both promises, and we do not see the error anymore in stress tests. Resolving now.


Server crashing when making the Foliot Crusher

When i craft the foliot crusher, the most basic crusher, the server crashes when the ritual completes.

start ritual
when it completes, server dies

this is in the dw20 1.20.1 mod pack, 1.14.0
occultism is 1.132.1
modonomicon is 1.73.0
crash-2024-06-30_23.43.28-server.txt
believe this is on neoforge.  I think. not sure what that mod pack uses

@Paxination this happens if the wrong version of smartbrainlib for your mod loader is installed.
Your pack is on neoforge, but the smart brain lib version is for forge.
Make sure to place the neoforge version and it will work. This might be an issue in the pack (contact the makers to fix it then) but it could also be a local issue due to curseforge launcher messing up.

Just an FYI I am posting this to ftb github.  and for anyone else, both server and clients need to change to the correct version of smartbrainlib.  fixes the issue as stated.


Added missing character

<description></description> was missing a closing > at the end.

Docs Build status updates of commit de1a2c5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/includes/add-description.md
:white_check_mark:Succeeded
View

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


Emulator Screen Capture

adds a "capture screen" option to the settings in side panel

Thanks for your contribution!


fix xen0/xenu detection: https://projects.puppetlabs.com/issues/10625

@heffergm - super-close.  That breaks a couple of tests.  We can totally fix them up, but if you run rspec spec in facter you can see them yourself.  http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests has the details on what gems, etc, are needed for that.
Thank you for being willing to do that.  Very much appreciated. :)

Will resubmit with test fixes.


extra space before and after user and host

I'm using user and host contexts but i have annoying space characters before and after:
\ user @ host
is it possible to overwrite this behaviour?
my config:
POWERLEVEL9K_LEFT_SUBSEGMENT_SEPARATOR="%F{$(( $DEFAULT_BACKGROUND - 2 ))}@%f"

POWERLEVEL9K_USER_TEMPLATE="%n"
POWERLEVEL9K_USER_DEFAULT_FOREGROUND="green"
#POWERLEVEL9K_USER_DEFAULT_BACKGROUND="gray"

POWERLEVEL9K_HOST_LOCAL_FOREGROUND="red"
#POWERLEVEL9K_HOST_LOCAL_BACKGROUND="gray"

Take a look at the context segment and how to customise it.
The example you mentioned (user@host) would be
POWERLEVEL9K_CONTEXT_TEMPLATE="%n@`hostname -s`"

@lpuglia if you don't really need to use the user and host but still want a different foreground colour you can also use escape sequences, I will add those to my suggestion with context

Thank you for the reply, your solution is a nice work around, here is the style i have now:
POWERLEVEL9K_CONTEXT_TEMPLATE="%F{"green"}%n%F{"white"}@%F{"red"}%m"
but i still have an annoying space character before the left prompt, how can i remove it?

Unfortunately I believe the space between the segments can't be removed with just configuration, maybe @bhilburn can answer this
Even with no segment separator like this
POWERLEVEL9K_LEFT_SEGMENT_SEPARATOR=''
POWERLEVEL9K_RIGHT_SEGMENT_SEPARATOR=''

The segments are still divided with a whitespace

This problem can be solved by setting these both variables:

POWERLEVEL9K_WHITESPACE_BETWEEN_LEFT_SEGMENTS
POWERLEVEL9K_WHITESPACE_BETWEEN_RIGHT_SEGMENTS

Both are set per default to " ". Just define it to "" and it should look like u want.
Just to mention: This will affect all segements on either the left or right side.

what version do you use? it says not found.

Just working on the current master state. U can take a look into the theme-file in line 112 and 202.  A short gaze to both lines in git blame shows, that both have been changed last time over 2 years ago.

For some reasons, I've relogin to my shell, to get the changes work. But that should not cause ur problem that u can't find it.

@lpuglia still an issue or could it be closed?

ok, it sounds like a solution, i still have a problem in ssh session but maybe i will open another issue for that.


Boss.Find fails to find element in iframes

Boss.Find (and other similar methods) that eventually relies on the algorithm in TryFind for a collection of finders fails when looking for an element in an iframe. While the algorithm is designed to search recursively through iframe elements, it fails because the driver is always instructed to switch to the default content on line 57.

LINQ query to reproduce:
Boss.StartChrome(hideCommandWindow: false);
Boss.Url = "http://jsfiddle.net/n5upnvoa/1/";
Boss.Click(".//a[@href='http://www.iana.org/domains/example']");

The JSFiddle page used by the query contains a single iframe element:
<iframe src="https://www.example.com/" width="600" height="240"></iframe>

The content of the www.example.com reads:

Example Domain

This domain is established to be used for illustrative examples in documents. You may use this domain in examples without prior coordination or asking for permission.

More information...

First try against version 2.0.1 on NuGet and it should fail with an InvalidDataException and a message reading:
Could not find elements matching .//a[@href='http://www.iana.org/domains/example']

The stack trace of exception reads:
   at Nito.BrowserBoss.Session.FindElements(ISearchContext context, String searchText)
   at Nito.BrowserBoss.Session.FindElements(String searchText)
   at Nito.BrowserBoss.Session.Click(String searchText)
   at Nito.BrowserBoss.Boss.Click(String searchText)
   at UserQuery
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()`

Then try against a build of PR #6 and it should find and click the link within the iframe.

I’m seeing the same issue and the fix from @atifaziz seems to do the trick. Any chance of this being merged into the code base and a new release issued?

Fixed in v2.0.2.


Pass payload to the rescue handler

In the @next branch, passing the payload to the rescue handler would be helpful for updating database entities with a failure state.

Released as 3.0.0-0 👍🏻
There are no breaking change, but 2.0.0  will be used for an AdonisJS 5 update.


ASP.NET Core Web API using .NET 8 does not service HTTPS requests on ACA

This issue is a: (mark with an x)

[X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Error when sending a request to an endpoint hosted on an ACA container that runs ASP.NET Core on .NET 8.
The same request works properly on .NET 7.
Steps to reproduce

Use Docker to deploy an ASP.NET Core Web API
Use the image "mcr.microsoft.com/dotnet/aspnet:8.0-jammy-chiseled"
Configure a startup/liveness/readiness probe on port 8080 to avoid issues
Deploy the container and confirm it is active
Configure the application ingress endpoint to expose the web api publicly on port 443
Send a request to port 443 over HTTPS to an endpoint exposed by the web api hosted in the container

Expected behavior [What you expected to happen.]
Endpoint responds with 200
Actual behavior [What actually happened.]
An HTTP 503 response with the error message "upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111" is received.
Screenshots
Additional context

I understand port 80 is no longer available. Note that ACA will attempt to use port 80 (as documented here https://learn.microsoft.com/en-us/azure/container-apps/health-probes?tabs=arm-template#default-configuration) if no health probes are explicitly configured. This will result in a failure to deploy the revision.
I've tried adding EXPOSE statements to EXPOSE 8080 and EXPOSE 443 in the docker file; I've also added USER $APP_UID as suggested here https://github.com/microsoft/azure-container-apps/issues/1009 and https://andrewlock.net/exploring-the-dotnet-8-preview-updates-to-docker-images-in-dotnet-8/; this does not resolve the issue either

@limoniapps What's the target port? It needs to match the HTTP port that the process is listening to, which looks like is 8080.

@anthonychu this issue is about HTTPS, in other words port 443

I am having the same issue with a Python Django App in a containerized app in Azure:

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111

I need to restart the service manually. I haven't been able to figure out why it happens, nor have I been able to implement a health check to get the app to reboot automatically.

@anthonychu do you need additional information?

@limoniapps Can you check the target port on the ingress configuration? It should be 8080. You might have it set to 443, according to this:

Configure the application ingress endpoint to expose the web api publicly on port 443

The target port is the port in the container that you want to direct traffic to, not the port that the ingress listens on. The HTTP ingress always listens to HTTPS on 443. Optionally, you can enable insecure requests and it'll listen to HTTP traffic on 80 as well. It will forward requests to your container at the configured target port using HTTP.
I've just deployed this app which should be similar to yours.
Here are the settings on my container app:

Health probes (optional):

@jpruiz114 Can you share your app's configuration, especially the ingress and health probes? It would also be helpful to see your dockerfile and the docker run command that you'd use to run the app locally on your machine. Since you are getting the same error, the problem might be the target port a well. Ensure it's set to the port that your container is listening on.

Hey, @anthonychu, thanks for the follow-up.
My app is a container app using Python and Django. It also uses an SQL Server DB.
Here are the Ingress settings:

Regarding the health probes, I am still determining if I have set those up correctly. My understanding is that they are now called resiliency configurations. Can you confirm this?
If so, here they are:

Here's the Docker file I use in Azure, which is almost the same as I use locally:
FROM python:3.7

WORKDIR /app

RUN apt-get update \
    && apt-get install -y --no-install-recommends \
        curl \
        gcc \
        g++ \
        unixodbc \
        unixodbc-dev \
    && rm -rf /var/lib/apt/lists/* \
    && curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add - \
    && curl https://packages.microsoft.com/config/debian/10/prod.list > /etc/apt/sources.list.d/mssql-release.list \
    && apt-get update \
    && ACCEPT_EULA=Y apt-get install -y msodbcsql17

COPY requirements.txt .

RUN pip install --no-cache-dir -r requirements.txt

COPY . .

EXPOSE 8181

CMD ["sh", "start-and-watch.sh"]

The bash script is something I added recently in hopes to implement a check for the app to restart the service if I found it to be crashed, but that approach didn't work.
#!/bin/bash

process_command="/usr/local/bin/python manage.py runserver <IP_ADDRESS>:8181"
process_ids=$(ps aux | grep -E "$process_command" | grep -v grep | awk '{print $2}')
if [ -n "$process_ids" ]; then
  for pid in $process_ids; do
    echo "Killing process ID: $pid"
    kill -9 "$pid"
  done
else
  echo "No processes with 'manage.py' found."
fi

python manage.py runserver <IP_ADDRESS>:8181

Locally, I would open the app here:
http://localhost:8181/accounts/login/

Hi @anthonychu, I added some details above. Please let me know if these work; thanks in advance.

@jpruiz114 Thanks for the details. Not seeing anything obvious that could be wrong. Can you confirm the status is running in the revision management page? Also check the console and system logs to see if there are any clues that might be causing the container to become unhealthy.

Hey @anthonychu, in effect, the app is running, and unfortunately, the logs haven't been able to indicate much of what is happening.
How can I implement health checks to restart the container if the app crashes? Do you think that would work?
I have suspected that the app is becoming unhealthy sometimes when the database goes to sleep, and since the database may be unavailable just for a fraction of a second, this could be crashing the app, but this is just a hypothesis.
The 111 error seems random.

Hey @anthonychu: I still get this error now and then. Should I look at something to try to remediate it? I expect to have the container app restart itself on failures. Thanks.

@anthonychu this issue is about accessing publicly hosted endpoints using HTTPS, in other words: port 443. The containers we use are configured for HTTP ingress, i.e. the application ingress endpoint is exposed on port 443. This works fine when the docker image is mcr.microsoft.com/dotnet/aspnet:7.0, but fails when using 8.0. Internal access using HTTP on port 8080 works fine since the health probe endpoints, which I have manually configured to access port 8080, are working. However, as I've mentioned above, the behavior of the default startup probe (i.e. the logic used when no explicit startup probe is manually configured) is to test for port 80. It would probably be best if that logic was updated to also fall back to 8080.

@anthonychu this issue is about accessing publicly hosted endpoints using HTTPS, in other words: port 443. The containers we use are configured for HTTP ingress, i.e. the application ingress endpoint is exposed on port 443. This works fine when the docker image is mcr.microsoft.com/dotnet/aspnet:7.0, but fails when using 8.0. Internal access using HTTP on port 8080 works fine since the health probe endpoints, which I have manually configured to access port 8080, are working. However, as I've mentioned above, the behavior of the default startup probe (i.e. the logic used when no explicit startup probe is manually configured) is to test for port 80. It would probably be best if that logic was updated to also fall back to 8080.

Hi limoniapps
I had the same issue after net8 upgrade. What helped was the following:

in docker file expose ports 8080 and 8081
in azure container app deployment set the additional port mapping in the ingress section  443:8081 and the target port to 8080
        "ingress": {        "targetport": 8080,        ....                   "additionalPortMappings": [             {               "external": false,               "targetPort": 443,               "exposedPort": 8081             }           ]    }

Hope this helps :)

@buerklma You should not need to add the additional port. Exposing it this way only allows other container apps in the same Container Apps environment to access it at port 8081, but it does not do anything to the ingress configuration (so it doesn't affect external requests).
To deploy your ASP.NET Core app to Container Apps, you should expose a single HTTP port. By default, the ASP.NET Core base image exposes 8080 and sets ASPNETCORE_URLS=http://+:8080 accordingly. With this configuration, you only need to set the ingress' target port to 8080.
By default, the Container Apps ingress listens only to HTTPS traffic on port 443. Requests are forwarded to your app at the target port, which is 8080. If you enable the Allow insecure setting on the ingress, the ingress will additionally accept HTTP traffic at port 80. It will forward all requests to your app at port 8080.

Hey @anthonychu: I still get this error now and then. Should I look at something to try to remediate it? I expect to have the container app restart itself on failures. Thanks.

@jpruiz114 Sorry I missed this. There's not enough information to figure out what's wrong. Can you check both our console and system logs when this happens? I don't think this is related to the issues the others are having here with ASP.NET Core.

I experienced this exact error message running a brand new .NET 8 Blazor webapp inside Container Apps. At some point i noticed that the log stream stated
  Now listening on: http://[::]:5000
(I had ingress configured on 8080 like discussed above)
Adding ASPNETCORE_URLS with value http://+:8080 as an environment variable for the container made traffic flow.
I was unable to determine why this particular .NET 8 app decided to listen on port 5000 (another I made a few days ago correctly listens on 8080 inside Container Apps with no modifications). But this might serve as a workaround for anyone seeing this error.


Implemented message peeking for determining if a message is available.

Implemented the full_message_available() function which uses the MSG_PEEK flag to determine if a full message has been received without clearing the message.

thanks!, I just fixed the compiler warnings and merged


debounce time

OS
macOS 13.0 (Build 22A380)
LinearMouse
v0.7.7
Is your feature request related to a problem?
No response
Describe the solution you'd like
I don't know wether it is possible to do this within this app but it would be amazing if you added the capability to edit the debounce time of the right/left click
Describe alternatives you've considered
No response
Additional context
No response

Thanks for the feedback. I guess this feature is for those random double-clicking mice where the microswitches wear out?

yes exactly

Could you try this build (built from #362) and see if it works as you expected?

this works great. thank you.


Common test for events

Blocked By
#222 (synthetic event)

Adds common tests for event handling.  Also fixes some minor issues with the common tests.

👻


✨ feat: merge extensions

Codecov Report

Merging #52 (ba39eaf) into main (84606e6) will increase coverage by 0.30%.
The diff coverage is 98.03%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   91.77%   92.08%   +0.30%
==========================================
  Files          23       24       +1
  Lines         815      859      +44
==========================================
+ Hits          748      791      +43
- Misses         67       68       +1

Impacted Files
Coverage Δ

...ftPlantUMLFramework/Internal/SyntaxStructure.swift
96.07% <ø> (ø)

...ramework/Internal/SyntaxStructure+Extensions.swift
96.77% <95.00%> (-3.23%)
:arrow_down:

...lantUMLFramework/Configuration/Configuration.swift
100.00% <100.00%> (ø)

...antUMLFramework/Configuration/ElementOptions.swift
100.00% <100.00%> (ø)

...tUMLFramework/Configuration/ExtensionOptions.swift
100.00% <100.00%> (ø)

...ftPlantUMLFramework/Internal/PlantUMLContext.swift
78.26% <100.00%> (+0.31%)
:arrow_up:

...LFramework/Internal/SyntaxStructure+PlantUML.swift
93.33% <100.00%> (+0.12%)
:arrow_up:

...ources/SwiftPlantUMLFramework/PlantUMLScript.swift
96.07% <100.00%> (+0.16%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Allow to set protected file patterns for files that can not be changed under no conditions

When pattern is set files that match them can not be changed neither using PR, nor push or web editor.
This could be later in other PR probably improved with exceptions to allow changing in PR
Screenshots:

I think those two warns are probably left over from testing.

Yes, for debugging ;)

I know exactly how you feel - some of my debugging log messages have actually managed to get into Gitea proper by mistake...

@lafriks I'm appreciate your changes . Actually I also was looking for something like this. But, my 2 cents is whether locking mechanism (like gitlab has https://docs.gitlab.com/ee/user/project/file_lock.html ) is better or not your implementation?
From business logic the manager need to lock specific files, not by mask. And these files are already exists in repository (master branch?)

@davydov-vyacheslav you can add also specific files using mask. This is a bit different use case as file locking, file locking is more to lock temporary while this is more permanent

Also Gitea supports LFS file locking

Codecov Report

Merging #10806 into master will decrease coverage by 0.04%.
The diff coverage is 9.52%.

@@            Coverage Diff             @@
##           master   #10806      +/-   ##
==========================================
- Coverage   43.56%   43.51%   -0.05%
==========================================
  Files         589      590       +1
  Lines       82691    82797     +106
==========================================
+ Hits        36023    36028       +5
- Misses      42192    42292     +100
- Partials     4476     4477       +1

Impacted Files
Coverage Δ

models/error.go
28.32% <0.00%> (-0.40%)
:arrow_down:

models/migrations/migrations.go
4.16% <ø> (ø)

models/migrations/v132.go
0.00% <0.00%> (ø)

modules/auth/repo_form.go
44.44% <ø> (ø)

modules/repofiles/delete.go
44.51% <0.00%> (-2.43%)
:arrow_down:

modules/repofiles/update.go
38.11% <0.00%> (-0.59%)
:arrow_down:

routers/private/hook.go
32.39% <1.78%> (-4.22%)
:arrow_down:

models/branches.go
41.88% <45.45%> (+0.11%)
:arrow_up:

modules/convert/convert.go
74.92% <100.00%> (+0.07%)
:arrow_up:

routers/api/v1/repo/branch.go
50.09% <100.00%> (+0.36%)
:arrow_up:

... and 8 more

Continue to review full report at Codecov.

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

(As an aside - my persistent warning applies here: we assume that git filenames are utf8 strings - there is no guarantee of this ... the only thing not actually allowed is \0)

Make lgtm work

I think maybe we should allow repo admin to add commit to change protect files. No one can change it is not good idea, do you think so？Thanks.

That could be possibly added as option if needed

The only way that would work would be through a flag that the admin could set and unset as and when they needed to do it. There is no way to warn an admin that they were about to splat a protected file and ask them if they really meant to do that during a git push - you simply do not have interactivity like that.

Another suggestion about this feature. maybe we should also check whether it changed protected files when making a pr to protected branch, if have. should block it to be merge.  similar to checking whether have conflicting files


azurehound: init at 2.2.1

Azure Data Exporter for BloodHound
https://github.com/SpecterOps/AzureHound
Related https://github.com/NixOS/nixpkgs/issues/81418

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
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.

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

x86_64-linux

:white_check_mark: 1 package built:

azurehound


Upgrade Docker image's Golang to 1.8.1

fixes intermittent STREAM/Protocol errors
probably HTTP/2-related
change default tag v2 -> v6 (gift to future self)
don't install PostgreSQL; it doesn't work

fixes:
E: Package 'postgresql-9.3' has no installation candidate
E: Unable to locate package postgresql-client-9.3
E: Couldn't find any package by regex 'postgresql-client-9.3'

fixes #185

LGTM! can you merge/update the pipeline?

The pipeline should automatically pull in the changes the next run (i.e., we haven't updated the pipeline.yml, only the the tasks' .yml files).

Great point, thanks :)


Captialisation validation should be off by default as not a standard or best practice

Capitalisation of filenames by default sets an error if PascalCase is not used.
This is not a standard or best practice (never seen pascalcase used anywhere in cfml in 20 years of coding to be honest.
As this format is a preference and should be only set in configuration, not as default. this is a bug.

That does not not trigger an Error; that issue is set to Info.
Regarding whether it's a standard or best practice, the conventions I see most often are borrowed from Java, which does use PascalCase for class names. For example, here is the Ortus standard -- Class/Component/Interface Names.
Regarding configuration, you can ignore or configure the rules as you see fit using the .cflintrc file. See the README for how this can be done. Also, see the RULES for the names and defaults. The value you are referencing is ComponentNameChecker.case.

I still think this info should be OFF by default, but configurable ON by config as it's not a cf standard. My 2c, but can use alt file for now.
Using through VS code... thanks for your work on this! #niceone

I have no issue with an opt-in model, which has come up in other issues before, but I don't believe there is currently a mechanism in place to allow for this.
To be clear on this rule in particular, you are correct that using a particular case anywhere is not an official CFML standard. However, having a naming convention and being consistent with it is a best practice, and that's what this rule enforces. PascalCase is simply the default for ComponentNameChecker, but it is easily changeable and I don't feel there is any harm in having all configurable rules with some default. CFLint is opinionated.


Add HED warning for incompatible column/column value names

Some of the JSON libraries for MATLAB and OCTAVE have limitations about the supported key names:
According to bids-standard/bids-starter-kit#262 these are the requirements for some libraries:

start with a letter, otherwise assigning to that field will error
contain only letters, numbers, and/or the underscore character, otherwise
assigning to that field will error, and
must be no longer than namelengthmax (currently 63) characters, otherwise
you will receive a warning and the field name will be truncated

We should add a HED Warning for incompatible key names for column names and also for column values in categorical columns of
events files, which are also keys.

I think we will have to rely on BIDS to decide about this.


Correct the text. "搜素" => "搜索"

Hi @elegance, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@lukaschal please send following strings to fix the typo in preferencesWidgets.nls.resx.lcl

Search default settings

搜素默认设置

Search Default Settings

搜素默认设置

Waiting for linguistic input.

Fixed as suggested.
File: src\vs\workbench\parts\preferences\browser\preferencesWidgets.nls.resx
ID: ".resx", 0; "SearchSettingsWidget.AriaLabel"
SRC: Search default settings
TGT: 搜索默认设置


fix!: adapt to breaking upstream changes

Problem: The "trick" of wrapping an anonymous node into a single choice or seq no longer works as of https://github.com/tree-sitter/tree-sitter/pull/2577  since the wrapped anonymous nodes are no longer exposed to queries.
Solution: Drop unnecessary choice and skip and use named nodes in queries instead (anonymous nodes are no longer exposed).
@amaanq

Thanks! Do I need to propagate these query changes to nvim-treesitter?

No, thank you, I can handle this myself (since I know what changes are needed)!

Ah, I guess I missed some hidden queries ;)

Ran our query formatter on the nvim queries, as a treat ;)


Cannot use extended batch shape with channel_first Conv2D

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.12
Custom Code
Yes
OS Platform and Distribution
Ubuntu 1804
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Given input tensor for shape, say [batch_dim_1 = 4, batch_dim_2 = 5, channels = 6, Height = 7, Width = 8] to a channels_first (keras) Conv2D of stride 2, the "_get_sequence" function at Line 1288 in nn_ops.py sets strides to [1, 2, 2, 1], which is wrong. Strides should be [1, 1, 2, 2] for the input tensor will be reshaped to [batch_dim_1 * batch_dim_2, channels, Height, Width] later in squeeze_batch_dim in nn_ops.py.

Standalone code to reproduce the issue
As described above.

Relevant log output
No response

@Yang-Yuan Thanks for reporting an issue!
Could you please elaborate the issue here by stating the example if you are using any. Thank you!


RunAsTI as a virus?

windows defender detected me as a virus from RunAsTI tho.
Proofs:
https://github.com/jschicht/RunAsTI/issues/9
https://github.com/gerardog/gsudo/issues/49

That's definitely a false positive. You may need to add the directory to it on the whitelist in your antivirus program.

yea

but how

ok  but thanks


Update README of azure-identity-providers-jdbc-[mysql/postgresql] libraries

Make some improvements:

Update README of azure-identity-providers-jdbc-mysql
Update README of azure-identity-providers-jdbc-postgresql

Docs
azure-storage-blob
azure-identity.

@stliu Could you help review this PR?

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-identity-providers-core

@backwind1233, I have to change the target branch so I force-pushed to your PR. Please do not pull directly.

do we need a README in sdk/jdbc folder as https://github.com/backwind1233/azure-sdk-for-java/tree/update-jdbc-readme/sdk/keyvault ?

Closing this PR, redirect to https://github.com/Azure/azure-sdk-for-java/pull/31380.


docs: fix typo in "Live reload with other tools"

This PR fixes typo on page https://templ.guide/commands-and-tools/live-reload-with-other-tools/#reload-event: build.bin instead of build.cmd in "Note" block.

Ah, thanks for that! Nice spot!


Missing documentation on all API methods

Problem
Document DockerCli Cmd... method
Solution
Write godoc-style docstrings for each Cmd... method(which cli command it represents, maybe something about parameters) in api/client/commands.go.

#dibs


Update setup.py

@MehulAgarwal07 thanks for the contribution, we are looking for meaningful contributions. Please see GitHub issues and let us know if we can be helpful.


Doesn't seem to work with Laravel Websockets self hosted pusher

I have been commenting on many issues and no one is responding.
I am not able to get this to work. While i was using an older deprecated package called flutter_pusher_client which is very similar in syntax it is working flawlessly.
What seems to be the problem with this package and laravel self hosted pusher option?
Does anyone have a working sample with the same stack as me?
Thanks.

@apostle51  you can write to me if you need help. I migrated to this plugin
https://github.com/olubunmitosin/laravel_flutter_pusher
and it was a BREEZE! Stop using this one.

@apostle51 you can write to me if you need help. I migrated to this plugin
https://github.com/olubunmitosin/laravel_flutter_pusher
and it was a BREEZE! Stop using this one.

didn't work for me using laravel websockets and laravel passport
are you still using same code or other solution?

Yes. Works like a charm.

Yes. Works like a charm.

Would you give me a link of your code or some parts of it Flutter code and Laravel code
I will be thankful to you

Ok sure contact me on skype nzein19

Ok sure contact me on skype nzein19

I did thank you

Seems perfect. You most likely have an issue on the laravel side then. BTW, i'm using an older version of laravel and passport because i haven't had time to update. What are you using?

Also, what error do you get in websockets when you try connecting?

Also, what error do you get in websockets when you try connecting?

if you mean Laravel websockets Dashboard it's working

You should move your issue to the flutter package, it is creating noise here for now reason. You get an error message in flutter and that should be your starting point. Reproduce the print statements i sent you in my sample code. We can do a zoom session tonight, i can spare an hour.

I can't at night, i have day only nowadays, i'll search it tomorrow and update you here.

@nicolasvahidzein  would i comment on the issue https://github.com/olubunmitosin/laravel_flutter_pusher/issues/7 to close this one.
after a lot of searches i found that it's an Null safety issue that appears in lot of packages
so can i know what versions of packages you use in the code you have sent to me?
mine is like follow
laravel_echo: ^1.0.0-beta.1
laravel_flutter_pusher: ^0.0.4

You are using a more recent version of laravel, i'm still on 5.8. Send me your laravel echo and websockets versions you are using on the backend.

You are using a more recent version of laravel, i'm still on 5.8. Send me your laravel echo and websockets versions you are using on the backend.

, i don't have my pc right now but they are the Latest versions


Fixes strict and non-strict threshold recurrence.

Fixes strict and non-strict threshold recurrence as requested in #611

And again with adjusted test cases. Exemplary 😍


Merge changes from Sugarizer's web library

Part of #127 .
As per title, this pull request merges changes from Sugarizer's web library back to this repository.
Currently, running volo add -f from a Sugarizer activity causes it to pull sugar-web from this repository. However, this library is outdated and doesn't work with Sugarizer activities.
The changes accomplish the following:

Works with Sugarizer activities.
When running on Sugar Desktop, works similarly to the current repository. This is done with minimal changes, by using env.isSugarizer() to run different branches of code on the different platforms. In other words, the library is still essentially the same when running on Sugar Desktop.

What doesn't work:

Sugarizer activities still will NOT work on Sugar Desktop with this library.
grunt test is broken.

Most of the code written is by @llaske, with some fixes made by me during the porting.
The changes made are fairly extensive, and difficult to compare due to some files being moved around, particularly for  datastore and bus. This is quite a major upheaval to this library, and I hope to get feedback from you guys.

@cheongsiuhong can you share your test methods?

I manually ran every Sugarizer activity with their default sugar-web, and this one. I noted no changes in behavior, though admittedly this is not the most thorough way to test.

I manually ran every Sugarizer activity with their default sugar-web, and this one.

I'm guessing you ran them in sugar, if that's the case; how did you run it?

I manually ran every Sugarizer activity with their default sugar-web, and this one.

I'm guessing you ran them in sugar, if that's the case; how did you run it?

The Sugarizer activities were tested in Sugarizer.
If you're asking how to run Sugarizer activities in Sugar, you can run python setup.py dev via the terminal. The corresponding activity should show up in Sugar desktop. Most of them don't work though, as mentioned.

The Sugarizer activities were tested in Sugarizer.

Any changes made in sugar-web has to be tested with a web activity in sugar, a git search will show you the sugar-web activities.
The changes can't be tested on sugarizer activities in sugarizer as it's an update for sugar-web which is also used by sugar activities in sugar.
You can read more at the issue you referenced.

Nice work.  Just need some way to test that everything is working in Sugar before we merge it.  Is there a test method?  Is it as simple as replacing the directory in an already working Sugar activity?

Unfortunately, there are a fair number of issues that make this pull request somewhat hard to test properly.
The Karma tests don't work, probably due to the dependency being very outdated. As the purpose of this patch was solely to port changes over from Sugarizer, I avoided changing any dependencies.
Secondly, the Sugar web activities that are currently on the sugarlabs GitHub mostly use an outdated version of this library. It took some time, but I tested all of the activities here with this updated version of sugar-web. The Moon activity is the only one that uses a somewhat up to date sugar-web library, and it works with no issue when I replaced it with the updated one.
It is unclear if the problems lie with this patch, or with the outdated activities that may not be have been written to work with the current version (meaning unpatched) of sugar-web. It would take quite abit of time to debug and fix them all, if that were the case...
Hope to hear some guidance on this issue.

The challenges you've faced are expected, some problems might lie with the patch and some problems might not, you'll have to figure out which problems are which and try fixing them as you go along.
In the case of some activites index.html calling sugar.css and not the current sugar200dpi.css, that's a case of the patch not being the problem and you can easily fix that by referencing sugar200dpi.css and not sugar.css.

Thanks @cheongsiuhong and @chimosky.
I urge caution in using Moon as an example, because I made that release without much experience, and also how it can be used to induce a specific failure in the journal interaction.
Yes, the GitHub Sugarlabs repositories are outdated, because (a) we have had no JavaScript maintainers for Sugar, and (b) maintainers for Sugarizer have forked the source code into the Sugarizer repository.  (Which has reminded me to pull from @llaske and push to @sugarlabs following the most recent release - done).
Sugar web has been under maintained.  There is a 0.100 branch, a 0.102 branch, and then a v0.110.0 tag but no later.  Sugar is at 0.117 now.
Guidance;

select a Sugar web version for the next release, e.g. 0.118,
select some simple Sugar web activities, such as Hello World, and one or two others, chosen for their use of the API,
for each change to the API proposed by this pull request, make those changes also to the selected activities,
assess the changes that were required and write a "Port to Sugar web 0.118" guide for sugar-docs.

If you agree on this plan, then I suggest it be posted on sugar-devel@ mailing list, because the audience for this repository is limited.

@quozl I suggest also to update file one by one instead of updating all files at the same time.
For example, update first env library, then bus library, then datastore ibrary, ...
When I've forked sugar-web I've isolated the initial source code an create sub directories for each file with the Sugarizer code in a sugarizer.js file and Sugar code in a sugaros.js code. In the initial file name, there is only the code to switch between Sugar/Sugarizer.
For example, here is the code in the bus.js file it's just a switch between sugaros
define(["sugar-web/env", "sugar-web/bus/sugarizer", "sugar-web/bus/sugaros"], function(env, sugarizer, sugaros) {
    'use strict';

    var bus;
    if (env.isSugarizer()) {
        bus = sugarizer;
    } else {
        bus = sugaros;
    }
    return bus;
});

Following this logic, it should be easier to update Sugar-Web.

Thanks @llaske!  Yes, that seems like it would be an effective way to iterate.

Thanks all for the feedback.

Guidance;

select a Sugar web version for the next release, e.g. 0.118,
select some simple Sugar web activities, such as Hello World, and one or two others, chosen for their use of the API,
for each change to the API proposed by this pull request, make those changes also to the selected activities,
assess the changes that were required and write a "Port to Sugar web 0.118" guide for sugar-docs.

Currently, I think I'd work on the above steps. I agree with @llaske that pushing incrementally would make the updates easier to review, but it may be quite challenging to test the functionality of each iteration.
It would then require something like:

Update a batch of files, eg datastore.js or env.js, and activity.js if needed.
Test if some activities work, otherwise update them.
Repeat 1 and 2 until fully updated.
Release updated Sugar-web with porting tutorial.

Would this be a suitable workflow?

Thanks.  That workflow seems fine to me.  Another would be to add a test activity inside sugar-web or somewhere else that can serve as a worked example and test for the API.  Like Hello World but using all API features.

For work on incrementally updating sugar-web, I will open different pull requests for each separate file change.
Closed this for now.


python310Packages.pyswitchbot: 0.37.5 -> 0.37.6

Diff: https://github.com/Danielhiversen/pySwitchbot/compare/refs/tags/0.37.5...0.37.6
Changelog: https://github.com/Danielhiversen/pySwitchbot/releases/tag/0.37.6
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 225215 run on x86_64-linux 1

8 packages built:

home-assistant-component-tests.bluetooth
home-assistant-component-tests.mopeka
home-assistant-component-tests.shelly
home-assistant-component-tests.switchbot
python310Packages.pyswitchbot
python310Packages.pyswitchbot.dist
python311Packages.pyswitchbot
python311Packages.pyswitchbot.dist


Dashboard shows incorrect OS Version

Azure Data Studio Version: master

Steps to Reproduce:

Open Server Dashboard

Expected - OS Version of the server in details
Actual - Lots of extra details. Screenshot attached -

Closing as duplicate of https://github.com/Microsoft/azuredatastudio/issues/2793


Some changes to reflect Rust 1.4 update

Version 1.4 of Rust just came out today, and there are a few changes that affect the driver. First, the use of Self as a type in a trait now produces a warning if the trait does not also implement Sized. Additionally, the .expect() method (essentially unwrap() with a custom error message) has been added to Result, so there's no need to convert them to Option using .ok() beforehand.
Since the change with .expect() would not work on earlier versions of the compiler, it might make sense to put these changes in a separate 1.4 branch rather than merging with 1.0, which would make them available for people who opt to use newer version of Rust.

@saghm not quite sure how this would work with releasing this to crates - we can only have one "v0.1.1" on crates as far as I know. It might be worthwhile to merge this into master and just remove support for rust <= 1.3, since there isn't much reason to not upgrade to 1.4 and these changes are just in tests. What do you think?

Sounds good, although I'd suggest that we release it as 0.2.0 rather than 0.1.1. Cargo will by default use the highest release available (i.e. if you ask for 0.1.0 and 0.1.1 is available, it'll give you 0.1.1), so we might as well preserve the option of using 0.1.0 with older versions of Rust.

As far as I understand it, the driver with this PR will still work on Rust 1.0, just the tests won't work. Is that correct?

Yeah, the only changes made in the src/ directory are the documentation tests, so none of the actual driver implementation is changed.


allow appveyor python3+ builds to fail

Added a small section to appveyor config file to allow the python3 windows builds to fail without warning of build failure. I'll look deeper into the windows issues to see if I can get the tests passing and then add the [windows] build extra. If I can I'll revert the config back.

thanks!


Add typescript types

create a @types/fluent-schema

We prefer to ship them in the project, it’s kind of better for compatibility reason.

Cool, I was looking in the fastify project and I noticed that. However, thanks for the heads-up :)


Manual compound annotation pane

Can be used to manually define a compound. The annotation is stored as a compound annotation. If this method is used, the "DatabaseNameType" is set to "Annotated by user xy"
Invalid:

Valid:

Looks cool, but why not add a field for adduct/ion notation and calculate precursor based on formula and adduct?

Adduct information is in there already, i fixed that after the screenshot. see commit display adduct type
Calculation of precursor mz is not done, it's currently used the other way around to calculate neutral mass from adduct and precursor mz. can add that though, i think.

Great, thanks for adding the mz calculation

Great. Thanks for the last change to make it more robust.


Top-1 Loc, Top-5 Loc and backbone( DenseNet161 and EfﬁcientNet-B7 )

Hello! First of all, you did a great job! Congratulations! Second, I have three questions I'd like to ask you about running the code.

First, in the case of WSOL, I didn't find the test file test.py in the code. Is the result on the CUB-200-2011 test set and imagenet-1k validation set mentioned in this paper calculated by def test in train_ccam_cub. py?

Secondly, the three evaluation Top-1 Loc, Top-5 Loc mentioned in the paper were not found in the code to calculate Top-1 Loc and Top-5 Loc, so there was no Top-1 Loc and Top-5 Loc in the running result of my CUB-200-2011 dataset. How to solve this problem?

Thirdly, the C2AM(Ours) in Table1 uses backbone DenseNet161 and Efﬁcientnet-B7. I did not find the part of the code downloading and replacing these two backbone networks in the code, so that the results in C2AM(Ours) in Table1 could not be reproduced. How to solve this problem?

Hi,

This repository only provide the training code for CCAM (train_CCAM_CUB. py/train_CCAM_ILSVRC. py and test codes were included in them)
After training of CCAM, you can extract class-agnostic bouding boxes from CCAM and re-train a regressor using these pseudo bboxes. Please refer to sec 3.4. in our paper.
You can adopt DenseNet as the backbone for localization and efficientnet for classification (just following other works' setting like PSOL). Code was provided at here. I will try my best to open my code in this repository for re-training.
Btw, the simplest method to get top-1 loc and top-5 loc is to directly combine class-agnostic bboxes estimated from CCAM and classification from a classifer. Code for top-1 and top-5 loc you can refer to my another repository https://github.com/Sierkinhane/ORNet/blob/59e8ef5e461a5b00ca8c94d9fa0f5e58df193774/train_2nd_step.py#L225

Thanks for your reply! I would like to confirm the following questions with you again. For the second question, I need to manually add the top-1 and top-5 code to the source code, right? For the third question, I need to refer to PSOL to modify and add the source code to re-train and achieve the following result reproduction, right?

I really appreciate your work, hope you can open your re-training code in this repository, and I have strat for your work!

Exactly.

For convenience, I will try to clean and upload my codes in the coming weeks!

Ok, thank you very much for your reply!

Hello, I just clean and upload the code to train a regressor using the extracted bboxes. Please check that and feel free to ask any questions!

Hello, I just clean and upload the code to train a regressor using the extracted bboxes. Please check that and feel free to ask any questions!

Hello, I would like to know the configuration of your WSOL and WSSS experiments, as well as the epochs when training WSOL on CUB_200_2011 dataset and WSSS on VOC2012.

Hello, default configurations can be found in xxx.yaml or arguments in the code.

Sorry, after running the three steps of the PY file according to README in WSSS, the background clue I get is like this, I can't see the outline of the target at all, it is almost completely black. But I follow the README operation, only changed the path of the dataset and the name of the model, I don't know what is wrong?😭
Please help me!😭

Have you loaded the pretrained moco or detco?

When runing the experiments, you can observe the generated activation map in experiments/images/.
├── experiments/
|   ├── checkpoints
|   ├—— images

Hello, default configurations can be found in xxx.yaml or arguments in the code.

Hello, I see that the loss value of ten epochs is still decreasing. Should we increase the training epoch? As for the background clue being all black, I may need some more time to experiment.

I just run the code and it is no problem in my experiments. How about your configurations? Is same with this repository?

Please ensure the batch size is larger than 32.

Btw, the simplest method to get top-1 loc and top-5 loc is to directly combine class-agnostic bboxes estimated from CCAM and classification from a classifer. Code for top-1 and top-5 loc you can refer to my another repository https://github.com/Sierkinhane/ORNet/blob/59e8ef5e461a5b00ca8c94d9fa0f5e58df193774/train_2nd_step.py#L225
Hello,I'm confused about how to calculate top-1 loc and top-5 loc on top of  class-agnostic maps since class label is unknown, could you explained classifer in detail?For example,whether the classifer is directly bulit on the class-agnostic maps? And whether the classifier needs to be supervised?

Hi, just combine the bbox with a classification result. We provide details in method section.


Merge branch 'master' into 0.2

Coverage remained the same at 7.43% when pulling a7878195182124c44815ca623a402de9f7ca2bb3 on master into b6c98ca4f89efd7e9798c3a213e137ac0db96421 on 0.2.

Coverage remained the same at 7.43% when pulling a7878195182124c44815ca623a402de9f7ca2bb3 on master into b6c98ca4f89efd7e9798c3a213e137ac0db96421 on 0.2.


Fix --filename with single file searches

Previously if you passed the --filename argument when searching a single
file, the value of print_path would be overwritten. This adds a new
PATH_PRINT_FORCED option for when users specifically pass --filename
(versus it being set by the default) so that it will not get
overwritten. I've also added a test to cover this case
Fixes https://github.com/ggreer/the_silver_searcher/issues/972

@ggreer this one should be ready if you have some time to take a look 🙏

@ggreer this one should be ready if you have some time to take a look 🙏

Rebased

@ggreer can you take a look at this small one?

I don't want this in my github.com/pulls list anymore so I'm going to close it


No "Applies To"

does not tell us what licenses are needed at a Tenant to be able to apply these settings
[Enter feedback here]

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

ID: fb0c964d-2d1b-601a-c8a2-14378fc24fb8
Version Independent ID: ee549bd1-0652-2167-0f23-d22a58cf895b
Content: Learn about sensitivity labels - Microsoft Purview
Content Source: microsoft-365/compliance/sensitivity-labels.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@sarahmcm  There is no blanket "Applies to" for sensitivity labels - licensing depends on the scenario, so it's a bit more complicated. At the top of this page, and all pages for sensitivity labels, there's a link to the licensing page that has the relevant details and the "Get started with sensitivity labels" page has a section specifically for licensing: https://docs.microsoft.com/en-us/microsoft-365/compliance/get-started-with-sensitivity-labels#subscription-and-licensing-requirements-for-sensitivity-labels

great tx - now please go shoot the lawyers who made it so bloody complicated
ngā mihi
Sarah McM
@.***http://www.gtb.co.nz/
Sarah McMurray
Senior Tech, Director
04 297 1040 ext 704   |<PHONE_NUMBER>
GTB IT Solutionshttp://www.gtb.co.nz/
Quality Work  |  Care for People  |  Ongoing improvement  | since 1999
Information where you need it, when you need it - safe and secure
Get our ebook ‘Type Macrons Easily – How to install a Māori keyboard’https://gtb.co.nz/assets/ebooks/Type-Macrons-Easily---How-to-install-a-Maori-Keyboard---GTB.pdf
Watch our 4 minute video to see how to spot and keep safe from dangerous emailshttps://youtu.be/hTAfvuNEPKI
From: Carol Bailey @.>
Sent: Thursday, 28 April 2022 2:43 AM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Sarah McMurray @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] No "Applies To" (Issue #8425)
@sarahmcmhttps://github.com/sarahmcm There is no blanket "Applies to" for sensitivity labels - licensing depends on the scenario, so it's a bit more complicated. At the top of this page, and all pages for sensitivity labels, there's a link to the licensing page that has the relevant details and the "Get started with sensitivity labels" page has a section specifically for licensing: https://docs.microsoft.com/en-us/microsoft-365/compliance/get-started-with-sensitivity-labels#subscription-and-licensing-requirements-for-sensitivity-labels
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8425#issuecomment-1111089662, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARKYCXDX6MXTQMUB2R6443LVHFG5RANCNFSM5UN2B75A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

if it is not clear “how to buy” then how are people supposed to buy this service?
cheers
From: Carol Bailey @.>
Sent: Thursday, 28 April 2022 2:43 AM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Sarah McMurray @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] No "Applies To" (Issue #8425)
@sarahmcmhttps://github.com/sarahmcm There is no blanket "Applies to" for sensitivity labels - licensing depends on the scenario, so it's a bit more complicated. At the top of this page, and all pages for sensitivity labels, there's a link to the licensing page that has the relevant details and the "Get started with sensitivity labels" page has a section specifically for licensing: https://docs.microsoft.com/en-us/microsoft-365/compliance/get-started-with-sensitivity-labels#subscription-and-licensing-requirements-for-sensitivity-labels
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/8425#issuecomment-1111089662, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARKYCXDX6MXTQMUB2R6443LVHFG5RANCNFSM5UN2B75A.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@sarahmcm  I agree the licensing for sensitivity labels isn't simple, which is why an "Applies to" wouldn't work for this page and instead, we link to the relevant information that's owned and maintained by the team who are responsible for this area of the product. For feedback about the licensing itself, I recommend you use GitHub Issues on that licensing page itself or use the "This product" button in the Feedback section.  That way, the relevant people will see it.
Closing this documentation issue.


remove codecov

We are testing the imports, but codecov isn't designed to see this.
In this case, codecov is more annoying than helpful. I think we should remove it from the meta package unless someone can figure out a way to make it more useful.

cant see that coverage is a useful stat for the metapackage. I say we toss it

cant see that coverage is a useful stat for the metapackage. I say we toss it

Do we want to simply turn off CodeCov or remove completely?

Turning off can be done like this.
Removing altogether is a bit more involved:

[ ] remove integration (Settings->Intergrations->Configure->Repository access->X)
[ ] remove codecov.yml
[ ] remove from requirements, and environments (including ci/*)
[ ] remove action from unittests.yml
[ ] other?

Do we want to simply turn off CodeCov or remove completely?

Turning off can be done like this.
Removing altogether is a bit more involved:

[ ] remove integration (Settings->Intergrations->Configure->Repository access->X)
[ ] remove codecov.yml
[ ] remove from requirements, and environments (including ci/*)
[ ] remove action from unittests.yml
[ ] other?

Turning off makes sense to me.

Turning off makes sense to me.

This will have to done by someone with full admin privileges.

This will have to done by someone with full admin privileges.

i deselected pysal on the repos in our organization account that codecov reports. I'm assuming that takes care of it?

i deselected pysal on the repos in our organization account that codecov reports. I'm assuming that takes care of it?

I would think so. Let's try a toy PR to check?

I would think so. Let's try a toy PR to check?

https://github.com/pysal/pysal/pull/1206

https://github.com/pysal/pysal/pull/1206

resolved in #1207

resolved in #1207


[SECURESIGN-663] Add option to set an external ctlog service

Please run make generate manifest bundle command to generate all manifests and bundle metadata

/lgtm


ENH: updating remote modules to latest versions

Can anyone review/merge? It is ready to go.

I am missing extra information about the changes in the remove modules.
Can we provide a shortlog of the changes between SHA's?
For example for BioCells:
git shortlog --no-merges 47a233..1d394ab | cat                                                                15:08:52 
Mathew Seng (1):
      BUG: Fix failing tests for examples Replaced ITKIONRRD with ITKIOPNG and ITKIOMeta, because the examples were trying to build the png and mha images as nrrd, thus throwing an error

We would need to update the update script to include short logs, otherwise updating will become a chore.


fix order warnings

DEPRECATION WARNING: Dangerous query method (method whose arguments are
used as raw SQL) called with non-attribute argument(s): "lower(name)".
Non-attribute arguments will be disallowed in Rails 6.0.
This method should not be called with user-provided values,
such as request parameters or model attributes.
Known-safe values can be passed by wrapping them in Arel.sql().

These deprecation warnings display in rails 5.2
These fixes work in 5.1

@miq-bot add_label jansa/yes?

Jansa backport details:
$ git log -1
commit dc66de3810639030dc5fc9e21d83c1249076d472
Author: Joe Rafaniello<EMAIL_ADDRESS>Date:   Thu Apr 2 13:47:30 2020 -0400

    Merge pull request #20036 from kbrock/unsafe_queries

    fix order warnings

    (cherry picked from commit 7fc11c687b456aac779f65a50d4805db7f80216c)


gltfpack: Add simplification options

This change adds two new command-line arguments, -si R (to specify the simplification ratio) and -sa (to enable aggressive simplification). Each mesh in the output is simplified to the given ratio; when aggressive simplification is enabled, the target ratio is reached disregarding change in appearance.
Supporting this for point cloud meshes required a new algorithm, meshopt_simplifyPoints; this uses a variant of sloppy simplifier with the quadric error based on distances to points. This is an experimental addition and will probably need to be refined (in particular, attribute error is pretty important for point clouds).
In the future the aggressive mode can be refined a bit further by trying to simplify the mesh with the default simplifier on a subset of attributes in some cases (e.g. trying to preserve UV seams but ignoring normal/tangent seams, which can maintain appearance a bit better compared to the sloppy simplifier).
Fixes #60.

Source:

After ./gltfpack -si 0.4:


Use ArrayFields, instead of creating more references

The current implementation of VulnerabilityReference , forces us to have only one reference_id and url which is inconvenient because consider : for vulneraiblity 'a' there are 'n'  reference_id and 'm' url , hence  to have all combinations of reference_id and url we need to create n*m VulnerabilityReference. This results in more db queries+ data duplication.
This can be simply solved by using ArrayField

Turns out this was not the problem. https://github.com/nexB/vulnerablecode/pull/216#issuecomment-653778007 and https://github.com/nexB/vulnerablecode/issues/223 for details


[NFC] Register tiling implementation for tensor dialect in IREE.

It forces the CPUDoubleTilingPadExpert pipeline explicitly set anchor op. Otherwise, the CodgenStrategy could tile on pad op, which is not expected. In the past, it would not tile pad op because the tiling implementation was not registered. This is an NFC to the CPU pipeline.

It is triggering some issues in experimental path (like fusing pad with its consumers). I looked into the IR dump. It unconditionally (or say greedily) tile and fuse pad into its consumer. But we probably don't want it or need some control on it. After talking to @MaheshRavishankar, I think it is part of pad fusion work. So I'm not going to push this PR forward.
(cc @ThomasRaoux @grypp )


Palette entries should have keyboard equivalents

Several palette entries should have keyboard equivalents.
Any keyboard equivalents should have a tooltip and/or aria label to indicate the keyboard equivalent.

Mostly fixed with https://github.com/benetech/MathEditor/commit/ee27672915126d02414f9d742ab4a132411d9169


Add MultiTenant.without

Issue #44
Helpful in tests and corner cases when cross-tenant queries are needed within a context where a tenant is already set.

@jaxn Nice, thats a great idea!


Booting new installation fails

Issue description
I got a new SSD for my Thinkpad X220 and installed it from the previous setup (nixos unstable).
It fails booting, it either drops into emergency mode - (I don't know why, but I guess because of https://github.com/NixOS/nixpkgs/issues/20353) - or it hangs during boot with the same message as when it drops into emergency mode:

I'm at loss right now because I fail to see what went wrong here.
Details which might be important:

/dev/sda1 is fat32 and should be mounted in /boot
/dev/sda2 is luks encrypted ext4 and should be mounted in / (decrypting during boot works)
No other partitions

In generation 3 (which fails into emergency mode), /boot does not get mounted properly. This should be fixed in generation 11, but when booting 11, it results in what you see in the image.
I'd provide more information if needed, of course.

Just a thought, but maybe use a minimal linux iso to chroot into the partition. SOmething like Archlinux, it gives you arch-chroot which will mount /proc and other things to feel as if you are using an installed Linux, in a way. Go in and check /etc/fstab ?
Also I havent tried it, I wonder if you could mount the partition with a nixos usb and chroot into it and edit the configuration file and do a rebuild?

Yes, boot from a NixOS install medium and use nixos-install --chroot.

If I boot into generation 3, I actually can log in. I can then nixos-rebuild switch to get to generation 11 and log in there as normal user.
Also, my configuration.nix was copied from the old drive and should work as intended, I guess. So... I see no point in booting an arch or something. @fpletz not sure what the nixos-install --chroot command gives me in my situation?

@matthiasbeyer did the uuid of your partition change? ls -la /dev/disk/by-uuid
These should match with your device attributes in hardware-configuration.nix:
  fileSystems."/boot" =
    { device = "/dev/disk/by-uuid/A767-904A"; # <-- might have change after disk upgrade
      fsType = "vfat";
    };

I refer to the partitions by /dev/sda1 and /dev/sda2.

Then check which service has failed by using journalctl -xb in the rescue console.

To get a bootable systems, you can also opt out partitions as a temporary work around.
  fileSystems."/boot" =
    { device = "/dev/disk/by-uuid/A767-904A";
      fsType = "vfat";
      options = ["nofail"];
    };

When booting into generation 3 (11 does not boot to a login prompt, as the image above shows), I see the following: A disk cannot be mounted by UUID (this is because generation 3 is before I moved to use /dev/sda1 and so on).
It also tells me:
systemd[743]: emergency.service: Failed at step EXEC spawning /run/current-system/sw/bin/plymouth: No such file or directory

(I typed the above by hand from the screen, typos may be there)
I don't know why generation 11 fails...

Ok, the nofail suggestion worked, I was able to boot into generation 12 which worked as expected now.
But, I do not understand why /boot couldn't be mounted. I checked the logs and it complained that /boot was not empty... but it mounted anyways (which simply fails then).
Can I just delete the files in /boot and try to boot?

If you delete boot you will delete the kernel and not be able to boot again at all. With standard Linux you could after you booted and then install the kernel and run mkinitcpio but I am unsure with Nixos

@ndowens nope, read again: The /boot directory is not empty with /dev/sda1 not mounted! That's why I'm asking: While booting, it tells me that /boot is not empty, but mounts /dev/sda1 anyways on it.
I don't know whether this is the error or not, that's why I'm asking whether deleting the contents would yield anything. I cannot see why else it would fail to mount it. On the other hand, it shouldn't matter whether there are things in the directory or not... at least this is what the error message tells me.

Okay this is funny now: as I wrote above, I managed to boot with the nofail option suggested by @Mic92 . I then mounted /dev/sda1 manually to /boot and nixos-rebuild switched. Now, everything just works.
I guess I will close this therefor.

@matthiasbeyer To this point I thought only zfs refuses to mount a partition onto a non-empty directory.
You can do the following (while your actual boot partition is not mounted).
$ mv /boot/ /boot-backup
$ mount /dev/sda1 /boot
$ sudo nixos-rebuild switch

Yeah I know what ya mean but boot contains the kernel so if you delete and then reboot then even no fail won't work.
I came from Arch so I know if I wanted to delete everything in boot I could either arch-chroot or boot and delete everything in boot; then use pacman to install kernel then run mkinitcpio

@ndowens nixos-rebuild will also repopulate the empty /boot/ on nixos. nixos-install does the same thing. At some point I just removed /nix/ completely and rebuild my system with nixos-install. So there is no need for manually using chroot, which I had to use previously on arch to fix missing kernel drivers.

@Mic92 ah didn't know that. Haven't had to do this yet on nix 😀  Just know how on traditional setups


Some fixes

nice cleanup in the last few commits btw!

I did a related update on test.js to allow customizing the options, but you still can't select the element though.
To set the options, you'd do something like this:
      function setUp() {                 h2cOptions  = {                     renderer: html2canvas.Renderer.WebGL({                         scene: scene,                         camera: camera                     }),                     onrendered: function(canvas) {                         $(canvas).css({                             position: 'absolute',                              left: 0,                              top: 0                         }).appendTo(document.body);                         animation.animate();                     },                     logging: false,                     profile: false,                     useCORS: true                 }             }

I just updated the commits for this pull request.
tests can now override the selector and any option, default options are still taken from the test.js file.

Nice one!

:D


Ignore Qt installation when finding ICU

This is a bit hacky but I can't find another solution. We want to ignore Qt-provided ICU as it has no headers provided so it's impossible to use it out-of-the-box.
Also move Linux-specific commands before Qt setup.

I made the feature opt-out if needed.


User-admin check 'hijack_admin.W001' incorrectly assumes default admin site

users.User: (hijack_admin.W001) django-hijack-admin does not work out the box with a custom user model.
        HINT: Please mix HijackUserAdminMixin into your custom UserAdmin.

It looks like this pulls the check from the global admin site, but doesn't notice we're using an overriden site.
I tired overriding the global site but is is too late, checks already ran.
from django.contrib import admin

class CustomAdminSite(admin.AdminSite):
    ...

# set the global site
admin.site = CustomAdminSite()

The warning is easily silenced but FYI.

fixed by merging #21


invalid release.json files

hi @NinerBull ,
I compile a catalogue of WoW addons hosted on Github once a week and noticed some of your addons went missing today:

NinerBull/AccWideUILayoutSelection
NinerBull/NPCRPGossip
NinerBull/tRP3_RDotIO
NinerBull/tRP3_RPNameInQuests

Upon inspection it looks like the release.json files are invalid, missing the nolib field. The previous releases look fine.
Frustrated at the lack of a specification myself I created one here:
https://github.com/ogri-la/release.json-specification
As well as a validator if you're interested (feedback welcome):
https://github.com/ogri-la/release.json-validator
I was able to validate ~1.7k release.json files and was surprised at how uniformly valid they all were, probably because they were all generated by the same program. May I ask what you used to create those release.json files?

Hey there!
Thanks for the message and links. I've been doing them by hand, wasn't sure what the nolib field was for, but now I do!
I've added it back into the release.json for all 4 repos, can you check and see if they look ok?
Thanks,
//Conine

Just checked them and they all looked valid:

tRP3_RPNameInQuests
NinerBull/tRP3_RDotIO
NinerBull/NPCRPGossip
NinerBull/AccWideUILayoutSelection

Thanks for touching them up.
Best.

..., wasn't sure what the nolib field was for, but now I do!

A drawback of JSON/JSONSchema is that it can't be annotated with comments.
nolib addons are a release of an addon without the libraries it ordinarily depends on. They're usually smaller and used for bundling within other addons or for those interested in very carefully controlling release dependencies.


[locale] sr-cyrl: Improve L* formats

Fixes incorrect date format explained in #4740
fixes #4740

Coverage decreased (-0.02%) to 94.625% when pulling 257e7139bc7e81f177c18f4a0720524a70d83364 on scrnjakovic:patch-2 into 2e2a5b35439665d4b0200143d808a7c26d6cd30f on moment:develop.

Coverage decreased (-0.02%) to 94.625% when pulling 257e7139bc7e81f177c18f4a0720524a70d83364 on scrnjakovic:patch-2 into 2e2a5b35439665d4b0200143d808a7c26d6cd30f on moment:develop.

@scrnjakovic hello again :) That looks more on-track. Still you'll need to modify the correct files (src/locale/sr-cyrl.js and src/test/locale/sr-cyrl.js).
@milan-j this is the PR equivalent of the issue I pinged you about. Any thoughts?

@milan-j @crnjakovic @dusansimic - can you review this change?
For @crnjakovic @dusansimic - would you like to join as a locale author?

@milan-j @crnjakovic @dusansimic - can you review this change?
For @crnjakovic @dusansimic - would you like to join as a locale author?

Again, sorry for late reply. :) What would that imply? We could continue on fb if you prefer.

Thanks for signing the CLA.
It looks like dusansimic approved these changes.
When new changes happen to these files, I ask the locale authors for approval.
If you would like that, please add a new line at the top of src/locale/* files like
//! author : Milan<EMAIL_ADDRESS>: https://github.com/milan-j

@marwahaha yeah, sure, will do. 👍🏼


Checking the commit hook on CI.

Don't know if contributors have run the commit hook before a commit. We should check it on CI.

Method used for the C++ lib : https://github.com/thibault-martinez/iota.lib.cpp/blob/master/.travis.yml#L243

if I am right, need to add clang-format in Dockerfile and a new step in pipeline.yml.


Release notes are not visible for 12.6.1 driver?

On the official MSSQL JDBC Driver release notes page there is no documentation for 12.6.1 (at https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16) but the milestone https://github.com/microsoft/mssql-jdbc/milestone/73?closed=1is in closed status. would we be having more fixes in this version or this is ready to be published?
Kindly confirm
Thank you

Hi @HarshaVardhan-Sai,
You're right, we missed this. The docs will be updated shortly.

Docs have been updated, will be visible in a few hours.


delete duplicate dep

granderl is duplicated, delete it.

Yes and no. I added it here because I had to add it as an explicit dependencies in vonnegut.app.src. It isn't required to then have it in rebar.config since shackle depends on it and will have it fetched, but it is good form to have all top level deps in .app to be in rebar.config.
And the reason for this was that shackle.app does not include granderl even though it is needed, which means it won't get included in the release if not included in vonnegut.app.
So the first thing that has to happen before we can remove it from vonnegut's deps is to get shackle updated to include granderl in its .app.

@tsloughter  There are two granderl in the deps, delete one of them.

Ooooh, hahaha, my bad :). I misunderstood the patch :). Thanks!


Import rebuilds indexes

dolt table import rebuilds any indexes that are on the target table. Rather than changing the current code to allow for index writes, it should be rewritten to use the same code path that SQL uses.
Of note, dolt table cp shares most of its code with dolt table import, and should probably be simplified so that the old code can be completely eliminated.

@Hydrocharged can we close this now?


Update wasm.md

https://github.com/hyperledger/iroha-2-docs/pull/389 and https://github.com/hyperledger/iroha-2-docs/pull/387 only add whitespace.
You are trying to add your email in https://github.com/hyperledger/iroha-2-docs/pull/386
This is nothing more than blatant spam, and I'm closing all those PRs.


New proposal: Fixing rethrows checking and introducing rethrows(unsafe)

Random question now that async/await are accepted: do we need reasync(unsafe)?

For anyone following, I relied to @lattner's question in the forum discussion: https://forums.swift.org/t/pitch-fix-rethrows-checking-and-add-rethrows-unsafe/44863/5


walk command teleport non-npc entity

The entity zombie is on l@105,6,0,world and when I run the command walk to the zombie to l@100,6,0,world the zombie teleport instead walk
https://one.denizenscript.com/paste/62637

If you were trying to make a zombie walk, your first problem is that you weren't doing that command on a zombie, that's a snowman.

Teleportation, for both NPCs and mobs, indicates that a path could not be found. If it affects mobs but not NPCs in the same path, it's likely related to a difference in pathfinder logic between Citizens and vanilla (vanilla pathfinder tends to get stuck easily).
That said, the walk command doesn't seem to work on mobs at all in 1.14 in my local testing


MSID: 92673 Version: 2 DOI: 10.1101/2<IP_ADDRESS>1293

MSID: 92673
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>1293
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92673
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1293

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/92673v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>1293
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/92673/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

elocations missing from references


Made input bar corners as same as input fields in project properties box on simulator page.

Fixes #2710
Describe the changes you have made in this PR -
Just corrected the border-radius property of .input-search class selector correct
Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage increased (+0.4%) to 82.645% when pulling 0fe370de08a7031707acf8610bc78a9c9bff01c9 on Creatoon:Making-Search-Box-Corners-Square#2710 into 7cc19ee5f624f713005b8b262bc292c9d8a262c2 on CircuitVerse:master.

@vedant-jain03 I have centered the input box as you can see down.

also, Can I make the placeholder color white as same as the other input box placeholders, after implementation,  it will look like.

@vedant-jain03 I have centered the input box as you can see down.

also, Can I make the placeholder color white as same as the other input box placeholders, after implementation,  it will look like.

I think the current color for the placeholder looks good. Let's wait for @nitin10s review.

I think the current color for the placeholder looks good. Let's wait for @nitin10s review.


#472 package.json: { "main": "lib/node.js" } => { "main": "riot.js" }

see discussion for issue #472.
It might take a long time to really separate the files; can we do this little step first?

I do not think this is the right way to handle riot, what will happen to all the users that load it via browserify or webpack?

Anyway this was already merged into the master and it has already led to new issues https://github.com/muut/riotjs/issues/575

Why I don't see it on master? Do I miss some discussion here?

Oups probably yesterday I was too drunk :beer: and I understood the other way around { "main": "riot.js" } => { "main": "lib/node.js" } I am sorry 4 this :smile:
Anyway the issue you have created will stay opened #472 until we will find a better solution that could handle the compiler and riot without breaking the backward compatibility. Thanks for pointing it out and I will keep this pull request closed because it doesn't really solve the problem


Implement histogram smoothing

A couple of minor points but otherwise looks great :)

We've changed the signature round so the caller allocates & frees.


fix: Merge intel master (PERCEPTION-1972)

Merge latest from Intel Realsense master: https://github.com/IntelRealSense/librealsense
v2.12.0 (+ a few misc changes from master https://github.com/IntelRealSense/librealsense/compare/v2.12.0...master)
Install patches from https://github.com/jetsonhacks/buildLibrealsense2TX
Some assumptions are made about how devices attach in the library.
The Jetson has some devices onboard (the ina3221x power monitor, camera module)
that do not report on the USB bus as the library expects.
This patch is a work around to avoid spamming the console
The render loop of the post processing does
not yield; add a sleep
Add CUDA code to translate uyvy to RGB/BGR/RGBA/BGRA

Found invalid ticket: DSO-9243.

Found invalid ticket: PATCH-1.


Add node to end of timeline - new tests

Added two tests for jsPsych.addNodeToEndOfTimeline, in response to #688
Sorry about all of the extra commits. I think all my unrelated changes have been reverted, so the only change included in this PR should be two new tests.

Just ran the tests locally and they seem to be working. The following test fails with the undefined typo that was fixed in pull request #690:

'add node to end of timeline > adds node to end of timeline, without callback'

This test passes when the typo is fixed. The other test ('adds node to end of timeline, with callback') passes in both cases.

This looks good to me. I'm merging!


Support optional error string

statement error string::interval: context-dependent operators are not allowed in computed column\nHINT: STRING to INTERVAL casts depend on session IntervalStyle; use parse_interval\(string\) instead
CREATE TABLE invalid_table (
  invalid_col interval AS ('1 hour'::string::interval) STORED
)

Statement error is also a part of the testing. In some circumstances, we may expect the system to produce errors as expected.

We already have
query error pgcode 42601
select count(sum(v3)) from t

Does this work for you?

Am I using the wrong version?
sqllogictest --version
sqllogictest 0.5.4

My sqllogictest encountered the following failure:
query error pgcode 22000
select -1.702823466e+308 -1.702823466e+308

sqllogictest -p 4566 -d dev -u root 'test.slt'
[FAILED]

failed to parse sqllogictest file

Caused by:
    ParseError { kind: InvalidSortMode("pgcode"), loc: Location { file: "test.slt", line: 1 } }

Error: some test case failed:
[
    "test.slt",
]

Oh, then it might not be well-supported. I'll take a look...

Currently we only have statement error support.
Duplicate with: https://github.com/risinglightdb/sqllogictest-rs/issues/30

close as duplicate


Error response from daemon: No such image: registry.gitlab.com/mlpds_mit/askcos/askcos-vue-nginx:dev

Hi,
I'm trying to do local deployment but getting an error: Error response from daemon: No such image: registry.gitlab.com/mlpds_mit/askcos/askcos-vue-nginx:dev.
Full log attached.
log.txt

I noticed this too. I believe it has to do with this line. To work around, I just changed line 223 to be output_dir = repo.split("FourThievesVinegar/")[-1][:-4] and was able to proceed.


Using default nodePort in tests in unreliable because it might already be occupied on CI

Problem statement
Using a concrete, default nodePort: https://github.com/Kong/kubernetes-testing-framework/blob/238e12e74d32e8692fcae1435b45fd8490f70ac9/pkg/clusters/addons/kong/addon.go#L540 proves to be unreliable in tests, especially in CI since we don't have full control over the environment and sometimes the port can be already occupied e.g. https://github.com/Kong/kubernetes-testing-framework/actions/runs/5022546754/jobs/9006138317#step:8:144 which fails the test.
Proposed solution
Use something like github.com/phayes/freeport which allows finding a free port and use that in tests.

The external library is not even needed for such a simple thing. Passing 0 as the port number instructs the kernel to give some random free port. It will work in this case too, btw. it's what the proposed library does under the hood (but the library ensures only that this port is free for the localhost address, which may be or not a problem). I suggest copying and adjusting a helper function for our use case


inference demo: negative saliency value

I'm testing the inference demo code with the default setting (r2_tuning_qvhighlights). While printing the value of output['_out']['saliency'], I found that it has negative values. Is this reasonable?
Furthermore, if I want to use this model for video retrieval task, should I use the average saliency to represent the clip score?
output['_out']['saliency']
tensor([-0.0343, -0.0360, -0.0387, -0.0397, -0.0320, -0.0345, -0.0370, -0.0371,
-0.0331, -0.0292, -0.0297, -0.0313, -0.0316, -0.0310, -0.0315, -0.0331,
-0.0314, -0.0298, -0.0303, -0.0318, -0.0339, -0.0335, -0.0323, -0.0289,
-0.0274, -0.0262, -0.0271, -0.0275, -0.0330, -0.0315, -0.0349, -0.0313,
-0.0492, -0.0390, -0.0345, -0.0321, -0.0230, -0.0220, -0.0190, -0.0137,
-0.0236, -0.0219,  0.0140,  0.0164,  0.0221,  0.0272,  0.0253,  0.0258,
-0.0045,  0.0361,  0.0355,  0.0158,  0.0122,  0.0146,  0.0366,  0.0380,
0.0433,  0.0294,  0.0306,  0.0315,  0.0392,  0.0407,  0.0425,  0.0346,
0.0381,  0.0396,  0.0455,  0.0410,  0.0397,  0.0432,  0.0465,  0.0310,
0.0261,  0.0397,  0.0332,  0.0335,  0.0299,  0.0208,  0.0195,  0.0373,
0.0143,  0.0156,  0.0156,  0.0274,  0.0172,  0.0033,  0.0055, -0.0062,
-0.0117, -0.0114, -0.0148, -0.0246, -0.0299, -0.0326, -0.0399, -0.0376,
-0.0376, -0.0347, -0.0523, -0.0589, -0.0879, -0.0853, -0.0893, -0.1123,
-0.0485, -0.0520, -0.0483, -0.0528, -0.0507, -0.0532, -0.0555, -0.0542,
-0.0322, -0.0324, -0.0365, -0.0354, -0.0324, -0.0307, -0.0342, -0.0301,
-0.0334, -0.0333, -0.0315, -0.0329, -0.0342, -0.0314, -0.0303, -0.0315,
-0.0285, -0.0311, -0.0360, -0.0343, -0.0298, -0.0315, -0.0357, -0.0285,
-0.0302, -0.0330, -0.0343, -0.0321, -0.0286, -0.0274, -0.0325, -0.0319,
-0.0391, -0.0388, -0.0364, -0.0412], device='cuda:0')

Yes the negative scores are normal as they haven't been normalized. You may refer to our demo code for normalization.
For video retrieval, you may consider using either averaged or max saliency scores.


Sandbox don't open

Hi. Sandbox examples on the https://istarkov.github.io/rifm/docs-readme page does not opening. Please, update it.

We gonna replace current examples with embedded codesandbox editors.


Use drawables for location indicator layer

This PR adds guards for OpenGL code in src/mbgl/renderer/layers/render_location_indicator_layer.cpp and adds an alternative implementation using drawables for the location indicator elements.

added a set of new simple shaders: CommonShader, CommonTexturedShader
added mipmapping and runtime mip generation
added texture sampler anisotropy value/check

Closes #1654


Plans / timeline to upgrade from using tower-cli to replacement awx?

Thank you for developing this tool.
It would appear that tower-cli has become deprecated in preference for using awx.
Is there plans to update this project, to leverage awx in place of the pre-existing tower-cli dependencies / calls?
If yes, what is the projected timeline?

Hi @inversecow, thank you for your interest in the project.
My team has been winding down the usage of Nagios, and for that reason the upgrade development has slowed down. I do however have a personal interest in this, so I will take a look at what needs to be done, and assess the next steps. Please bare with me a little bit.
Thank you.

So, I took an initial stab at it. The new not-sufficiently-tested code has been pushed to the dev branch. Would you please test and see how it works for you?
The biggest difference is that you need to set up various environment variables to pass the authentication information.
TOWER_HOST=https://tower.example.com
TOWER_USERNAME=admin
TOWER_PASSWORD=password

I will find some time to test it more during the week.