The required anti-forgery cookie "__RequestVerificationToken" is not present

Description of bug
The event viewer is flooded with hundreds even thousands of error messages indicating required anti-forgery cookie is not present.
Steps to reproduce

Create a simple Web API GET Method that has the [ValidateAntiForgeryToken] attribute.
Disable cookies in your browser and hit this method to reproduce the error.

Current behavior
The request is denied which is the expected behavior; however, the error is logged in the Event Viewer. This is a huge problem because BOTS (such as Google) index sites several times every week and DO NOT have cookies enabled. This results in thousands of errors in event viewer.
Expected behavior
Deny the request since an anti-forgery cookie is not present; but do not log the error in Event Viewer.
Additional context
This issue appeared with DNN 9.x. In 8.x, the error is thrown but not logged in event viewer.
Affected version

[x] 9.4.3 latest supported release
[X] 9.4.2 latest supported release
[X] 9.4.1 latest supported release
[X] 9.4.0 latest supported release
[X] 9.3.2 latest supported release

I can confirm this issue.

Does anyone have a stack trace of this exception that they can provide?  And can we confirm that the behavior is the same in 9.4.3, where we have the fix for the Memory Leak that applies to WebAPI Modules?
Tracking the code for ValidateAntiForgeryToken itself, we don't log the error, there hasn't been much of change that impacts this.
Realistically, this is/should be logged as an error in some regard, as it could be flagging malicious usage.  (Yes bots will cause this, but it could be a far more malicious user)  Possibly we need to throttle etc.
Just trying to find the root cause on this.

Realistically, this is/should be logged as an error in some regard, as it could be flagging malicious usage.

I agree here I am sure they are malicious attempts.  When I see these logged it is from very strange bots that are not your normal google or bing bots.  And along with them I see attempts to connect to pages that are more related to wordpress admin pages.  I would like to use this as a way to detect them and block or ban them from using the site if possible.  I see pages such as domain.com/wp-admin.
For example on my test site I just got this error:
`12/05/2019 20:25:50
HTTP Error Code 404 Page Not Found
TabId PortalAlias www.d.com OriginalUrl /user/login Referer http://d
TabId:
PortalAlias:www.d.com
OriginalUrl:/user/login
Referer:http://d.com/user/login
Url:http://www.d.com/user/login
UserAgent:Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
HostAddress:<IP_ADDRESS>
HostName:<IP_ADDRESS>`
Following this page load exception:
`Check
12/05/2019 20:25:50
Page Load Exception
AbsoluteURL /user/login DefaultDataProvider DotNetNuke.Data.SqlDataProvide
AbsoluteURL:/user/login
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:ce48f0d5-a0fe-4ed8-a1a7-82a892acafc3
ExceptionHash:c8MISMtxDOjV3GcK3XU0sg8tbxc=
Message:Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <system.web><httpModules> section in the application configuration.
StackTrace:
InnerMessage:Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <system.web><httpModules> section in the application configuration.
InnerStackTrace:
at System.Web.UI.Page.get_Session()
at DotNetNuke.Framework.CachePageStatePersister.Save()
at System.Web.UI.Page.SaveAllState()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)`

Realistically, this is/should be logged as an error in some regard, as it could be flagging malicious usage. (Yes bots will cause this, but it could be a far more malicious user) Possibly we need to throttle etc.

I totally agree; however, any malicious usage is almost impossible to identify among a sea of unnecessary and legitimate calls by BOTS. We have several clients with thousands of these calls by Google BOT.
Consider the following example:
Let's say we use a Web API call to increment a view of a blog post. This happens via a JavaScript call when a user views the page. Google BOT now follows JS; so it makes the call to API but results in the error since it doesn't have cookies enabled.
I don't have a GREAT solution for this issue. Here are my thoughts:

Go back to 8.x logic. Throw the error but don't log it.

Log this as a separate event type so at least admins have the ability to turn the logging off. Right now it's basically spamming the Event Viewer

Ideally, if we can identify if cookies are available for a user agent. If so, then the error should be logged; otherwise, it shouldn't be. But then, malicious users can use this (turn off cookies) to bypass the logging. Same goes if were to identify the User Agent as a BOT. Like I said, I can't think of a great solution.

Perhaps, we need to implement something at Client Side (within our modules) to check for cookies. If cookies are not enabled then we shouldn't use Web API (with validate anti forgery token)

Does anyone have a stack trace of this exception that they can provide?

Here you go:
Message:The required anti-forgery cookie "__RequestVerificationToken" is not present.
StackTrace:
at DotNetNuke.Web.Api.ValidateAntiForgeryTokenAttribute.OnActionExecuting(HttpActionContext actionContext)
at System.Web.Http.Filters.ActionFilterAttribute.OnActionExecutingAsync(HttpActionContext actionContext, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Tracing.Tracers.ActionFilterAttributeTracer.<>c__DisplayClassd.<b__a>d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Tracing.ITraceWriterExtensions.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()

Ok, we need to look at this a bit, there wasn't any intended behavior change here, I'm wondering if the swap to 4.7.2 changed the .NET Framework handling.

@thabaum Your post is exactly why logging is important, you can blog them.  Google, not doing it is a bit surprising and I'd venture it might not be them.

One thing to note here (not sure if this is the case), bots (well legitimate ones) will follow links but will not click buttons. Very often I see links used to fire up actions which is wrong. Buttons should be used for actions and links well to link to another url... I am not sure if this has play in this situation here. But let's say you have a blog list and the link to get to the detail fires up an action and an api call from javascript instead of redirecting to the url of the detail page...
Disregard if it is not the case, just wanted to point that out in case :)

Thanks Daniel. We're not using a button or a link. My understanding is that we have a call to increment the view of the page wrapped in a jQuery Document Ready method. So the call goes out on every page and Google's BOT is now executing JavaScript.

Yeah, that would kind of explain it. Does the code that executes in that event grab the token and adds it to the request headers, that should technically work...

Daniel, there's no problem with the code. It works fine. We pass in the anti forgery token.
The problem is that when a Google Bot visits the page. It has no support for cookies and hence no anti-forgery token which results in an exception; thousands of them.

I don't know enough about how the attributes work, I see we throw an exception but we don't log it, is the logging coming from the actual module try-catch block... If so, maybe catching that specific one and log it as a warning instead of an error? I am not sure just throwing ideas as the wall to look at what sticks :)

From a quick look at it and I did not try it, I think the [DnnApiController] has the [DnnExceptionFilter] attribute on it, it decides what to respond upon some type of exceptions, then it logs it, but that should be in Log4Net, not the event log. I am still unsure what brings this into the event log...

@valadas it's getting logged into the event log at https://github.com/dnnsoftware/Dnn.Platform/blob/46c17ffcbf8f8b2a562e3b97496748d4369cb4f4/DNN Platform/DotNetNuke.Web/Api/DnnExceptionAttribute.cs#L81

Oh right, I read that, but looks like I misread that, I though it was only logging to Log4Net...  Hmm. Disabling that logging based on the user agent would be bad for security, So I guess the solution might need to be on the API endpoint to maybe ignore bots or add that path to the robots.txt maybe? At any rate for this use case, bots should not be counted as a view right...

At any rate for this use case, bots should not be counted as a view right...

Correct. Robots.txt sounds like a great way to address this. Only if all bots actually honored robots.txt. But so far, this is the best solution.
Checking the User Agent at logging or even at API endpoint will have a performance hit.

Checking the User Agent at logging or even at API endpoint will have a performance hit.
And could be a way to circumvent security by spoofing the user agent...

Adding exceptions to robots.txt did not clear this issue

I does not solve the underlying issue, but for this use case only, bots should not count as a view, so maybe a workaround could be to filter for bots (user-agent) in that javascript code before calling the API that counts views, bots should not count as a view anyway.
Also, there are times when crooks try to impersonate google bot, are you able to do a reverse IP lookup on those bot requests, just to make sure we are really dealing with google. See https://support.google.com/webmasters/answer/80553?hl=en

DNN sites who have this issue are probably on Cloudflare or any other proxy. I use CF but I turned all CF functionality off, it only does DNS now and proxy is turned off. The problem did no longer occur in the last 24 hours. What does this tell us? If CF proxy changing cookies or what?

I have been testing this for the last 3 days and the issue also occurs without CF

We have the same issue on dnncommunity.org, see screenshot

Currently a UnauthorizedAccessException is raised if the token is missing.
What would be a better exception? HttpAntiForgeryException  or a custom one?

We need to look at what .net does. But I believe it should be unauthorized only

@mitchelsellers Link was wrong in my post. DNN doesn't take care on what .Net does.

The problem is that when a Google Bot visits the page. It has no support for cookies and hence no anti-forgery token which results in an exception; thousands of them.

That statement is wrong. The anti-forgery token is not part of the cookie. The anti-forgery token is injected in the hidden form field __RequestVerificationToken, and then submitted as HttpRequestHeaders as part of the request.
Anyway, I see the same entries in logs of my servers.

Can we get this fixed in 9.5.0?

Right, but I believe that is the same response that .net does for API responses. I’ll go looking

My logs are filling up with these messages and so does https://dnncommunity.org/ a bit

Can somebody with the same issue confirm that changing

to

solves this issue?

@marietteknap that would most likely be a huge breaking change, granted a good one most likely.
@bdukes thoughts?  Or even @ahoefling possibly?

I have my site running with that setting for 'true' now for a week and I hardly see the issue again. When I see it I can confirm that it is some hack attempt but bots no longer cause the issue. I am a bit confused by some remarks I found about this setting. Some even say that it makes a DNN site read only which is definitely not the cause for me

It would definitely be a breaking change, we'd need to run a few major modules through their paces and see what breaks.

But with the move from WebForms to Web APIs, this may not run into as many issues as it would have years ago.

@marietteknap I'll send you a message with some details, this has security implications

Is this Exception Log related with this issue or not?
Message:RequestVerificationToken not present
StackTrace:
at DotNetNuke.Web.Api.ValidateAntiForgeryTokenAttribute.OnActionExecuting(HttpActionContext actionContext)
at System.Web.Http.Filters.ActionFilterAttribute.OnActionExecutingAsync(HttpActionContext actionContext, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Tracing.Tracers.ActionFilterAttributeTracer.<>c__DisplayClassd.<b__a>d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Tracing.ITraceWriterExtensions.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
and more.........
we could not fix it on DNN 9.7.0

I had a same issue and I found out it was because SSL was enabled and forced in site settings how ever ssl was not enabled on the pages. so enabling SSL on tabs will fix the issue.

I had a same issue and I found out it was because SSL was enabled and forced in site settings how ever ssl was not enabled on the pages. so enabling SSL on tabs will fix the issue.

Thanks for that. I did not have it set to Enforced in Site Settings but I have changed that setting now.

I'm seeing this on a 9.11.0 site, and it occurs every time an authorized superuser tries to use any link in the persona bar.

I'm seeing this on a 9.11.0 site, and it occurs every time an authorized superuser tries to use any link in the persona bar.
UPDATE Technically, it's not "any link," but rather, any action that performs a verified GET or POST to the DNN API. It otherwise appears to be working as expected.

Never mind...  Someone had slipped in a domain restraint in the cookies that I was unaware of.  Once that was updated to         match the dev domain, it's working as expected again.


Typo in Readme image

"Pasenger" in legend should be Passenger (double S).

@toyg I think this should be fixed. If you would please check. Ta


Basic Improvements to Lua's setHealthBarColors

Currently, setHealthBarColors is sufficient enough, however if you are trying to change one side of the healthbar's colors, it's not too great at that.
Currently, running the code setHealthBarColors(nil, 'FF0000') in your Lua script presents you with this.

Due to the way this function is coded, trying to change one side of the healthbar's colors with it isn't ideal.
This PR fixes that, if one argument of the function is nil/empty, it will simply use the current health bar color for the switch.
Now, running the same example mentioned above provides you with this.

Thus making changing one half of the health bar's colors much simpler.

can i use this on a project?

github bugged

can i use this on a project?

shure i dont mind

👍

Going to close this so I can remake the fork with the experimental branch so I can push this commit to it without merge conflicts


Unable to create business critical tier for mssql managed instance

Closing as integrated into 5.4.2


Contribution Guidelines issues

Several broken links on this page, including:

"Pre render scripts" trying to go to https://github.com/cloudfoundry-incubator/quarks-operator/blob/master/docs/from_bosh_to_kube.md#Pre_render_scripts
"CCDB encryption key rotation" trying to go to https://github.com/cloudfoundry-incubator/kubecf-docs/blob/master/content/en/docs/Contribution guidelines/encryption_key_rotation.md
"Secret Rotation" trying to go to https://github.com/cloudfoundry-incubator/kubecf-docs/blob/master/content/en/docs/Contribution guidelines/secret_rotation.md
"README" trying to go to https://github.com/cloudfoundry-incubator/kubecf-docs/blob/master/content/en/docs/Contribution guidelines/pre-render-scripts.md

Also found a link to the suse GH org vs cloudfoundry-incubator.

@mudler @viovanov do you know where those links are supposed to point to?


Add opt-in user preference for prefix and suffix text on renames

Fixes #28679
This PR adds a user preference which, if not set, returns the rename behavior on shorthand properties and import/export specifiers to its state in 3.1.

@uniqueiniquity - I just tried this new feature for the first time (thank you so much for building it!) and I was surprised that renaming a property of a named, destructured export wouldn't rename the symbol when it's imported in another file. Is this expected?  I'll file a separate issue if not expected. Here's the repro:

Uncheck the "Rename Shorthand Properties" options for TS and JS
Create a new code file env.ts:

type ReadonlyAndNotUndefined<T> = {  readonly [P in keyof T]: string; }
export const {
  APP_NAME,
  MONGODB_CONNECTION_URI,
  SENDGRID_API_KEY,
  NOTIFICATION_URL_BASE,
  NOTIFICATION_FROM_EMAIL,
} = process.env as ReadonlyAndNotUndefined<typeof process.env>;

Create another file, use_env.ts :

import { NOTIFICATION_URL_BASE, SENDGRID_API_KEY, NOTIFICATION_FROM_EMAIL } from './env';

In env.ts, use rename symbol (F2) to change the name of NOTIFICATION_FROM_EMAIL

Expected: name is also changed in use_env.ts
Actual: no change to use_env.ts, and a compiler error :
Module '"src/libs/env"' has no exported member 'NOTIFICATION_FROM_EMAIL'. Did you mean 'NOTIFICATION_FROM_EMAIL_2'?

Note that if you export individual variables (not via destructuring export) the rename works fine, e.g.
export const foo = 'bar'; can be renamed to foo2 and the rename will propagate to imports in other files.


Fix "TypeError: Cannot use 'in' operator to search for '__language' in null" in LexicalSelection

Prevents the error "TypeError: Cannot use 'in' operator to search for '__language' in null" from being thrown if firstBlock is null by putting the $isElementNode(firstBlock) first in the if statement.

are your custom nodes inline or block?

@gigantedocil would you want to throw your nodes into this sandbox? I tried to create a minimum replication and couldn't get it to fail, so there's a different bug somewhere up the call stack for me. But my initial fix was setting the custom node's isInline to true

Thanks, @s0rta. I'll try to do this whenever I have some free time.

I'm no longer able to reproduce this in the latest version so I'll be closing the PR.

@gigantedocil  @s0rta This is still reproducible using the most recent version of lexical. The problem is if the CustomElementNode is marked as being inline.
Here is a minimal reproduction case: https://stackblitz.com/edit/facebook-lexical-urixtg?file=src%2FCustomElementNode.ts
And a video of me pressing "ctrl-v" to paste some text into the CustomElementNode: https://youtu.be/XJHWj9TZXIg
I'm not sure if this PR is the right way to solve this issue though. Should I raise this as a separate bug report?

@nigelgutzmann If you think it's a bug you should raise it as a separate issue that follows the issue template

Reported here: https://github.com/facebook/lexical/issues/6701


View Filter based on Session_Id or LoggedIn User

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Be able to filter a view based on session_id or logged in user
Describe alternatives you've considered
Don't know at this stage.

if you Key to user field is called something like responsible, embed the view with extra state formula = {responsible: user?.id}

you can also use the session_id variable in extra state formula here

The solution you provided is working like a charm. I am really enjoying this platform. So much potential and your support is awesome. Thank you.


Add correct c++ support

Seems like c++ is being a weirdo.
g++: fatal error: cannot execute 'cc1plus': execvp: No such file or directory
compilation terminated.

I think this is fairly solvable by re-installing c++, for the very least.

Fixed as of 0.0.5a


#error "Unsupported board." of twister build ./tests/drivers/adc/adc_api

Describe the bug
Got #error "Unsupported board." of twister build ./tests/drivers/adc/adc_api.
About the failing check of "Run tests with twister / twister-build (1)", it's not caused by modification of the PR.
According to the build log, lpcxpresso55s69_lpc55s69_cpu0_ns seems fail to build /tests/drivers/adc/adc_api/drivers.adc.
The snippet of log as below:
/__w/zephyr/zephyr/tests/drivers/adc/adc_api/src/test_adc.c:45:2: error: #error "Unsupported board."
45 | #error "Unsupported board."
|  ^~~~~
https://github.com/zephyrproject-rtos/zephyr/actions/runs/8645366060/job/23733494554?pr=71267
To Reproduce
Steps to reproduce the behavior:

Send PR of ./tests/drivers/adc/adc_api/boards
Twister build
Got error  "Unsupported board." of vmu_rt1170/mimxrt1176/cm7, yd_esp32/esp32/procpu, lpcxpresso55s69_lpc55s69_cpu0_ns s
https://github.com/zephyrproject-rtos/zephyr/actions/runs/8645366060/job/23733495034?pr=71267

fix is here #71472


Fix issues with complex-valued beam

fftvis.simulate_vis currently makes the assumption that the beam is real-valued and that the hermitian symmetry of the uv-plane can be used to compute negatively oriented baselines. If one provides a complex beam, such as a polarized beam, this assumption is broken. This should be addressed soon

Closed with https://github.com/tyler-a-cox/fftvis/pull/7


Proper security statements in README

This PR proposes adding more measured language around SSH3's current security status. Making absolute security claims about an early prototype could be misleading without extensive analysis and review over time.
To build community trust and encourage assistance accelerating SSH3's secure development, I've updated the messaging to:

Note SSH3 is still an experimental proof-of-concept
Advise against public Internet exposure in present form
Explicitly state that expert cryptographic review is still needed
Call for collaboration to advance the protocol responsibly

I believe positioning SSH3's security more conservatively for now is prudent. It still shows intriguing promise improving on SSH2, but overstating protections too early can risk credibility and user security if vulnerabilities emerge later.
By being upfront about limitations and the need for review, my aim is to facilitate open community engagement accelerating SSH3 towards safe production readiness. I welcome any feedback, and hope these README updates might encourage capable security researchers to help validate and strengthen SSH3 moving forward!

I would also like to refer Issue #57 in the README, by stating that if one has security questions, there is an open discussions with some answers there. Would you like to add that as well ?

@francoismichel I agree, all your wording suggestions look better. I've committed these changes and credited you as the author. Shall we address the security questions in a separate pull request? I believe it would be worthwhile to add some information to the SECURITY.md file in the repository.

Can we proceed with the changes proposed in this PR and comments? I feel this would add to the README and as such is good to merge sometime soon :)

Updated the code, please recheck if all proposed changes done right and the merge is correct.

Rebased your branch with main and then merged in 9259245, thank you very much for the work !


Model diff sig tests

@matanor
merging of statistical tests on LLM metric comparisons, and visualizations.  Also included a notebook showing how to use them

Have decided it may be better to make this its own repo outside of unitxt since it is of general use.


Fetch Stack Label at the click of the stack bar in the bar chart

Hi,
Is it possible to get the stack label at the click of the bar in the stacked bar graph?
Thanks!

You can check ChartMarker or override the highlight logic to display the stack label. Take a look at drawValues in BarChartRenderer. It draws the value label there. You can do it similarly


[BUG] Tailwind does currently not work in any starter

Qwik Version
0.0.24
Operating System (or Browser)
Linux 5.18.1, Chromium 102.0.5005.61
Node Version (if applicable)
18.3.0
Which component is affected?
Qwik Rollup / Vite plugin
Expected Behaviour
Tailwind styles should be included in the bundle (dev-mode and production mode)
Actual Behaviour
No tailwind styles are applied.
Additional Information
Reproduction:

use any starter and tick the tailwind option during creation
set a tailwind style in any component, e. g. bg-red-500 on any div
start build/dev mode

Fixed by https://github.com/BuilderIO/qwik/commit/8c4e554686cd35e00e197a75dfaa0322b7e54c6e

@manucorporat When trying out qwik v0.0.25, it still does not work with tailwind (or any CSS changes in src/global.css)
Can you please check again and reopen the issue?
Maybe I find some time to compare the starters to the documentation website.


Assets directory/list of dirs and files to be packaged with the binary

Hi,
This is a super cool tool. Thanks for making it.
It would be nice if this supported a sort of assets directory to package with the binary (or a file list).
I haven't found a way to spcify this in the deploy or build step so far.
Why?
What I'm trying to do is create a React on frontend / Rust as the backend server application.
I'm using lambda with axum and I need the react files (and index.html) to be served also from the lambda. So I need this to package my node dist output for the react app with the lambda (then I can serve it from there when needed), while also keeping the other routes such as api/bla for API work.

Ups, there's this that does exactly what I need:
https://www.cargo-lambda.info/commands/deploy.html#adding-extra-files-to-the-zip-file


RT4262: Configure always asks for make depend

When ./config is run, the Configure script always complains about
'make depend? needing to be run because the $default_depflags and
$depflags do not match.
Recent changes to Configure automatically create $default_depflags,
but takes special exceptions for shared, zip, hw and asm, which are
not normally put into $default_depflags but are put into |$depflags|
causing a mismatch leading to the warning.
Add (no-depflags) to the shared and zlib options in the disabled
table. This precludes them from being added to the $default_depflags.

Not sure if this is the correct way to fix it, but there is a mechanism to not add values to the depflags by adding (no-depflags) to the value.

@levitte: You should probably take a look at this.

Yeah, we should really tone it down quite a bit. Among others, Configure should keep quiet if there isn't a Makefile present beforehand.

fixed, differently, in d20bb611d90df0dc3561a6972ba6bf0e3c65b3e5


SPI Slave not Realtime and corrupting Data (IDFGH-5166)

Environment

Module or chip used:  ESP32-WROVER-IE
IDF version: v4.2-351-gce2c615bb
Build System:        idf.py
Compiler version: 8.4.0
Operating System:     macOS
Power Supply:        external 3.3V

Problem Description
I am interfacing with ADC to capture waveforms. ADC sends data as SPI Master at 8Mhz / 4Mhz (configurable) to ESP32 (SPI Slave). Waveform is a 50Hz sine wave from a signal generator.
The data received in ESP32 is then plotted. I am getting spikes every  3-4 cycle. ADC sends 28bytes at 8kHz frequency. It looks like the SPI Slave Driver is corrupting the data / not capturing bits in realtime.
Plotting the SPI Protocol data of ADC (using a protocol analyzer) results in a perfect sine wave.
So there is definitely something wrong with SPI Slave driver. Can you help ?
SPI Mode (as per datasheet of ADC) should be 3
But ESP32's SPI Mode 1 gives the perfect data. (0, 2, 3 are full of noises).
PFA Spike Image
Expected Behavior
Perfect Sine wave is expected.
Actual Behavior
Sine Wave with Spikes every 3-4 cycles. Protocol Data represents perfect Sine Wave without any spike. SPI Slave Driver is wrong.
As per ESP32 SPI Slave -

As per Protocol Analyzer -

Here is Logic Analyzer screenshots.

Thanks for the very detailed report.

Hi @nikhilavrio ,
For SPI protocol, master determines when to start/finish a transaction, no matter if slave has prepared ready TX/RX/both buffer(s) or not. So usually there is a synchronization way to let master know slave is ready.
Therefore, if you directly use SPI slave driver to receive data from ADC without synchronization, you may not get complete data in some conditions. Let's take an easy example:

Slave side prepares a 28-Byte buffer.
Master lowers down the CS, the transaction starts.
Slave side called spi_slave_transmit. When the slave-prepared-buffer is actually loaded to the SPI hardware, we assume that at this time, master has already sent 10 Bytes data to the SPI bus.
Slave side gets the rest 18 Bytes data from the SPI bus.
Master finish sending all the data, and it sets CS to high.
spi_slave_transmit will return due to the low CS.

Finally, for the 28-Byte buffer, the first 18 Bytes data are actually got from the master, whereas the rest 10 Bytes of the buffer are unchanged. At this point, if you plot all the buffer, you'll get a wrong plot.
However, you can check the trans_len  of spi_slave_transaction_t indicating the actual received bytes per transaction. With respect to the above situation, the trans_len would be 18*8 (in bits).
For synchronization, the goal is to make sure that slave has actually loaded its buffer to the SPI hardware (time point A) before master lowers down the CS line. We have a callback to indicate the time point A  - post_setup_cb in spi_slave_interface_config_t will be called at this time.

@nikhilavrio Thanks for reporting, would you please help share if any updates for this issue? Thanks.

@nikhilavrio Thanks for reporting, would you please help share if any updates for this issue? Thanks.


(FACT-1595) update debug tests, override cases, and split no_ruby test

Updated test for code style, risk tags, command output collection, and TestRail numbers
Split the no_ruby tests into separate tests
Split the command line override tests into separate tests
Renamed the ttls.rb test file which will be split out in a different pull request
Tested on:
arista4-32a, ciscoxr-64a%7Bhypervisor=vmpooler%7D, cisconx-64a%7Bhypervisor=vmpooler%7D, cumulus25-64a, debian8-64a, fedora25-64a, osx1012-64a, redhat7-64a, sles12-64a, solaris11-64a, ubuntu1604-64a, windows10ent-64a, windows2016-64a

CLA signed by all contributors.

@Magisus now updated with the file name change.

👍


1294 nomad facet

Description

Fixes #1294
Type of change

[x] Tests
[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective
Add NomadFacet unit tests
Related Issue(s)
Fixes #1294
Related pull request(s)

First merge in #1383


How to reset Captcha

How is reset handled?

@frostymarvelous I will implement it as soon as possible.

@appleboy I was thinking of creating a pull request for this feature, I propose exposing a reset method which could be accessed via a callback ref. So usage would look like...
resetCaptcha() {
    this.recaptcha.reset();
}

render() {
    <Recaptcha
        ref={e => this.recaptcha = e}
        {...otherProps}
    />
}

Let me know your thoughts and I can implement and document.

Refs. Hmm.
Anyway,, I think it is a good idea.

@danbahrami Good. I will take it.

@frostymarvelous I would say refs is the most declarative way of doing this but I'm open to suggestions. do you have a different api in mind?

I was speaking from something I remembered from the docs concerning deprecation.
However, I went back and checked and it was only referring to "string" refs.
So yeah, it is a great way of doing it.

@frostymarvelous Please try the 2.2.3 version and see the example.

A big thanks to @danbahrami for the work put in.
And thanks to @appleboy for the project in the first place.


GNOME Software is broken on master

Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
$ nix run nixpkgs#gnome.gnome-software
00:26:08:0195 GLib-GIO g_app_info_get_name: assertion 'G_IS_APP_INFO (appinfo)' failed

This is the default nixpkgs flake, targetting NixOS master. nix comes from NixOS 21.11's pkgs.nixFlakes
Expected behavior
It runs
Additional context
Host is running NixOS 21.11. GNOME Software from that version works
Notify maintainers
@hedning @jtojnar @dasj19 @maxeaubrey
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.96, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4`
 - channels(root): `"nixos-21.11.335820.521e4d7d13b, nixpkgs-git"`
 - channels(afontain): `"nixos-20.09-20.09.4407.1c1f5649bb9, nixpkgs-unstable-22.05pre342949.28d58b97925, nixpkgs-20.09-20.09.4407.1c1f5649bb9"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Also, I'm using GNOME 40 Wayland, and
nix-repl> :p outputs.legacyPackages.x86_64-linux.gnome.gnome-software.version
"41.3"

GNOME Software 41 from master works fine on GNOME 41 from master (or nixos-unstable). Given how tightly integrated GNOME is, I don’t find it surprising that you need the same version of everything. Why do you want to mix-and-match and why do you expect that to work?

Turns out that it actually works, but due to the gnome-software daemon being autostarted, it did unexpected things. If you close it manually then it works perfectly. The error ("assertion failed") did look like a fatal bug, and one that isn't supposed to happen, even with mix-and-match. So I opened an issue.

why do you want to mix-and-match

This was for experimenting with a newer version to see if a bug has been fixed.

why do you expect that to work?

Because why not! While GNOME Settings is pretty dependent on the version of the many gnome settings daemons, I wouldn't expect GNOME Software to be. I think I've even seen GNOME Software working on non-GNOME?
My mistake though, as it actually works, closing.


Failed to load the preview package

[Enter steps to reproduce below:]

Just tried to install from the freshly installed Atom ->  Preferences -> Install
...

Atom Version: 0.192.0 :warning: in 1.0 API Preview Mode :warning:
System: Mac OS X 10.10.3
Thrown From: preview package, v0.13.7
Stack Trace
Failed to load the preview package
At Cannot read property 'prototype' of undefined

TypeError: Cannot read property 'prototype' of undefined
  at __extends (/Users/name/.atom/packages/preview/lib/preview-message-view.coffee:1:1)
  at /Users/name/.atom/packages/preview/lib/preview-message-view.coffee:4:3
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview-message-view.coffee:28:5)
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview-message-view.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Users/name/Applications/Atom.app/Contents/Resources/app/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview-view.coffee:8:22)
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview-view.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Users/name/Applications/Atom.app/Contents/Resources/app/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview.coffee:2:15)
  at Object.<anonymous> (/Users/name/.atom/packages/preview/lib/preview.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (/Users/name/Applications/Atom.app/Contents/Resources/app/node_modules/coffee-cash/lib/coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Package.module.exports.Package.requireMainModule (/Users/name/Applications/Atom.app/Contents/Resources/app/src/package.js:667:34)
  at /Users/name/Applications/Atom.app/Contents/Resources/app/src/package.js:170:28
  at Package.module.exports.Package.measure (/Users/name/Applications/Atom.app/Contents/Resources/app/src/package.js:147:15)
  at Package.module.exports.Package.load (/Users/name/Applications/Atom.app/Contents/Resources/app/src/package.js:161:12)
  at PackageManager.module.exports.PackageManager.loadPackage (/Users/name/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:354:14)
  at PackageManager.module.exports.PackageManager.activatePackage (/Users/name/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:433:30)
  at /Users/name/Applications/Atom.app/Contents/Resources/app/node_modules/settings-view/lib/package-manager.js:268:29
  at exit (/Users/name/Applications/Atom.app/Contents/Resources/app/node_modules/settings-view/lib/package-manager.js:43:16)
  at BufferedProcess.triggerExitCallback (/Users/name/Applications/Atom.app/Contents/Resources/app/src/buffered-process.js:63:47)
  at ChildProcess.<anonymous> (/Users/name/Applications/Atom.app/Contents/Resources/app/src/buffered-process.js:85:18)
  at emitTwo (events.js:87:13)
  at ChildProcess.emit (events.js:169:7)
  at Process.ChildProcess._handle.onexit (child_process.js:1057:12)

Commands
     -6:26.0 application:open (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -5:43.1 snippets:next-tab-stop (atom-text-editor.editor)
     -5:43.1 snippets:expand (atom-text-editor.editor)
  5x -5:41.9 core:move-down (atom-text-editor.editor)
     -5:36.4 core:save (atom-text-editor.editor)
     -5:06.2 timecop:view (atom-text-editor.editor)
  4x -4:40.7 core:backspace (atom-text-editor.editor.mini)
     -3:56.4 core:confirm (atom-text-editor.editor.mini)
     -1:03.4 command-palette:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
  4x -0:52.9 core:backspace (atom-text-editor.editor.mini)
     -0:50.5 editor:consolidate-selections (atom-text-editor.editor.mini)
     -0:50.5 core:cancel (atom-text-editor.editor.mini)
     -0:49.3 tool-panel:unfocus (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {}
}

Installed Packages
# User
language-jade, v0.4.0
preview, v0.13.7

# Dev
No dev packages

+1

Can you both provide me with some more information. I am unable to reproduce this error.

@Glavin001 This issue just appeared after I upgraded Atom to 0.198.0. The error message pops up right away once you launch. It seems this update broke a number of packages.
I'm working on a fix for this package along with several others. I'll make a pull request and reference this issue if manage to fix it.

I am also on Atom v0.198.0 and I just published v0.14.0 that fixes all deprecation warnings ( #94 ). Let me know if this is still an issue with v0.14.0


Shorter state URLs

Right now, the state URLs are very long; for example:
https://balatrolator.com/?state=N4IgFghgdgJgziAXARgDQhgSzgYwgJ3iQAZ0BbAeygFMBPE9AIwBtNYlQoIzqkQBlMhGbMABACFW7dNgCCOAC6YAbr0QL8AV2oBfdDGo4A1nwBK1GKIAihk%2BkiwAMtVXMEiUADFmmuGFGeKmqgzC7UzEhoIAAOzBC07sR6IN6%2B-gASFL7BIKGukeix8YnJgaqiFABmohCiANJsMBy5YREohXEJJMn8GhCYAOZgCgE%2Bfs154QUxnSXonln4FdW1DeweLfntM8Xd85oiopnZE63TRV2ISfNjYKdbACwdu1c9fYPD91PbF3MgACpgfDUajLGr1RpfNpRX57AEAdwoogACv18FDzrM4ajMOiNpNoc9LtcQOkPqIAMIEJr4s4-LGvZIAKwoRmo%2BHcAG1ONw1AIKMYarAJL4jGwQOgLJglFQ%2BIwIHBeB1fBSwJhoollXAALIHJSxTDshggJQ8HV69WsI3bfDQEyIEDyJUgOCaaV8Ck%2BRgIGRweRKVRIDTaPQ8nh8KyiiUgKUyqByhXO2IqtUa43J83MfVWvGkE2YM26rOWw14qK2qD2x04Z2u90Oz2ab3RuSKIJBrS6VBhvmOXwKWiiABSrKNkqwcYTiujGdV6s1M18RezpeNpuomZX1vLdr4TujdYUHq9PpArYDamDXZ7fEk2mi%2BDYR-H0swsod8unWrnaauWuXJbWnm66boBZYAEwAHTgQArOgFZVvu6CHseTanue7bqJ2oYgFw4YOpIFAUPAChUM6sZvvGH6JjOYw-guGYAQaQHoCBTE5tMCF7jWB5ukeDYni2fptoGWEhgAuugLJsvg-DMBQCjuAAbESFhUoQXKgFxDprAMvH1qS1AEIp0YUe%2BICfuRUAODWPBQPxuFkQeRltI5NBCTYjCaJUlQWEglTCIqOHaSAun6Q56RGfgJkvpO1FfjG1nQLZ1D2XwUBOchLnpZlZ5wJ53m%2BTSAVuNeIAhUOEDGOFfCRcZp5mVRFk0ZKSVQClaUOhl7lZcIOU9XlBU%2BX5iAlUF3blbuDpIS6fG1VFMUxhOlFTlZNnUHZDndbW2Vdbl2BDUV-mBWVIVKTVDp1dFDXLeZlmmW1HVbblip9XtA0HdQXnDcVJ06JJ4DhDA6lEIgnLiToQA
I know you're tracking a few more things than I am, but the same hand in my calculator has a URL state-string that's less than 3% of the length of yours:
https://efhiii.github.io/balatro-calculator/?hand=oACMOJQACOMAECgAKaA0BIAwBA
There are a few things that made it possible for me to make the state-string so short:

default states:

If a particular feature isn't used, it can be represented using only 1 bit to signify that it's in the default state; for example:

hand level (default each to 1)
joker state (default to the state it's at when bought)

minimal bit-lengths for values; for example:

edition: 1 bit to signify if it's standard, if non-standard, 2 bits for which edition (my 4 states don't include negative but does include disabled)
enhancement: 3 bits for which enhancement and 1 bit for if it has a Red (Double) Tag (other tags are not bothered with)
joker type: 8 bits
number for suit: 2 bits
number for card type (2 - ace): 4 bits
most numbers are stored as either 16 bit unsigned int or 16 bit signed int

number of cards is a 16 bit unsigned int
number of jokers is a 16 bit unsigned int
hand levels are 16 bit unsigned ints
joker states are 16 bit signed ints

assumed 0s

the representation of all default values is via 0s and the last step in my URL building function is to remove trailing zeros, then during URL interpreting, I assume any bits past what was provided in the URL is a zero.
Ordering less-used features (like number of planets in the consumable area for Observatory) at the end so that they usually are free because of assumed 0s

Even if you don't want to rely on using small numbers like 16 bit ints, you can use small ints where possible and have a higher bit-length fallback, but for all the things I used 16 bit ints for, I don't think it's practical for the integer limit to be reached.

Thanks for the suggestion, @EFHIII!
I've implemented a more application-specific (custom) algorithm for shorter share URLs in https://github.com/kleinfreund/balatrolator/commit/c114663f4cffa68c2db4817b25a2db06558f3734.
This is possibly not final and certainly not the most minimal in terms of URL length, but much better than the previous URLs which were indeed excessive. I want to give myself some room in case the state model I use needs significant changes (pretty much certain at this stage of development). I want to avoid needing to change it too often because every time I do, the chance the current URLs break is very high.

I think it's broken at the moment

I think it's broken at the moment

Could you be a bit more specific, please? I can look at this later, but from a quick glance, it seems to work. Note that any previous URLs will definitely be broken. I very much consider this project a work-in-progress in the current stage and am fine with breaking things like that if necessary.

Sorry, I was messing with it and every time I refreshed, it went back to blank. I hadn't realized you had to click the submit button to get the url to update.
(the URL on mine updates anytime something changes)


No PipFile found

Hello All ,
My systems is macOSX Ver 10.14.6.
My python 3.7.4
When I run pipenv like "pipenv --python 3.7"  the env is do created but always in the same place.
and NO PipFile and Pipfile.lock is avail on the local dir.
here what I have done...
I created dir /home/test1/
run "pipenv --python 3.7"
no Pipfile on the /home/test1 dir to be found.
I try to install django and it did install it fine but not on the pipfile on current dir.
I also created /home/test2
run the same as above and the result are the same.
I try to install flask and it did install it fine but not on the same pipfile as above in main home dir.
Any help please.
Koby Peleg Hen

You must have a Pipfile somewhere in the parent directories, type pipenv --where to see where it is.

Thank you all ,
I did have at the top dir Pipfile.
I deleted the file , make the test and every thing is perfectly fine now.


feat: allow disabled state at build time

This pull request removes the current requirement that the module must be enabled at build time in order to be available at runtime.
This change gives developers more flexibility: the module can now be initialized in a disabled state and later enabled at runtime.

Hi, first of all thanks for the PR! I'm just not quite sure if I understand what your goal is here, since what you're describing is already possible, as you can set the enabled flag via a runtime variable.
For example:
NUXT_BASIC_AUTH_ENABLED=true

I would like to have a 'disabled by default' feature. Currently, if you build your project with NUXT_BASIC_AUTH_ENABLED set to false, it is not possible to enable it at runtime.

Ah I see right, gonna merge it and make a release, thanks again for the contribution.


4.x: CurrentThreadScheduler fast path untimed Schedule

This PR modifies the schedule logic of the CurrentThreadScheduler to avoid allocating the queue for the first task on an idle scheduler. If the action schedules further tasks in a reentrant manner, those will get queued us just like now.
Since this scheduler is per thread, there is no need for locks/synchronization as each caller thread will only see its own thread-local structures and it can't cross-post to some other thread.

The fast-path could be added to the timed case as well (i.e., sleep before executing the plain action, then trampoline if necessary).


Orchard v.<IP_ADDRESS>- Corrupted Orchard.Index?  All Indexes Rebuild Failing

Question
Is there something I can do uncorrupt Orchard.Index, so I can start indexing things again?  I have disabled and re-enabled the related modules: Indexing, Lucene, and Search without results.
Details
I am no longer able to build indexes because of, I suspect, some sort of corruption of Orchard.Index I do not know how to fix.  Rebuilding some old indexes caused me to lose all the old indexed documents.
To dig deeper into the issue I created a new index and a new content type.  I set the new content type to be indexed, by the new index and then created one article for it.  I then rebuilt that new index and this indexed fine in the development environment, but failed in production where everything is failing to index, and failing to generate the settings file.
(Full disclosure I am reposting, though this article has the latest details, from the same problem posted in stack overflow due to not getting any responses from stack overflow for a couple days.
orchard-all-indexes-rebuild-failing)
I followed this article without results: orchard-search-indexing-issue
This did not work. I think probably because
App_data\Sites\Default\Search.settings.xml
doesn't get generated in the first place. I do however see a file:
App_data\Sites\Default\Search.settings.xml.lock
I believe the Orchard.Indexing.Services.IndexingTaskExecutor UpdateIndexBatch method is failing because my impression is the lock file would be created and then deleted if it was working. Here is a possibly relevant error:
2021-01-08 00:00:41,174 [48] Orchard.Exceptions.DefaultExceptionPolicy - Default - An unexpected exception was caught (null) System.NullReferenceException: Object reference not set to an instance of an object. at Orchard.ContentManagement.DefaultContentManager.Get(Int32 id, VersionOptions options, QueryHints hints) at Orchard.ContentManagement.DefaultContentManager.Get(Int32 id, VersionOptions options) at Orchard.Indexing.Services.IndexingTaskExecutor.b__0(ContentItemVersionRecord versionRecord) at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext() at System.Linq.Enumerable.d__641.MoveNext() at System.Collections.Generic.List1..ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source) at Orchard.Indexing.Services.IndexingTaskExecutor.BatchIndex(String indexName, String settingsFilename, IndexSettings indexSettings) at Orchard.Indexing.Services.IndexingTaskExecutor.UpdateIndexBatch(String indexName) at Orchard.Indexing.Services.UpdateIndexScheduler.UpdateIndex(String indexName) at Orchard.Events.DelegateHelper.<>c__DisplayClass2b2.b__2a(Object target, Object[] p) at Orchard.Events.DefaultOrchardEventBus.TryInvokeMethod(IEventHandler eventHandler, Type interfaceType, String messageName, String interfaceName, String methodName, IDictionary2 arguments, IEnumerable& returnValue) at Orchard.Events.DefaultOrchardEventBus.TryNotifyHandler(IEventHandler eventHandler, String messageName, String interfaceName, String methodName, IDictionary2 eventData, IEnumerable& returnValue)
Another error I see that I believe is related to the issue seems to occur in Orchard.Indexing.Handlers.InfosetFieldIndexingHandler
2021-01-08 00:00:02,236 [48] Orchard.ContentManagement.DefaultContentManager - Default - NullReferenceException thrown from IContentHandler by Orchard.Indexing.Handlers.InfosetFieldIndexingHandler (null) System.NullReferenceException: Object reference not set to an instance of an object. at Orchard.Fields.Fields.DateTimeField.get_DateTime() at Orchard.Fields.Drivers.DateTimeFieldDriver.b__15(DateTimeField field) at Orchard.ContentManagement.Handlers.DescribeMembersContext.Enumerate[TField](Func1 enumerate) at Orchard.Fields.Drivers.DateTimeFieldDriver.Describe(DescribeMembersContext context) at Orchard.ContentManagement.Drivers.ContentFieldDriver1.Orchard.ContentManagement.Drivers.IContentFieldDriver.Describe(DescribeMembersContext context) at Orchard.Indexing.Handlers.InfosetFieldIndexingHandler.<.ctor>b__0(IndexContentContext context, InfosetPart cp) at Orchard.ContentManagement.Handlers.ContentHandler.InlineStorageFilter1.Indexing(IndexContentContext context, TPart instance) at Orchard.ContentManagement.Handlers.StorageFilterBase1.Orchard.ContentManagement.Handlers.IContentStorageFilter.Indexing(IndexContentContext context) at Orchard.ContentManagement.Handlers.ContentHandler.Orchard.ContentManagement.Handlers.IContentHandler.Indexing(IndexContentContext context) at Orchard.ContentManagement.DefaultContentManager.<>c__DisplayClass99.b__97(IContentHandler handler) at Orchard.InvokeExtensions.Invoke[TEvents](IEnumerable1 events, Action1 dispatch, ILogger logger)
I really need to get this working, and do not know what to do.  Any ideas would be appreciated.

You can try to delete the index files and it will recreate them

You can try to delete the index files and it will recreate them

Thanks for the response!  We tried deleting the App_data\Sites\Default\Search.settings.xml and the App_data\Sites\Default\Index\Search directory, but we are unable to rebuild Search.  We also tried deleting the index through the application instead, and the result was the same.  Also, instead of App_data\Sites\Default\Search.settings.xml  we get  App_data\Sites\Default\Search.settings.xml.lock when we rebuild.

Thanks for the response!  We tried deleting the App_data\Sites\Default\Search.settings.xml and the App_data\Sites\Default\Index\Search directory, but we are unable to rebuild Search.  We also tried deleting the index through the application instead, and the result was the same.  Also, instead of App_data\Sites\Default\Search.settings.xml  we get  App_data\Sites\Default\Search.settings.xml.lock when we rebuild.

The solution was found.  There was some null data within ContentItemRecord.  The null Data and ContentType_id resulted in no indexes being built.
Here is the query we used to find the bad data.  The xxxxxx would need to be replaced by whatever prefix is assocaited with your table, but gives you an idea what to do.
  There was some null data within ContentItemRecord.  The null Data and ContentType_id resulted in no indexes being built.
Here is the query we used to find the bad data.  The xxxxxx would need to be replaced by whatever prefix is assocaited with your table, but gives you an idea what to do.


adding MASQ token info and logo

hello and こんにちは to the team at Sushiswap!
KauriHero from MASQ Network here - humbly requesting you to consider our project to be added to default list.
I've added info.json and logo.png as outlined in the instructions.
We have been on uniswap and linkswap for quite a few months now, so would be grateful to be joining the sushiswap community!

Greetings @jiro-ono
I see the PR failed, but I couldn't detect if it was something on our end with our addition of the info.json and logo.
is there anything I can assist with, to fix and have this reviewed, so you can consider merging it?

actually I have just further inspected it and detected a typo.
I apologize for this - I will correct and review again @jiro-ono
apologies

ありがとうございました @jiro-ono !
That is great service!  😀


flatcar linux: fw_cfg has been updated

System Information
Linux distribution
arch linux

Terraform version
$ terraform -v
Terraform v0.12.6

Provider and libvirt versions
$ terraform-provider-libvirt -version
5c01d18431ea2b9df4870990be6a1736ec6f322a
Compiled against library: libvirt 5.5.0
Using library: libvirt 5.5.0
Running hypervisor: QEMU 4.0.0
Running against daemon: 5.5.0

Description of Issue/Question
Hi ! I am using this plugin in order to deploy flatcar linux cluster on libvirt. FYI flatcar linux is a fork of coreOS container linux (https://www.flatcar-linux.org/).
Back in the days, the ignition config file was given to the domain through fw_cfg, but the key value has changed from opt/com.coreos/config to opt/com.flatcar-linux/config. (https://github.com/flatcar-linux/ignition/issues/2)
It could be nice to specify the value of the key in terraform config file ?
https://github.com/dmacvicar/terraform-provider-libvirt/blob/5c01d18431ea2b9df4870990be6a1736ec6f322a/libvirt/domain.go#L240-L249

@tormath1  thx. I think it should be not really difficult to convert it to a variable. thx for issue

Ok, I am on it. :rocket:

@tormath1 considering this closed by your pr. Feel free to squash commits


the legacy buildpack can still be used in "binder" or ".binder" folders

In https://github.com/jupyter/repo2docker/pull/829 the legacy buildpack (LegacyBinderDockerBuildPack) is removed, but actually it can still be used in binder config folder, because detect method only checks the Dockerfile at the root:
https://github.com/jupyter/repo2docker/blob/8bbced7ded5a21b581f1f3846ffc9f87944ba799/repo2docker/buildpacks/legacy/__init__.py#L19-L23
was this on purpose? Or should we create a PR and change it to check Dockerfile in binder_dir?
Btw I know this is not a realistic usecase, but if a repo contains

./Dockerfile: which uses the legacy image
./binder/requirements.txt

this will also throws error saying that legacy buildpack is removed, but actually it should pick python buildpack.

I think it should not check for Dockerfile in binder_dir, since that never worked for the legacy buildpack, but it should probably add:
if self.binder_dir:
    return False

before checking the top-level Dockerfile contents to make sure legacy is never used if binder_dir is present.

Should we add this special casing? Everywhere else in repo2docker we have the "rule" that "if there is a Dockerfile it is used, nothing else counts". Here we'd start inverting that "Dockerfile wins, unless it is a legacy one, and your have config files in a binder sub-directory, but not if the config isn't in a sub-directory." (or something like that) The point being it is more complex than the current rule.
I'm wondering if there is a reason for repo owners wanting to keep the legacy Dockerfile instead of deleting it when they don't want to use it any more. If there is no use-case for keeping it I'd vote for a solution that encourages people to remove the legacy Dockerfile as a solution to problems/weird behaviour.

tl;dr: I think the logic we have now is right, and we shouldn't make any changes.

Everywhere else in repo2docker we have the "rule" that "if there is a Dockerfile it is used, nothing else counts"

Not quite, because binder_dir takes top priority and determines how we check "if there is a Dockerfile". If a binder directory exists, we consider no files outside this directory, even Dockerfiles.
The logic (excluding Legacy) is more like:

resolve where binder files should be found (.binder, binder, top-level)
only within this directory, is there:

Dockerfile -> use it, ignore everything else
other buildpacks, etc.

which results in the effective priority:

binder/Dockerfile
binder/requirements.txt
/Dockerfile

i.e. the presence of binder/requirements.txt means top-level Dockerfile is and should be ignored. However, we currently special-case top-level Dockerfile matching the legacy Dockerfile pattern  as the actual first priority, taking precedence over the presence of the binder directory.

Should we add this special casing?

I think special-casing legacy makes sense, since it is, somewhat by definition, a special case. The goal of the Legacy buildpack is to keep some fraction of old pre-repo2docker Binder repos working, and not use any of the newer repo2docker logic in that case.
Stepping back, I think the logic for picking legacy should be:

Is this repo built for the old Binder, before repo2docker was a thing?

So the question is really, in the presence of a top-level Dockerfile that looks like it was built for the old Binder, does the presence of a .binder or binder directory indicate that the repo has been updated for repo2docker instead of the old Binder? It's ambiguous because we have an old Dockerfile but also a newer binder directory with other files.
Case for using Legacy in this situation:

it's technically possible to have created a repo with a dir called binder with no special meaning for the old binder,
so I could make a contrived case that would be broken by adding this and would need updating.

Case for not using Legacy in this situation:

an old repo had the Dockerfile for Binder v1, but was updated to work with repo2docker and this should be ignored until the legacy Dockerfile is removed

Now that I think of it, our current logic makes more sense than the change I proposed for two reasons:

only the repos with more recent activity need more changes to work as desired
because of the current logic, those repos don't work now, so probably don't exist, or at least aren't in use

To make this change, we would be enabling a new partial transition from Binder v1 to repo2docker without dropping support for the old way, which hasn't been operation for a couple of years now.


Problem with Sdcb.OpenVINO.runtime.centos.7-x64 version 2023.3.0

Error:
The type initializer for 'Sdcb.OpenVINO.Natives.NativeMethods' threw an exception.
System.TypeInitializationException: The type initializer for 'Sdcb.OpenVINO.Natives.NativeMethods' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Sdcb.OpenVINO.Natives.OpenVINOLibraryLoader' threw an exception.
---> System.DllNotFoundException: Unable to load native library: libopenvino_c.so.2320, dependencies status:
libtbb.so.12:94587538264256
libopenvino.so.2320:0
Unable to load native library: libopenvino_c.so.2310, dependencies status:
libtbb.so.12:94587538264256
libopenvino.so.2310:0

Files:

Hi,
You fixed OpenVINO, but PaddleOCR does not work!
Thanks.

Should be missing some deps, can try watch my video here: https://www.bilibili.com/video/BV1R64y1L7Sv/ (in Chinese)

The error is understandable:

The PaddleOCR assembly gives these files:

All dependencies need to be actualized:

Thanks for your information, yes according to your provided code, this seems an issue


Add sequence flow for main API greencheck traffic

This PR adds the documentation with sequence diagrams showing how data flows through the system for the majority of web traffic. We can't easily  render the images in this PR AND have them render in the docs when merged in, so please refer to issue #491 to see what the diagrams look like:
https://github.com/thegreenwebfoundation/admin-portal/issues/491

Hey @tortila  can you please cast an eye over this an merge in when done? It contains the sequence diagrams of the most common flows of data we need to think about.

Merging in after an in-person convo with Oliwia


[c++ grpc] Fix multi-slice deser. memory leak

The caller of grpc_byte_buffer_reader_next is responsible for calling
grpc_slice_unref on the slice. However, SerializationTraits::Deserialize
was only calling grpc_slice_unref on the last slice. Now, it is called
on each slice.
Also fixes a potential bug that would call grpc_slice_unref on an
uninitialized slice.

Since the CI systems are backed up, I ran builds and tests locally. They're passing.


Hopefully corrected formatting

This includes several minor changes, but I'm not sure if I'm using the right method

There appear to be conflicts to be resolved.

Hi Jeremy,
While you were working on your "master" branch in your fork somebody added some stuff to the "master" branch of incubator-netbeans-website.
This happens all the time: you start working on your branch and people keep adding stuff to the master branch of incubator-netbeans-website. When this happens you have to include other people's changes (in incubator-netbeans-website) in your branch first, and then do a pull request.
Your local reposity (i.e., the directory in your hard disk) has a "remote" git repository, this is usually called "origin". In your case this should look like https://github.com/JeremyCavanagh/incubator-netbeans-website.git You can verify this by using the "git remote -v" command.
What we do is tell your hard disk local repository about the Apache incubator-netbeans-website. We do this only once, like so:
git remote add upstream https://github.com/apache/incubator-netbeans-website.git

Then if you check your remotes again (git remote -v) you'll see that you have two remotes: "origin", pointing to https://github.com/JeremyCavanagh/incubator-netbeans-website.git and "upstream", pointing to https://github.com/apache/incubator-netbeans-website.git.
Now to the point: in order to fetch stuff other people have been doing in incubator-netbeans-website, you do this:
git fetch upstream

(this fetches all branches from upstream, i.e., from https://github.com/apache/incubator-netbeans-website.git and stores these branches in a hidden directory in your hard disk)
And then we "merge" these changes with the ones you've been doing in your hard disk (in the branch you're working on):
git merge upstream/master

Git might complain that there're some changes to the files in your hard disk that are incompatible. This is called a "merge conflict". If so then you have to open the files and review them manually.
Feel free to ask any questions you may have. Some other instructions are available here: http://netbeans.apache.org/participate/submit-pr.html
Cheers,
Antonio

Sorry Everyone,
More complete ignorance of how things work. I have run through the changes I made and corrected them. It wasn't someone else Antonio it was 'me', thanks for information very helpful, I'll try not to make any more mistakes, I probably will though.
Regards to one and all
Jeremy

Thanks for your perseverance! When we merge this, what are the maib changes we should see live in the codereference tutorial?

Thanks for the great work. Though note the first table seems to cause a big white space above it:
https://netbeans.apache.org/kb/docs/java/editor-codereference.html

I had noticed that. The problem is not knowing how the conversion from asciidoc to html is done and how the TOC is inserted.
However, I'm sure the solution is not so difficult and can be revised later.

I have had a quick look at the next two tutorials in the series and think there might be problems.

The first, https://netbeans.apache.org/kb/docs/java/code-inspect.html

Investigating what jsr305-2.0.0 is I came a cross this reference:
https://github.com/google/guava/issues/2960

Should I not worry about it and continue with a revision?

The second, https://netbeans.apache.org/kb/docs/java/editor-inspect-transform.html

The section "Using Configurations" includes references for migrating to JDK5, JDK 7 and JDK 8

I also noticed that these are included in NetBeans 10. This seems strange to me, especially as there is no migrate to JDK 11.

Again, should I not worry and continue with a revision.

Your thoughts would be greatly appreciated.

Regards

Jeremy

Message from 23/02/19 15:54
From: "Geertjan Wielenga" > To: "apache / incubator-netbeans-website"  > Copy to: "JeremyCavanagh" , "Mention" > Subject: Re: [apache / incubator-netbeans-website] Hopefully corrected formatting (# 319) > >
Thanks for the great work. Though notes the first table seems to cause a big white space above it:
https://netbeans.apache.org/kb/docs/java/editor-codereference.html

You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/apache/incubator-netbeans-website","title":"apache/incubator-netbeans-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/apache/incubator-netbeans-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@geertjanw in #319: Thanks for the great work. Though note the first table seems to cause a big white space above it:\r\n\r\nhttps://netbeans.apache.org/kb/docs/java/editor-codereference.html"}],"action":{"name":"View Pull Request","url":"https://github.com/apache/incubator-netbeans-website/pull/319#issuecomment-466658902"}}}[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/apache/incubator-netbeans-website/pull/319#issuecomment-466658902", "url": "https://github.com/apache/incubator-netbeans-website/pull/319#issuecomment-466658902", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

In the 2nd, you'll see "Not all releases of the JDK introduce new language features."
Indeed, some people could use Apache NetBeans 10 or 11 to create applications that involve upgrading code from JDK 4 or 5 or whatever.

That text could be more prominent or larger, whatever you think is best, for this precise reason i.e. others may wonder about the same.


[BUG]: Documents with Chinese filenames will appear as garbled text when uploaded.

How are you running AnythingLLM?
Docker (local)
What happened?
Documents with Chinese filenames will appear as garbled text when uploaded.

Are there known steps to reproduce?
No response

Same problem


Web - Unexpected error when UserB sends multiple messages and UserA selects "Admins only" for posting permissions

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login with userA
Navigate to the "New room" section
Enter room name and select userA workspace
Set visibility to "Public"
Click on "Create room"
Go to the room Details > Share code
Copy the room URL to the clipboard
Return to settings and clicked on "Who can post"
Now open a different browser and login with userB
Join the room by pasting the URL
Send 1-9 messages
Go back to the userA account
Select "Admins only" for the "Who can post"

Expected Result:
When UserB sends multiple messages and UserA sets the posting permissions to "Admins only," there should be no unexpected error displayed
Actual Result:
An unexpected error is displayed when UserB sends multiple messages and UserA sets the posting permissions to "Admins only"
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.31-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/b3515afe-17fd-475b-b9f4-36f4b4959e00
https://github.com/Expensify/App/assets/93399543/0b13535d-e980-468a-b694-dde99b9e19b0
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687472329701279
View all open jobs on GitHub

Hmm, it makes sense that the error would show if the messages haven't been sent to the server yet. But if the server had already saved the messages, it's weird that a message would show later.
cc @amyevans in case this is on your radar at all. I'll try to test and see what scenarios it's happening in.

This isn't something that was previously on my radar. It looks like the server must have received messages 1-4, then the UpdateReportWriteCapability API command, then messages 5-9, although you could probably find logs to confirm. I kind of forget what recent pusher updates we've made... was there something about waiting to deliver pusher events in a batch that might be making the composer disappear later than it should for User B? (Or am I making that up and the pusher changes were something else?)

Thanks @amyevans.
I just tried re-creating this and it worked just fine. I think what is happening is that @ayazhussain79 has switched to admins-only before the API commands to add those comments have completed. Which is why they end up failing. That doesn't feel like a bug to me. In the rare scenario where someone flips that setting at the same time as someone else has sent a message, it would cause an error. Which feels like the proper behavior.
If you wait for the API commands to complete before changing the setting, then no error messages are shown. Also, the composer disappeared for me just fine on the non-admin account when I changed the setting to admins-only.

I'm going to go ahead and close, since I don't think this is a bug, but feel free to continue the discussion here if you disagree!

@puneetlath @amyevans You can check User B has already sent messages, but User A is receiving them late. User A should receive all the messages that User B has already sent because User A changed post permission to "Admins only" when user B sent all messages
https://github.com/Expensify/App/assets/56740856/20161bdc-c2b4-406c-8a5f-c9df31a5fc98

@puneetlath  it is more effective to remove or gray out unsend messages when the posting permission is changed to "admins only" This simple approach will not show unexpected errors and clearly indicates that messages have not been sent

They are grayed out. Along with an error message indicating why they failed to send. I think what we have right now is fine and in-line with our error message patterns.


Total Request Units is not throughput

This page introduces confusion bw Total Request Units and throughput.
Request Units is a cost, much like Total Requests and not throughput.
See the below quote.

By default, the throughput data is aggregated at one-minute interval.

The second ambiguity is about the aggregation of this metric: The aggregation type needs to be specified as an avg over one minute is all too different than a max. I suppose in this case it is Count as defined here,
Third, the charts in Azure portal are using both Count and Sum, is there any difference bw the two aggregations?
Thanks

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

ID: 9ac8cba1-4317-a0b7-395e-c880cdbc7dbd
Version Independent ID: e46d7e04-d5b1-57f8-ee04-a91feee04e59
Content: Monitor the throughput usage of an operation in Azure Cosmos DB
Content Source: articles/cosmos-db/monitor-request-unit-usage.md
Service: cosmos-db
GitHub Login: @StefArroyo
Microsoft Alias: esarroyo

@ciufudean Thank you for the feedback. We are actively investigating and will get back to you soon.

#assign:seesharprun
Hello @ciufudean! The term throughput is purposefully used here as request units are commonly referred to as the "currency of throughput" in Azure Cosmos DB. In the screenshots and text, it's indicated that total RUs is being integrated on a time interval, which fits the definition of throughput for Azure Cosmos DB.
At this time, I don't believe there are any action items to take on this specific article. Changing the article to de-emphasize throughput would put it out of alignment with the RU conceptual article.
But, I do have two suggestions:

If you want to discuss the distinction between throughput and RUs in detail, I recommend posting on the Q&A forum for Azure Cosmos DB.
If you believe that you have language that would make this article clearer, I invite you to edit the article and submit a PR.

Thank you for taking time to discuss this topic with us.
#please-close


Update --infer-tsconfig to skip the allowJs option when there exist TS files

Fixes #87. Previously, we always included the allowJs option when
using --infer-tsconfig. However, this behavior was undesirable because
TypeScript package repos include a large amount of generated JavaScript
code that should not be indexed.  This commit changes the behavior so
that we only use allowJs when the project doesn't have any TypeScript
files.
For example, the npm/typescript package (for the TypeScript compiler
itself) times out when we index with allowJs while it completes in
a few seconds without allowJs.  It's OK to skip the JavaScript files
since the TypeScript files include the definitions for the JavaScript
code.
Test plan
Added new inferTsConfig.test.ts file.

Gonna go ahead and merge this since @varungandhi-src is on sick leave today and tomorrow. Happy to address review comments after merging.

The existing snapshot test can be kept as is. I covers the use-case where we want a pure JS project without tsconfig to index. It was probably overkill to add dedicated tests for this but I liked having the option to tweak this behavior in isolation down the road.


Add support for externally-managed prolog and epilog scripts

Forward-port #50 from v5 to add externally-managed prolog/epilog script support to v6

This has been tested with a blueprint that contains setup instructions identical to documentation:
tpdownes_google_com@slurm0a3p-controller:/opt/apps/adm/slurm$ ls -lh
total 24K
drwxr-xr-x 2 root root 4.0K Apr 22 20:54 etc
drwxr-xr-x 2 root root 4.0K Apr 22 20:54 logs
drwxr-xr-x 2 root root 4.0K Apr 22 20:54 partition-a3-epilog_slurmd.d
drwxr-xr-x 2 root root 4.0K Apr 22 21:12 partition-a3-prolog_slurmd.d
drwxr-xr-x 2 root root 4.0K Apr 22 21:12 scripts
lrwxrwxrwx 1 root root    9 Apr 22 20:54 slurm_epilog -> slurm_mux
-rwxr-xr-x 1 root root 1.6K Apr 22 20:54 slurm_mux
lrwxrwxrwx 1 root root    9 Apr 22 20:54 slurm_prolog -> slurm_mux


Compiling issue: 5:29-36 Critical dependency

I got this error massage in Chrome:
Error: Bootstrap tooltips require Tether (http://tether.io/) app.js line 4049 > eval:674:45
[WDS] Warnings while compiling. index.js:147
./src/assets/plugins/tether/dist/js/tether.js
15:29-36 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ./src/assets/plugins/tether/dist/js/tether.js  @ ./src/main.js  @ multi (webpack)-dev-server/client?http://localhost:8080 webpack/hot/dev-server ./src/main.js
What I am trying to do it to is to convert a .html file (a static page) to a project with webpack(vue-cli)
<script src="assets/plugins/jquery/dist/jquery.min.js"></script>
<script src="assets/plugins/tether/dist/js/tether.min.js"></script>
<script src="assets/plugins/bootstrap/dist/js/bootstrap.min.js"></script>
<script src="assets/plugins/slick-carousel/slick/slick.min.js"></script>
So here I put these codes on the top of my main.js file:
import './assets/plugins/jquery/dist/jquery.js'
import './assets/plugins/tether/dist/js/tether.js'
import './assets/plugins/bootstrap/dist/css/bootstrap.min.css'
import './assets/plugins/bootstrap/dist/js/bootstrap.min'
I don't see any solutions anywhere.  I found similar problem in #274

You should upgrade to a stable Bootstrap release. They don't use Tether anymore


Allow openssh-rs backend

Based on https://github.com/jonhoo/tsunami/pull/23, so that should go first.

Hmm, this approach probably won't work, since the features won't be additive. If cargo ends up enabling both (say, because one dependency has one and another one the other), then the crate won't compile. I'm also not sure we want to provide a choice. I think we should probably just provide openssh.

I'm also not sure we want to provide a choice. I think we should probably just provide openssh.
Fair enough - I'll close this and re-open one with just the openssh part.


Request for permissions ((java.io.FilePermission "<>" "execute")) Security Risk ?

I have looked at the library again and it request for that permission. I believe its a security risk. Can it be dealt away with ?

documents4j does of course need to access files. It needs to execute scripts which is why this is required. documents4j does not expose any such routines so it is safe to give this permission.

When the policy file is in the context of document4j alone then its definitely okay but document4j is however being used in a document app for Mendix that requires a policy file to be defined for the entire application and hence adding the permission exposes the entire application to any other jar file to use the same permission. so if jar files are not  cautiously added then someone can take advantage. I will ask a similar question in the mendix groups and get response


Keep MARSKernel internals within a single translation unit

Codecov Report

Merging #719 into master will increase coverage by <.01%.
The diff coverage is 90%.

@@            Coverage Diff             @@
##           master     #719      +/-   ##
==========================================
+ Coverage   93.89%   93.89%   +<.01%
==========================================
  Files          59       58       -1
  Lines        1802     1803       +1
==========================================
+ Hits         1692     1693       +1
  Misses        110      110

Impacted Files
Coverage Δ

simulator/kernel/kernel.h
100% <ø> (ø)
:arrow_up:

simulator/kernel/mars/mars_kernel.cpp
92.1% <100%> (+1.19%)
:arrow_up:

simulator/kernel/kernel.cpp
71.42% <80%> (ø)
:arrow_up:

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 08539f0...5545a40. Read the comment docs.


ngast: maintenance release

$ dart analyze ngast
Analyzing ngast...
No issues found!

Looks good to me. Thanks!


dibs: I will implement exercise run-length-encoding

@yonivy Thanks so much for doing this.  You've implemented all the canonical tests, and a nice clean example solution as well.
One request: you're missing a few semicolons, and the "house style" here is to include them everywhere they are normally required.  Can you fix that up, and then I would think we're ready to merge your contribution!

@matthewmorgan no problem. A few semicolons coming right up

@matthewmorgan do we have any "house style" linter config?

@yonivy sadly, no!  This project isn't currently using linting at all.  I think that would be a good addition...know anyone who would be interested? ;) The ecmascript track uses it.

Speaking of house style,  we usually like to have one commit per merged PR.  I should have squashed your commits...my bad.
Thanks again for your contribution!


CITE-seq COUNT cell number

Hi,
I am using CITE-seq COUNT for ADT and HTO analysis and couldn't get the correct number of cells defined. (And it worked before but not anymore...)
Below is the script used:
CITE-seq-Count -R1 ADT_HTO_tag_R1.fastq.gz -R2 ADT_HTO_tag_R2.fastq.gz -t /home/chenx302/Xiao/XC7_hashing/XC7_libraries_tag_CITE.csv -cbf 1 -cbl 16 -umif 17
-umil 28 -cells 11496 -wl /home/chenx302/Xiao/XC7_hashing/XC7_WHITELIST_antibody -o ~/Xiao/XC7_hashing/XC7_hashing/outs/fastq_path/tags_fastqs/CITE_SEQ_04122
019

The WHITELIST contains 11496 rows and I also '-cells 11496'. However the barcodes.tsv in umi_count only contains 11484 rows.
Any idea why?? I got the proper number of rows before with the same files. But now I merged all the R1.fastq from different NextSeq lanes and the same for R2.fastq and it stopped working. Can CITE-seq COUNT handle multiple R1 R2 entries? I did the below script previously but it seems like the output from the last file overwrite the previous.
R1="ADT_tag_S2_L001_R1_001.fastq.gz ADT_tag_S2_L004_R1_001.fastq.gz HTO_tag_S3_L003_R1_001.fastq.gz ADT_tag_S2_L002_R1_001.fastq.gz HTO_tag_S3_L001_R1_001.f
astq.gz HTO_tag_S3_L004_R1_001.fastq.gz ADT_tag_S2_L003_R1_001.fastq.gz HTO_tag_S3_L002_R1_001.fastq.gz"

R2="ADT_tag_S2_L001_R2_001.fastq.gz ADT_tag_S2_L004_R2_001.fastq.gz HTO_tag_S3_L003_R2_001.fastq.gz ADT_tag_S2_L002_R2_001.fastq.gz HTO_tag_S3_L001_R2_001.f
astq.gz HTO_tag_S3_L004_R2_001.fastq.gz ADT_tag_S2_L003_R2_001.fastq.gz HTO_tag_S3_L002_R2_001.fastq.gz"

arr=($R1)
arr2=($R2)

for i in {0..7}
do
       CITE-seq-Count -R1 ${arr[i]} -R2 ${arr2[i]} -t /home/chenx302/Xiao/XC7_hashing/XC7_libraries_tag_CITE.csv -cbf 1 -cbl 16 -umif 17 -umil 28 -cells 114
96 -wl /home/chenx302/Xiao/XC7_hashing/XC7_WHITELIST_antibody -o ~/Xiao/XC7_hashing/XC7_hashing/outs/fastq_path/tags_fastqs/CITE_SEQ
done

Hello @notimenocall
Could you check if the report gives you a value of 12 for the field "uncorrected_cells"?
Also, can you tell me which version you're using vs the one before?

Hi @Hoohm ,
Yes.
Running time: 27.0 minutes, 33.09 seconds
CITE-seq-Count Version: 1.4.2
Reads processed: 55054608
Percentage mapped: 96
Percentage unmapped: 4
Uncorrected cells: 12
Correction:
        Cell barcodes collapsing threshold: 1
        Cell barcodes corrected: 175408
        UMI collapsing threshold: 2
        UMIs corrected: 665030
Run parameters:
        Read1_filename: ADT_HTO_tag_R1.fastq.gz
        Read2_filename: ADT_HTO_tag_R2.fastq.gz
        Cell barcode:
                First position: 1
                Last position: 16
        UMI barcode:
                First position: 17
                Last position: 28
        Expected cells: 11496
        Tags max errors: 2
        Start trim: 0

How to correct for this please?

There is no error here. The 12 cells that are uncorrected are aggregated cells and should be filtered out. If you still want the uncorrected UMI counts for them you can get them in the uncorrected_cells folder as dense_umis.tsv
Version 1.4.3 added this to fix the long hanging of the UMI correction. If you get a TAG/HTO/ADT in one cells with over 20'000 different UMIs, this cell won't be corrected.
It might change in the future.

The umi_count could not be added as a seurat assay object if the cell numbers are not identical correct? How would you recommend doing it in this case?

I would subset the original seurat object and get rid of the uncorrected cells. Then add the assay as usual.

Thanks a lot. Really appreciate it!


UnfoldAdminSingleDateWidget calendar picking up wrong year if used different format

class BaseUnfoldMixin:
    formfield_overrides = {
        models.TextField: {
            "widget": WysiwygWidget,
        },
        models.DateField: {
            "widget": UnfoldAdminSingleDateWidget(
                format="%m-%d-%Y",
                attrs={
                    "placeholder": "MM-DD-YYYY",
                },
            ),
            "input_formats": ["%m-%d-%Y"],
        },
    }

For the above code, it displays the date in 'mm-dd-yyyy`.  But the calendar widget shows year 1910.

But commenting the format="%m-%d-%Y" and the date format back to yyyy-mm-dd shows the correct year.

Just noticed that setting the date format might bring more issues.  With current dd-mm-yyyy format, selecting a date from the Calendar widget or Today button, would input the date in yyyy-mm-dd format.

Also, the calendar widget highlights today's date in circle and not the input value's.

Did you updated DATE_INPUT_FORMATS in settings.py? Please create a minimal repo where I can reproduce the issue because right now I'm not able to see all the settings and dependencies.


Attempt to fix flakey test in document-collections.feature

Trello: https://trello.com/c/bVMUgKC9
The following test has been failing intermittently on CI for a number of weeks:
Unable to find button "Update tags" that is not disabled (Capybara::ElementNotFound)
./features/step_definitions/document_collection_steps.rb:148:in `/^I redraft the document collection and remove "(.*?)" from it$/'
features/document-collections.feature:33:in `I redraft the document collection and remove "May 2012 Update" from it'

Based on the debug added in PRs 7698 and 7713 I'm fairly confident that the test fails when the "Yes - information has been added, updated or removed" radio button is selected but the Change note textarea isn't visible. This causes the saving of the edition to fail because the change note can't be blank.
Previously the test attempted to fill the Change note if the textarea was visible on the screen (using fill_in_change_note_if_required). Presumably based on the assumption that if the "Yes - information has been added, updated or removed" radio button is selected (because Edition#minor_change? is false) that the change note textarea will be visible. However, the change note textarea is conditional and therefore hidden by default until some JavaScript makes it visible. My theory is that there was a race condition in this test that meant it would fail intermittently depending on whether the JavaScript had executed and made the textarea visible before the call to fill_in_change_note_if_required.
By explicitly choosing "Yes - information has been added, updated or removed" and then filling the change note textarea (whose appearance Capybara should wait for by default) I hope to avoid the race condition.
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

Thanks, @callumknights :+1:


remove double api call for tags in tag interface and adminview

maybe try to pass tags in?

or pass the function in!


⚠ ESPN has degraded performance

In 0ec96c1, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 2664 ms

Resolved: ESPN performance has improved in 13d3aa9.


added "details" option to collection figures

Scope & Purpose
Added details option to figures command of a collection: collection.figures(details)
Setting details to true will return extended storage engine-specific details to the figures. The details are intended for debugging ArangoDB itself and their format is subject to change. Currently, the details are returned for the RocksDB storage engine only.
By default, details is set to false, so no details are returned and the behavior is identical to previous versions of ArangoDB.
Enterprise companion PR: https://github.com/arangodb/enterprise/pull/545

[ ] :hankey: Bugfix
[x] :pizza: New feature
[ ] :hammer: Refactoring
[x] :book: CHANGELOG entry made
[x] :muscle: The behavior in this PR was manually tested
[x] :computer: The behavior change can be verified via automatic tests

Backports:

[x] No backports required
[x] Backports required for: 3.7, 3.6

Testing & Verification

[ ] This change is a trivial rework / code cleanup without any test coverage.
[ ] This change is already covered by existing tests, such as (please describe tests).
[x] This PR adds tests that were used to verify all changes:

[x] Added new integration tests (i.e. in shell_server / shell_client)

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11781/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/11791/


onSaved: (value)  not working

onSaved: (value) {               print('The value is $value');             }
not working

sorry I can't still make it work, don't see any differences


PR for issues #2, 3, 4, 5, 8, 9

Checklist:

[ ] Reviewers confirm new code works as expected.
[ ] Tests are passing.
[ ] Coverage does not decrease.
[ ] Documentation is updated.

Noted, thanks @csookim


more control flow for Rune

Handle isn't enough for to translate JS flows into Rune without being forced to use the .unhandle .rehandle pattern
Necessary control flows
The handle function is great for branching your code based on a condition, but right now it doesn't cover all the very basic control flows JS offers. I'd like it to cover all use cases: if/elseif/else, , exhaustive switch (#624), and error handling. We could also add some new operators to make common flows easier: && ?? value! ?.
Why we need more conditionals:
handle() is not enough to avoid using .handle() and .unhandle(), since in some of the most common scenarios that this pattern was needed (for a lack of alternative) was when the user would be trying to reproduce a "if true do x, else do y".
// vanilla TS
const settings = props?.mintSettings?.defaultItemSettings
const defaultItemSettings = settings ? $settings.encode(settings) : 0n

// Rune
const settings = props.access("mintSettings").access("defaultItemSettings")
const defaultItemSettings = settings
  .unhandle(undefined)
  .chain($settings.encode)
  .rehandle(undefined)
  .handle(undefined, () => 0n)

If we were to try to use only handle (without the .unhandle .rehandle pattern):
const defaultItemSettings = settings.handle(undefined, () => 0n).chain($settings.encode)

This would give a type error, since after handle the type of the value is no longer Settings | undefined, it becomes bigint | Settings which cannot be used on $settings.encode. This could easily be fixed with some kind of else method:
const defaultItemSettings = settings.handle(undefined, () => 0n, /* else */ $settings.encode) // typechecks correctly as bigint

I would suggest a more advanced handle/match:
settings.handle(undefined => ...)
settings.match(
  handle((v) => ...) // if
  handle((v) => ...) // else if
  otherwise((e) => ...) // else
)

and maybe some helpers for operator shortcuts
settings.handle(truthy, () => ...) // &&
settings.handle(falsy, () => ...) // ||
settings.access("a", "b") // settings?.a?.b

I'm not sure about the names, the format, or even satisfied on how it looks, but I still think it is essential for rune to be able to express all the conditional control flows used in JS in more intuitive way than unhandle rehandle

Note: this is mostly important pattern lib developers who need to build their program completely inside capi, normal users wouldn't need to use these

The handle function [...] doesn't cover all the very basic control flows JS offer

I don't think an exhaustive match / version of handle is a key requirement atm considering that the result of a handle call is a rune, which will usually be supplied to another rune factory (and therefore type-checked against the given parameter).

since in some of the most common scenarios...

Can you please provide some specific examples from our domain (ideally from FRAME pallets). This way we'd have something specific to contemplate/design.

// vanilla TS
const settings = props?.mintSettings?.defaultItemSettings
const defaultItemSettings = settings ? $settings.encode(settings) : 0n

You're right... this is a bit of a pain point at the moment. Hopefully we can get rune.access to respect optionals so that we could do the following.
const settings = Rune
  .resolve(props)
  .access("mintSettings", "defaultItemSettings")
  .handle(undefined, () => Rune.resolve(0n))

Can you please provide some specific examples from our domain (ideally from FRAME pallets). This way we'd have something specific to contemplate/design.

Hopefully we can get rune.access to respect optionals so that we could do the following.

The initial example is a use case where the problem is not accessing optionals, but using a if/else flow (which currently can only be represented in .unhandle .rehandle
Being able to .access("mintSettings", "defaultItemSettings").handle(undefined, () => Rune.resolve(0n)) would not solve this example, since what we want to do is apply $settings.encode if the Settings object is present, and if not then return a 0n bigint default
The reason why this is a common problem is that it doesn't appear only when doing something based on if something is undefined or not, but in any case where you want to do something based on a condition (you could replace settings the first example with any variable that you'd want to treat differently based its value

Being able to .access("mintSettings", "defaultItemSettings").handle(undefined, () => Rune.resolve(0n)) would not solve this example, since what we want to do is apply $settings.encode if the Settings object is present

Ah, yes: seems I glossed over that. How's this then?:
const $settings = CodecRune.from($c)
const settings = Rune
  .resolve(props)
  .access("mintSettings", "defaultItemSettings")
  .handle(not(undefined), $settings.decoded)
  .handle(undefined, () => Rune.resolve(0n))

We don't have the not/guard-building helpers as of yet, but it should be simple enough. I'd imagine that––in most cases––devs will want a given Rune to resolve to a somewhat consistent shape. Too much branching shouldn't usually happen from Runes higher in the tree. But who knows?! For cases where one wants to represent such Runes, I still think handle and guards will be sufficient. If you disagree, please follow up on my earlier question:

Can you please provide some specific examples from our domain (ideally from FRAME pallets). This way we'd have something specific to contemplate/design.

We'll likely solve this in the same way as #624

Resolved as of #1078


Incorrect theme is loaded for i18n locales when activating

Issue Summary
Ghost appears to load locales from the old theme folder when activating a new theme.
To Reproduce

Set up a clean 3.35.5 site
Change the site locale to it (Italian) from Settings
Upload a theme with a locales/it.json file
Activate that theme
See that the translations are not working by checking the site

I've only briefly debugged, but activeTheme (below) is referring to the old theme name, which causes it to look up the wrong path and falls back to the en.json text. Possibly the i18n is being re-inited before settings cache has been updated or something (?)
https://github.com/TryGhost/Ghost/blob/d81b9c93b24d8218464925f335c956db05d0f267/core/frontend/services/themes/i18n.js#L23
I've reproduced this in 3.10.0 so it's not a new bug. Workaround is to restart Ghost which will cause it to load the correct locales.
Technical details:

Ghost Version: 3.35.5
Node Version: 12.18.0
Browser/OS: Firefox/Linux
Database: SQLite

The issue here spurs out of settings cache being updated after the even triggering i18n service to reload. Specifically this line: https://github.com/TryGhost/Ghost/blob/d81b9c93b24d8218464925f335c956db05d0f267/core/server/api/canary/themes.js#L40
sets a correct value to active_theme, but the event: https://github.com/TryGhost/Ghost/blob/d81b9c93b24d8218464925f335c956db05d0f267/core/frontend/services/themes/activate.js#L19
that triggers init method in ThemeI18n, is coming before settings cache has a chance to be corrected.
I think the best approach here would be to reduce dependency on settingsCache in i18n service and rely on the information coming with the event itself - would need to add current theme name when emitting services.themes.activated event. Possibly we could go even further and rely on ActiveTheme service instead of settingsCache to load up theme's name. The reason for this is that architecturally we are aiming to have as little dependencies on "server" services inside of "frontend".