Implement offline write

[ ]  Add WRITE support when offline
[ ] Queue writes when offline
[ ] Automatically push any local changes as soon as device comes back online
[ ] Send global notification to let user know data changed

One of the requirements of the offline read issue #30 is that a resource local path should match its selfLink; for example a resource with the selfLink dbs/1KtjAA==/colls/1KtjAImkcgw== will be locally cached at a location similar to /Applications/.../Caches/dbs/1KtjAA==/colls/1KtjAImkcgw==.
The selfLink is made of resourceIds and when it comes to offline write, because it's not yet saved in the remote database, it doesn't have a resourceId and a selfLink.
Alternatively, we could use the user generated ids and altLinks?
@colbylwilliams @NateRickard

I have an initial implementation for this in the branch feature/73-offline-write. It's not ready yet but posting the general design decisions here for documentation, feedback and discussion.
Overview
On a high level, when a user tries to write a resource while the network is not reachable, a unique resource ID is generated and assigned to the resource (if necessary). The resource is saved locally and metadata about the write operation is persisted so that the operation can be replayed once the network becomes reachable. Once the network becomes reachable, all write operations are performed and the previously saved resources are replaced with their online counterparts.
Implementation
The implementation is based around 2 main data structures, Write and WriteQueue.
Write captures all the information and metadata necessary to retry a request when the network is reachable.
enum WriteType: String, Codable {
    case create
    case replace
    case delete
}

struct Write: Codable {
    let type: WriteType
    let resource: Data?
    let location: ResourceLocation
    let httpHeaders: [String: String]?
    let date: Date
}

Because it's a Codable, it can be persisted to disk.
The WriteQueue keeps an internal collection of Write objects while the network is not reachable and performs them when it becomes reachable. It persists the Write objects to the disk when the app becomes inactive or is terminated and reloads them at startup.
class WriteQueue {
    static var shared = WriteQueue()

    // Performs all the `Write` operations online.
    func sync()

    // Persists the `Write` operations to disk.
    func persist()

    // Loads the `Write` operations from disk.
    func load()
}

It also has the helper functions addCreateOrReplace and addDelete.
// Performs a `create` or `replace` operation if the network is reachable.
// If not, creates a `Write` object, enqueues it and performs it as soon as
// the network becomes reachable.
func addCreateOrReplace<T: CodableResource & OfflineWritable>(_ writeType: WriteType, resource: T, location: ResourceLocation, httpHeaders: HttpHeaders? = nil, callback: @escaping (Response<Data>) -> ())

// Similar flow as `addCreateOrReplace` but for `delete` operations.
func addDelete(forResourceAt location: ResourceLocation, httpHeaders: HttpHeaders? = nil, callback: @escaping (Response<Data>) -> ())

WriteQueue is then used in DocumentClient like this:
func createOrReplace<T: CodableResource & OfflineWritable> (_ resource: T, at resourceLocation: ResourceLocation, replacing: Bool = false, additionalHeaders: HttpHeaders? = nil, callback: @escaping (Response<T>) -> ()) {

    WriteQueue.shared.addCreateOrReplace(
        replacing ? .replace : .create,
        resource: resource,
        location: resourceLocation,
        httpHeaders: additionalHeaders,
        callback: { callback($0.resourceResponse()) }
    )
}


What's the proper way to kill a pipe()?

I have server code which serves as a download proxy:
request(streamingDownload)
.on('error', function(error) {
// do something })
.pipe(res);
Occasionally, the server receives an error event after having started to pipe the response to the client; therefore, I'd like to terminate the connection to the client to let the client know the response has gone bad -- it's too late to res.send a status code at this point since piping has already begun.
What's the best practice for doing that using this module?

right now im doing something like this ,
	request
		.get(url, function(err,response,body){
			if(err) callback(err,null);
			else if(!err && body){
				callback(null,'success: '+response);
			}
		})
		.auth(user,pass,true)
		.on('error',function(err){
			callback(err,null);
		})
		.pipe(stream);

It looks ugly I know, but I raised an issue for this already, #2153

I was trying to do something similar and found the nonstandard requestStreamInstance.abort() to work for this purpose.


Logging on RT1010 EVK

Has anyone tried the LOG=2 option on the imxrt1010_evk?
I do not see any activity on the UART when set LOG=2

Sorry, I was working with an older version.  The latest has logs.


Special case for file_names without paths

Performing change for profiling handling built-in functions similar to '('', 1, 'reraise')'. Thus profiler completely interrupted within impossibility unpack trace correctly

This fix is included in #20


微信群又满了！！

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
微信群又满了！！
Expected behavior
No response
System Info
No response
Others
No response

已更新


i18n(pt-BR): Update guides/typescript.mdx translation

Description (required)
Update the translation of i18n/guides/typescript.mdx

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

pt-br
guides/typescript.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Good work @viniciusdeliz, I have a few suggestions here!
Also, I can see we're missing the changes of a few commits:

6e5e00f
8267745
3dd99e0

Could you update your translation to include them? 🙌

Great review @yanthomasdev, I'm sorry for missing those.
Let me know if the file still requires changes and I'll promptly fix it.


[WFCORE-5042] Upgrade WildFly Elytron to 1.13.0.CR2

https://issues.redhat.com/browse/WFCORE-5042
https://issues.redhat.com/browse/WFCORE-5044
    Release Notes - WildFly Elytron - Version 1.13.0.CR2

        Component Upgrade

[ELY-1997] -         Upgrade jboss-logmanager to 2.1.16.Final

[ELY-1999] -         Upgrade JBoss Threads to 2.3.5.Final

[ELY-2003] -         Upgrading  jboss-logmanager to 2.1.17.Final

        Enhancement

[ELY-2000] -         Add additional TRACE logging in GssapiClient when obtaining credential using Callback

[ELY-2006] -         Add a "Delegating" PolicyContextHandler

[ELY-2007] -         Bring SecurityIdentity PolicyContextHandler inline with WildFly Core implementation.

[ELY-2008] -         Move JACC tests into JACC module

        Feature Request

[ELY-1879] -         Support SSH authentication for Git persistence

[ELY-1932] -         Support for multiple security realms - Distributed Identities

        Bug

[ELY-1982] -         TLS with BCJSSE Provider does not work

[ELY-2004] -         SPNEGO mechanism handles delegated credential twice.

[ELY-2009] -         Remove loadedIdentities from PrincipalDistributedIdentity since it is unused and correct PrincipalDistributedIdentity#dispose

        Task

[ELY-1951] -         Add version 1.6 of the Elytron client schema

[ELY-1984] -         Add a wrapper HttpServerAuthenticationMechanismFactory that sets the peer address using the current authentication request

[ELY-2005] -         Support for "Container Subject Policy Context Handler" should be in Elytron

        Release

[ELY-2010] -         Release WildFly Elytron 1.13.0.CR2

This contains some Elytron enhancements for RFEs but there are still follow up PRs against WildFly Core to follow.

Closing as I have addressed the merge conflict in this PR https://github.com/wildfly/wildfly-core/pull/4266


I have asn data structure file and .dat file. How can i decode asn?

You have mentioned this
With pyasn1 you can build Python objects from ASN.1 data structures. For example, the following ASN.1 data structure:
Record ::= SEQUENCE {
id        INTEGER,
room  [0] INTEGER OPTIONAL,
house [1] INTEGER DEFAULT 0
}
Could be expressed in pyasn1 like this:
"my question is , how can i generate code from a data structure"

Please use asn1late for that.


Feat/auth cookie update

[x] Updates setAuthCookie(req, res) to set sb-access-token and sb-refresh-token cookies.
[x] Updates getUserByCookie(req, res?) to automatically try and refresh the access token if expired. Note: this requires res to be passed!
[x] Introduces getAuthCookieString(req, res): string[] to make it easier to set auth cookies in frameworks that aren't supported by setAuthCookie. Closes #206

anything that stands out to you?

@thorwebdev What do the response headers look like?
When you say request, what is making the request and what is receiving the request?

Gotrue is making the request via http.Redirect in the callback route.
Next.js api route is receiving the request.

Gotrue is making the request via http.Redirect in the callback route.
Next.js api route is receiving the request.

When in doubt .... CORS?
Also, see Preflight Requests Block Cookies: https://medium.com/swlh/7-keys-to-the-mystery-of-a-missing-cookie-fdf22b012f09
With RedwoodJS's cookie dbAuth provider, ran into a case where CORS needed to be set https://github.com/redwoodjs/redwood/pull/4150

Based on my understanding of cookies, this approach doesn't work since the cookies returned by GoTrue will be associated with the GoTrue domain. GoTrue redirects to the given API route which is on a different domain. The browser will not send the cookies associated with the GoTrue domain to any other domain since that would trivially lead to exploitation.

@bnjmnt4n yes, you are correct, this approach only works if gotrue is running on the same domain.

@dthyresson would you mind testing the getAuthCookieString approach with your Fastify app?

Hey,
I'm missing a lot of context here, but I'm keen to see token refreshing for SSR type web apps.
What happens when the cookie tokens and the client side tokens become out of sync? For example when the token gets refreshed server side, and then the client also tries to refresh after the page loads.
Does the GoTrue backend allow the same refresh token to be used multiple times within a short period of time, making this a non-issue?
I spun up this PR locally, logged in, and then waited for my session to expire on the /profile route. After refreshing, the token refreshed server side no problem, but upon navigating back to the / route, it seemed I was logged out client side.
Please let me know if I can help out!

Yes, very good point @alaister, you will need to decide what your source of truth is. E.g. here you will always need to fetch the user from the server, e.g. via https://github.com/supabase/gotrue-js/blob/feat/auth-cookie-update/example/next-auth0-migration-example/pages/api/me.js
In the future we're planning to move fully away from using localStorage, but there are a couple things that need to happen first.


Feature Request: Multiple Projects

Can you please enable people to have multiple projects on one installation. That's the single most crucial different Pockerbase and Appwrite, with the later one you can have as many projects you want and your users, functions, databases do not mix.
Basically its just a overhead table that separates one project from another. But it makes users have PB as an incubator for many projects.

No, sorry this is not planned. You can also check https://github.com/pocketbase/pocketbase/issues/324, https://github.com/pocketbase/pocketbase/discussions/97#discussioncomment-3139409, https://github.com/pocketbase/pocketbase/discussions/180 and probably others.
It is better and easier to maintain a single project per database file.


MAINT: new collections and seqs auto-convert nucleic acid seqs

Summary by Sourcery
Enhance sequence and alignment creation functions to automatically convert nucleic acid sequences to the appropriate molecular type, and add tests to verify this behavior.
Enhancements:

Add automatic conversion of nucleic acid sequences to the appropriate molecular type in sequence and alignment creation functions.

Tests:

Introduce tests to verify the automatic conversion of nucleic acid sequences to the correct molecular type for both aligned and unaligned sequences.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 92.239%

Files with Coverage Reduction
New Missed Lines
%

src/cogent3/maths/scipy_optimize.py
3
84.92%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.008%

Covered Lines:
34218

Relevant Lines:
37097

💛  - Coveralls


AAP-27466: CVE-2024-37891 ansible-lightspeed-container: urllib3: proxy-authorization request header is not stripped during cross-origin redirects [ansible_automation_platform-2.4]

Jira Issue: https://issues.redhat.com/browse/AAP-27466
Description
Update urllib3 to (minimum of) 1.26.19
pyproject.toml is used to build downstream AAP.
Testing
N/A. Minor revision bump.
Production deployment

[x] This code change is ready for production on its own
[ ] This code change requires the following considerations before going to production:

I don't think we need to do that since the user may have valid reasons to use the older lib version that is compatible with us. Our pyproject.toml should only list the dependencies that we need to get our project to work as expected.

Hi @goneri

I don't think we need to do that since the user may have valid reasons to use the older lib version that is compatible with us.

It's a single point increment in the revision version.. but something RH are insisting to address the CVE.
We've bumped versions for lessor reasons. Why the sudden concern?

Our pyproject.toml should only list the dependencies that we need to get our project to work as expected.

pyproject.toml already lists urllib3.

Hi @goneri

I don't think we need to do that since the user may have valid reasons to use the older lib version that is compatible with us.

It's a single point increment in the revision version.. but something RH are insisting to address the CVE.
We've bumped versions for lessor reasons. Why the sudden concern?

Our pyproject.toml should only list the dependencies that we need to get our project to work as expected.

pyproject.toml already lists urllib3.

It's not a concern, the purpose of the requirements field is to trace the minimal requirements that we have to get our package to work properly. It's not to trace all the CVE of our dependencies. Having too tight version constraints will create different problems.
This is the standard procedure for most of the Python distributions and this is the reason why tools like pip-audit may be handy.


api image missing from store

Description:

I am performing export-import api operation on the same apim server, which results in success. Even I am able to publish it but when I visit the store, the icon of published api is missing.
Steps to reproduce:
export api
change api name, context and context template in api.json
import api
publish api
go to store
imported api should contain thumbnail api
Affected Product Version:

wso2-apim-2.2.0
Environment details (with versions):

OS: linux
Client:
Env (Docker/K8s):

Optional Fields
Related Issues:

Suggested Labels:

Suggested Assignees:

Hi ,
Can you log into the management console and check wether the image resource exists in it
You can find the image resource path by store image link as follows

AS en example If the image path is as below
https://<IP_ADDRESS>:9443/registry/resource/_system/governance/apimgt/applicationdata/icons/admin/PizzaShackNII/1.0.0/icon
Omit the following part https://<IP_ADDRESS>:9443/registry/resource and get the registry resource path as below
/_system/governance/apimgt/applicationdata/icons/admin/PizzaShackNII/1.0.0/icon
Then go to the registry browser and check whether the image exists there as below and get back to us. (You can click the download button and check)

You can log in to the management console with https://localhost:9443/carbon url along with admin user credentials.
Hoping to here the feedback from you since its working in my end.
Thanks
@prasa7


delete userIDs

What type of this PR
Add one of the following kinds:
/kind feature
What this PR does / why we need it:
delete userIDs
@recallsong

/approve


add modulus support

This PR is based on my communications with Modulus support http://help.modulus.io/customer/en_us/portal/questions/12745491--dirname?new=12745491
Fixes #16

Thanks a lot, @adamwong246 ! Great that you added a comment as well.
Do you mind adding some sentences to this section in the README as well?

@structuresound Can you revert that change? Since this PR is on the cusp of being approved, I don't think we need a custom email package anyways.

Agreed. Please revert to original name for this repo.
@adamwong246 Great! The numbered list in the README section won't render as Markdown though – you need some whitespace around it. Just a head's up.

@johanbrook the name of the package ahas been reverted and a line added to the README for proper markdown

Thanks! Merging.


How to get a list of running forever-monitor processes?

I am writing an app using forever-monitor. I want to get the same information that the forever app shows me when I do a forever list, but in a JavaScript object, inside the app.
I started digging through the forever code, and see it calls forever.list to do this. When I call that inside my app, it fails inside getAllProcesses, on the first line where it tries to do a forever.config.get ('sockPath').
I'm fumbling around in the dark. I'm looking for a simple way to do this. I can probably maintain much of this structure myself, but really would rather use the one that forever or forever-monitor must be keeping around.
Any help much appreciated. ;-)

I figured it out. Explained here..
https://github.com/scripting/Scripting-News/issues/18#issuecomment-318837832
Dave


Save files in local folder

Im working on a offline application where users can upload pictures. Uploaded files needs to be saved in a folder within my app.
How can i achieve this?

I don't know and this isn't in the scope of the library. Please ask this at StackOverflow.


the pretrained file link is disconnected

the "https://drive.google.com/uc?id=1R638ou1AMncTCRvrkQY6I-11CPwZy23T" for pretrained model is disconnected.
Could you please put a valid link? very thanks

The link is working fine for me. Maybe Google Drive is blocked in your country.

Maybe you can upload the zip data，because we are in Asia country,we can not use the anchor data.


Make miflora monitored_conditions parameter optional

Description:
If miflora monitored_conditions is not set default to monitoring all miflora sensors.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

👍

Managed to simplify it even more, no need for list either as default iterable of a dictionary is the keys 👍


2FA support

Is there any plans to add 2fa? This feature isn't possible to add by plugins (right now) due to required UI changes. Anyway, 2fa must be in verdaccio core.

@reklatsmasters I'm outdated about what we might do about 2FA with open source. Do you have any suggestion?

@juanpicado I think verdaccio should provide the same 2fa logic as npm:

2FA for login
ask 2FA for publish
require 2FA for publish per package

Of cource, this shouldn't break login from CI.

Ok, but I think we need more context here. What pieces are needed to achieve this?
I wonder how would be the connection verdaccio <---> token generator.   Since the primary registry is close code, who knows how they achieve that.  Any idea?

They (like most everyone else) achieve it by implementing something that follows RFC 6238. The gist of this RFC is that for a user, you generate a "secret". The user is shown this secret through some combination of text and QR code (generally just the QR code) which the user then plugs into some application (like Google Authenticator). Then, any time the user goes to login, you use that "secret" for the user to generate a token (using the RFC algorithm) and then check it against what the user puts in.
In term of how you'd want to implement it, you'd probably want to use something like (otplib)[https://www.npmjs.com/package/otplib] which wraps all of those details for you, but I've only started looking at this project so I have no idea where exactly this hookup would be in the verdaccio codebase.


Bug fix: the component is removed,But the event handler registered is…

fix bug: when the component is removed,But the event handler registered is still running.see Issue #13
Here is a demo: https://github.com/winnieBear/demo-show-react-webcomponentify-bug

Will this work also with Functional components (noting will break)? As well as components with React.memo?

Hi @winnieBear, thanks for your contribution. I've tested this in sandbox, and it works just fine.
Just for reference,

here is example with defect reproducible: https://codesandbox.io/s/modest-architecture-jly5y?file=/package.json:763-801
and here is an example with a fix: https://codesandbox.io/s/optimistic-butterfly-yn6ik?file=/package.json:763-855

@a7ul, feel free to release this. Thanks


HTML render with headless chrome + GPU hangs

I'm trying to get a screenshot of a webpage using puppeteer, it works fine with CPU but I had no success getting it working with GPU. Looking at puppeteer code it seems headless option turns off GPU altogether. Since I intended to generate a lot of images from HTML I was interested in knowing how much GPU would help.
I'm playing with the options being sent to Chromium directly using args object. and manipulating it so that it doesn't ask Chrome to  turn GPU processing off. Though the request is being accepted and chrome processes are spawned nothing happens after that , no data is returned and it times out after some time.
Steps to reproduce
Issue can be reproduced on try-puppeteer:
https://try-puppeteer.appspot.com/
With this code :
const browser = await puppeteer.launch({
                        headless : false,
                        args :[
                                '--headless',
                                '--hide-scrollbars',
                                '--mute-audio'
                        ]
                });

const page = await browser.newPage();
await page.goto('https://example.com');

console.log(await page.content());
await page.screenshot({path: 'screenshot.png'});

await browser.close();

Tell us about your environment:

Puppeteer version: 0.13.0
Platform / OS version: Windows 10 , Ubuntu 17.10 and whatever the appspot demo for try puppeteer uses.
URLs (if applicable): NA

What is the expected result?
A screenshot should be returned.
What happens instead?
The call hangs until its timed out.

I wouldn't try running headful chrome on try-puppeteer.appspot.com. But I notice you're using headless : false, and passing the  '--headless', flag at the same time :)
This script doesn't hang for me on mac, running from the terminal:
const browser = await puppeteer.launch({
  headless: false,
  args: [
    '--hide-scrollbars',
    '--mute-audio'
  ]
});

const page = await browser.newPage();
await page.goto('https://example.com');

console.log(await page.content());
await page.screenshot({path: 'screenshot.png'});

await browser.close();

The reason I'm using headless:false and '--headless' together is to make
puppeteer stop adding flags [which includes disabling GPU] when it
encounters headless:true.
I'll try your version of script [--headless removed from mine] and post.
Thanks for checking !
On Sat, Dec 16, 2017 at 9:12 AM, Eric Bidelman<EMAIL_ADDRESS>wrote:

I wouldn't try running headful chrome on try-puppeteer.appspot.com. But I
notice you're using headless : false, and passing the '--headless', flag
at the same time :)
This script doesn't hang for me on mac, running from the terminal:
const browser = await puppeteer.launch({
headless: false,
args: [
'--hide-scrollbars',
'--mute-audio'
]
});
const page = await browser.newPage();await page.goto('https://example.com');
console.log(await page.content());await page.screenshot({path: 'screenshot.png'});
await browser.close();
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/puppeteer/issues/1610#issuecomment-352196541,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC8A474RiQUyoXSChdqxgH9Lzkecrs9Qks5tA_oGgaJpZM4REIGM
.

--
Ragards,
Abhijeet J. Apsunde

Gotcha.  I tried your script and that also works for me on mac. No hanging. You could try adding the dumpio: true flag to see if that shows where the hang is occurring.
Related: https://github.com/GoogleChrome/puppeteer/issues/872

Thanks Eric,
I can confirm this works on Mac , with iodump:true on windows I get following errors :
[1218/105906.588:ERROR:browser_gpu_channel_host_factory.cc(124)] Failed to launch GPU process.
[1218/105906.588:ERROR:gpu_process_transport_factory.cc(1009)] Lost UI shared context.
[1218/105906.767:ERROR:command_buffer_proxy_impl.cc(118)] ContextResult::kFatalFailure: Shared memory handle is not valid

With same settings Ubuntu still hangs but I didn't see the error logs I pasted from Windows.

Hey @ebidel I stumbled upon a document authored by you headless chrome which talks about --gpu-disable for some older versions of chrome [not that old, but early 2017]. You mentioned the limitation will eventually go away, no definite timeline though.
Do you think issue I'm seeing on Windows and Ubuntu is because of something that is yet to be addressed in Chrome ?


[CARBONDATA-1179] Improve the Size calculation of Objects being added and managed in LRU cache

Can one of the admins verify this patch?

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2499/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/380/Failed Tests: 3carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-spark-common-test: 3org.apache.carbondata.spark.testsuite.partition.TestDataLoadingForPartitionTable.data loading for partition table: range partitionorg.apache.carbondata.spark.testsuite.partition.TestDataLoadingForPartitionTable.Insert into for partition table: range partitionorg.apache.carbondata.spark.testsuite.partition.TestQueryForPartitionTable.detail query on partition table: range partition

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/128/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2702/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/627/Failed Tests: 1carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-core: 1org.apache.carbondata.core.cache.dictionary.ReverseDictionaryCacheTest.testLRUCacheForKeyDeletionAfterMaxSizeIsReached

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/160/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2736/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/161/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2737/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/666/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/665/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/198/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2777/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/707/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/205/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2784/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/714/Failed Tests: 1carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-core: 1org.apache.carbondata.core.cache.dictionary.ReverseDictionaryCacheTest.testLRUCacheForKeyDeletionAfterMaxSizeIsReached

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2786/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/207/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/716/

LGTM


switched to github.com/lestrrat-go/jwx/v2

Hi,
I made the minimal required changes to adopt this middleware implementation to jwx/v2 . Tests pass. Hopefully this will suffice for merging the changes.
Cheers,
Shmul

Just minor changes, but it definitely helps. Specially since it's v2 of the jwx library the one getting updates. I hope this one get merged.

Hey guys, any progress with this merge? :)


After import from gitter: "Error saving edit"

Zulip server version 2.1.4
downloaded from https://www.zulip.org/dist/releases/zulip-server-latest.tar.gz
(This error occurs on the released version above and without the PR #14825)
Problem:

When editing the topic of a message which is old enough, at validation time, as an admin, with the option Allow message editing: Any time, I get the error message.
Error saving edit: Invalid message(s)
When I try getting messages using the rest API through python-zulip-api, I get far less messages than expected:

import zulip
client = zulip.Client(config_file="~/.zuliprc-just-coq")
len(client.get_messages({'num_before':4000, 'num_after':0,'anchor':1000000000})['messages'])
# Out: 287
client.get_messages({'num_before':1, 'num_after':0,'anchor':1000000000})['messages'][0]['id']
# Out: 91163

while
$ cat coq/messages-*.json | grep "subject" | wc -l
# 91206

(coq/messages-*.json was obtained by applying the procedure here on the single file archive/coq/coq.json produced by the archive-gitter tool, untouched)
Note that I got errors during the import
https://gist.github.com/CohenCyril/41ea1d099e6cd6908665214f52c0aa18
which I cannot relate to the error above...
Side note:

Now, with #14825, it becomes ever worse:
import zulip
client = zulip.Client(config_file="~/.zuliprc-all-coq")
len(client.get_messages({'num_before':4000, 'num_after':0,'anchor':1000000000})['messages'])
# Out: 1
client.get_messages({'num_before':1, 'num_after':0,'anchor':1000000000})['messages'][0]['id']
# Out: 186599 # Does it count messages from the two realms???

while
$ cat converted_gitter_data/messages-*.json | grep "subject" | wc -l
# 95484

With the same kind of error during import https://gist.github.com/CohenCyril/dac72ab0f2521bc9035513ae74c12951

@hackerkid I am not sure yet how much this issue is linked with #14825

I believe this situation is at least partially explained by your system not creating UserMessage rows during the import for anything but the default stream.  The get_messages API only requests messages in the current user's personal history, which you aren't creating during the import because of the missing Subscription objects.  If you add the streams:public  keyword, for example, you'll see all the messages in public streams th.
On the IDs front, IDs are globally sequential for the server, so if you do multiple imports (etc.) the first message ID an organization will just keep increasing.

(I think that you can fix this by just creating Subscription objects for every stream for every user; that's at least a better default than what we have now).

@timabbott thanks for the explaination what happens when a new user joins a stream, can't we recreate that?

what happens when a new user joins a stream

A Subscription object is created marking them as a subscriber, which causes the stream to appear in their sidebar.
But the key thing going on here is that GET /messages, without a specified narrow, searches the user's personal history (i.e. messages received after they joined Zulip).  Whereas with a specified narrow, it searches all messages in the stream that the user has access to (which in particular, includes all messages in public streams or private streams with shared history).  The fact that the import tool didn't create Subscriptions (and as a further in the import tool process, crease UserMessages and thus give users simulated "personal history" for those streams) led to the unlikely-in-normal behavior seen here.
I think #14871 resolves the main issue described here.
For https://gist.github.com/CohenCyril/41ea1d099e6cd6908665214f52c0aa18, are you running Debian by any chance?  I think https://github.com/zulip/zulip/issues/14805 might be the root cause of the problem (namely, memcached access errors causing cascading other exceptions).

@timabbott

But the key thing going on here is that GET /messages, without a specified narrow, searches the user's personal history (i.e. messages received after they joined Zulip)

That kind of makes sense to me, but the seemingly connected problem was that I could not edit the topic of all the messages (using the web UI, as a newly created admin), and could apparently edit only the ones in the personal history of the user. It was also solved by #14871, ... so if there is indeed a causality between between "being in the personal history" and "being able to modify the topic", I am still wondering if it is intended...

For https://gist.github.com/CohenCyril/41ea1d099e6cd6908665214f52c0aa18, are you running Debian by any chance?

Nop, Ubuntu 18.04.4 LTS Bionic Beaver freshly installed in a virtual machine end of April, but not updated since then.

OK, new theory based on another similar report we debugged : The problem here was OOM kills of memcached.  If you're up for testing, I think that:
(1) Stopping the Zulip server first
(2) running manage.py import --processes=2 (to add fewer processes than the default 6)
Should work without any exceptions -- so the issue isn't parallelism, exactly, it's memory usage leading to a memcached OOM kill.
https://github.com/zulip/zulip/commit/779daa5374e96cc2e48ab313adf118077e14a333 adjusts the documentation to suggest (1), we'll address (2) as well in the defaults to not be 6.

Closing in favor of our planned solution https://github.com/zulip/zulip/issues/14960, under the assumption that diagnosis proves correct.


⚠ Bofrost.be has degraded performance

In 67a1418, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1295 ms

Resolved: Bofrost.be performance has improved in 346f562.


FloatProperty, etc...

In the Python API there are lots of other property types.
Will those be implemented in Dart as well?

@mkustermann Did this land at all?
Because of the 500 char limit, I've recently found a need for the TextProperty again, but I have a feeling that it's not as simple as just adding
class TextProperty extends db.PrimitiveProperty {
const TextProperty(
{String propertyName, bool required: false, bool indexed: false})
: super(propertyName: propertyName, required: required, indexed: indexed);
bool validate(db.ModelDB db, Object value)
=> super.validate(db, value) && (value == null || value is String);
}
or you would have done it.
Being able to read TextProperties is pretty important for one of my use cases, so if there's something I can do to help get this landed, please let me know. Thanks!

@lukechurch The DoubleProperty, BlobProperty and ModelKeyProperty properties landed.
Strings of more than 500 characters cannot be indexed on AppEngine. Did you try turning indexing off? [i.e. @db.StringProperty(indexed: false) String myLongString]

Since this issue was originally about floating point property and we've added that as DoubleProperty I'll close this issue.


Resolve TODOs in Commitment Verifier

[ ] What happens if the committee rotated after the fork?
[ ]  verifyAttestations: this might differ if we have Accounts with changing weights depending on the SlotIndex/epoch

This can be done together with #210

Addressed with #531


Support for 1.20.4.

Fabric has had 1.20.4 for weeks now.
Is there any benefit to using Quilt, such as memory, or performance? Quilt just seems to be "Fabric" renamed to "Quilt".
If these updates will be this slow, I'll stick with Fabric, unless you can justify Quilt in any way.

Support for 1.20.4 is planned for. Work is still being done to release 1.20.2. As the maintainer for both QFAPI and QSL, I have been extremely busy and unable to spend any time on updates.
If you want to know the difference between quilt and fabric, check our FAQ

Fabric has had 1.20.4 for weeks now.
Is there any benefit to using Quilt, such as memory, or performance? Quilt just seems to be "Fabric" renamed to "Quilt".
If these updates will be this slow, I'll stick with Fabric, unless you can justify Quilt in any way.

it's typically this kind of comment that destroys the desire of some developers to maintain their projects
please be understanding towards them

Quilt provides a lot of useful tools and is working on lot of more advanced projects than Fabric's one. There's a few examples:

Quilt's Enigma, which recently got its 2.0 release
Collision Handling ASM, which will be really useful when ready-for-release
QSL, which provides new modules that are really usefulls for devs, such as Recipe API, Registry Entry Attributes, Registerable Tacked Data Handlers etc...
Quilt Mappings which will enters to its 2.0 release in the future, allowing a lot of useful additions for mod developers.
Quilt Loader, with their Quilt Loader Plugins and few improvements over the Fabric Loader.

Support for 1.20.4 is planned for. Work is still being done to release 1.20.2. As the maintainer for both QFAPI and QSL, I have been extremely busy and unable to spend any time on updates.
If you want to know the difference between quilt and fabric, check our FAQ

I've read this useless FAQ many times, and all I see is: "More compatible", and "an inclusive community."


deletion update is 1 step behind

when deleting an object using the transform tool, the update is 1 step behind because the click event (and the update state) happens before the double click event fires.
A suggestion is to save the state after the double click event (a pull request #34).

Closed with #34 thanks for the fix!

Closed with #34 thanks for the fix!


[BUG] Crashes with BetterEnd / BetterNether

Bootup crash
latest.log

Ah, optifine, optifine, optifine... I've heard that it can cause tons of crashes with random things. I know this is several months late, but maybe try without optifine @SylisMC ?

No, I think it's this mod, I encountered it myself. I need to get back to finishing this mod.


[MAC] undefined macro: AC_DEFINE, AC_MSG_FAILURE

MAC OS X 10.10.5
$ rustc -V
rustc 1.14.0 (e8a012324 2016-12-16)
$ cargo -V
cargo 0.15.0-nightly (298a012 2016-12-20)
in the /flowgger and run "$ sudo cargo build --release -v". Get the following errors.
....
HOST = Some("x86_64-apple-darwin")
TARGET = Some("x86_64-apple-darwin")
HOST = Some("x86_64-apple-darwin")
CFLAGS_x86_64-apple-darwin = None
CFLAGS_x86_64_apple_darwin = None
HOST_CFLAGS = None
CFLAGS = None
running: "./autogen.sh"
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
--- stderr
configure.ac:17: installing './compile'
configure.ac:17: installing './config.guess'
configure.ac:17: installing './config.sub'
configure.ac:15: installing './install-sh'
configure.ac:15: installing './missing'
Makefile.am: installing './INSTALL'
/usr/local/share/automake-1.15/am/ltlibrary.am: warning: 'libsnappy.la': linking libtool libraries using a non-POSIX
/usr/local/share/automake-1.15/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
Makefile.am:4:   while processing Libtool library 'libsnappy.la'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
configure.ac:43: error: possibly undefined macro: AC_DEFINE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:45: error: possibly undefined macro: AC_MSG_FAILURE
thread 'main' panicked at 'failed to run successfully: exit code: 1', /Users//.cargo/registry/src/github.com-1ecc6299db9ec823/snappy-sys-0.1.0/build.rs:102
note: Run with RUST_BACKTRACE=1 for a backtrace.

Hi there,
If you don't need Kafka, you can probably get around this by compiling without Kafka:
cargo build --release --no-default-features

(sudo is not required btw, even for cargo install)
The problem doesn't seem to be in Flowgger itself, but in the Snappy library.
OSX 10.10 is getting really old now, and I don't expect the Snappy developers to support this operating system any more. If my memory serves me correctly, it used to ship with autoconf and automake in the base system, but these were already pretty old.
You may want to install them using Homebrew instead in order to get newer versions.
But still, if you don't need Kafka, the easiest way to go is probably to just not compile Flowgger without Kafka support.


Rotation issue when closing in landscape mode

ImageViewer does not handle common device correctly when being closed.
Steps to reproduce

Adjust Demo to allow Landscape Orientation

Launch Device in Portrait (e.g. iPhone 6+, iOS 9)

Tap on Image

Rotate Device

Close Image by using "X" Button

Alternate Steps

Rotate Device before tapping Image
Tap Image
Close Image by using "X" Button

Expected

Image closing to DisplaceableView

Result

Image closing to DisplaceableView but rotating wrongly during close

Further Details
Using latest commit https://github.com/MailOnline/ImageViewer/commit/65a0a235bafd2a0b2212c86fd92f23fc4be5b5b2.
Issue Preview

Excellent bug report @winkelsdorf
Will try to look into it ASAP

@zfoltin You're welcome, thanks having a look into!

I don't understand the complicated rotation handling implemented in ImageViewer yet, but I can imagine it's needed for cases where your applications usually run in portrait-only mode and you would like to override this for the ImageViewer while allowing to revert back to the previous displacement items.
Probably this would have been easier alongside using open override var supportedInterfaceOrientations: UIInterfaceOrientationMask?
When using .rotationMode(.applicationBased) it shouldn't be needed at all.
Anyway, regarding the reported bug, if I comment out your custom rotation handling in ItemBaseController´s method public func dismissItem(alongsideAnimation: () -> Void, completion: @escaping () -> Void) at line L525 it works:
    public func dismissItem(alongsideAnimation: () -> Void, completion: @escaping () -> Void) {

        guard isAnimating == false else { return }
        isAnimating = true

        alongsideAnimation()

        switch presentationStyle {

        case .displacement:

            if var displacedView = self.findVisibleDisplacedView() {

                if displacementKeepOriginalInPlace == false {
                    displacedView.hidden = true
                }

                UIView.animate(withDuration: reverseDisplacementDuration, animations: { [weak self] in

                    self?.scrollView.zoomScale = 1

                    //rotate the image view
//                    self?.itemView.transform = deviceRotationTransform()

Of course this probably breaks other places but at least it's the line causing the problem.


Spine JS + JQuery Mobile + Ajax Request

Ciao,
do you have an example with your router and Spine JS?
Grazie

Ciao,
uhm, not yet, but I'd like to add one soon.
If you're willing to try and write something, I'll happily add it to the repository.
A presto,
Andrea


Vault Support + Tenant Mode

Description
This PR introduces the support for using Vault as the secrets backend for Airflow instances created from this repo. It also adds the ability to override those variables from within Airflow via the overrides variable key. There's some general refactoring to enable the overrides.
This also adds the "tenant" mode of installation for Airflow within our baremetal cluster. Unlike the playground mode, this only lets a git user deploy 1 instance of Airflow and is not branch-aware. This should be the default method of installation for users looking to have a longer-running instance of Airflow within our cluster. Playgrounds should be reserved specifically for development. This change also introduced some labels to the resources created by these modes to make it easy to prune playgrounds that exist too long.
More importantly there's a good number of doc changes to make the repo more self-explanatory.
Fixes

es issue where it could only support http:// urls
issue in airflow where you have to add each module to the path for local imports to work. Resolved by adding the top level package in it's __init__.py
issue where repos cloned with the ssh url don't install properly

Short-term they are definitely very similar, but Playground is mainly meant to be used to test changes before opening PRs against upstream (similar to this one).
Medium/Long-term we may have cases where a tenant would want to have their own secrets in vault (i.e. QE uses their own AWS creds/jumphost/etc. and they may want to just add their credentials in vault instead of having to override them). We can also pass down the tenant-id to thanos/elasticsearch/dashboard to segment the data.


optional keywords -K

Added option -K, similar to -k but if no keyword is found, use the value " " instead.
optional keywords are printed after required keywords, because the args system puts them in different lists.

a space is used instead of empty string, so it can be distinguished from null fits value, and also it can works better with some formatting of the output.
optional keywords are put to the end, because the args system puts them in another list.

Maybe it is better to add an binary option instead to make all keywords optional and to give a default value by the user.  It would be less precise but cleaner. let me know


Construct new columns in EIA PPL data

Feature engineering for the PPL dataset used by Panda can be done by adding the following columns to the PPL (and FERC):

[x] utility_name_eia (where did this code end up?)
[x] construction_year
[x] installation_year
[x] map the codes for use in comparison to plant_name_ferc1 (prime movers, fuel types, etc.)

a little confused how plant_name_new is constructed on the EIA side - it's assembled from primary key columns for the plant part?
could maybe make another version of plant_name_new that includes full strings inside of codes?
[ ] prime mover code to full string
[ ] fuel type code pudl

record_id_eia: 2707_hy_2018_plant_prime_mover_total_3046, record_id_ferc1: f1_hydro_2018_12_17_0_1
st, ic, gt on EIA side maps to steam on FERC side

[ ] EIA energy source code
[ ] EIA technology description (maybe could map to FERC plant_type)
[ ] see what Christina did with recent code mapping

[ ] fuel_type_code_pudl could maybe use another pass on the FERC side, can we eliminate some nulls? Alternatively, can fuel_type_code_pudl map to a few different columns on the FERC side?

To get construction_year and installation_year:
There is an operational_date and an uprate_date for each of the EIA generators. We can take the max and min of the operational_date for each plant part to get a date that somewhat corresponds to the construction and install year in FERC.
These changes should probably go into a CCAI output layer. This output layer will be reworked and integrated into the DAG later down the line.

LF summary:

Utility name:

is it enough to say that utility id must be matching, utility id is manually assigned?

Installation and construction name:
FERC plant name to EIA columns composite LF:

could also include capacity_mw?

plant_id_report_year:
use true grans and ownership columns?


Support new "astro:db:setup" hook

Since they added new support for Astro DB the hooks changed.  would be nice to get a patch that

Updates the already existing AIK Extended hooks to use the new Astro v4.5 Hooks
2. adds support to tie into @astrojs/db's new hooks

That means AIK 0.7.0 will only support 4.5 and above I guess? That's a bit annoying 🤔 but maybe @Fryuni you know how to best deal with it? I mean is there a smart way with peer dependencies and stuff?

https://docs.astro.build/en/guides/astro-db/#building-astro-db-integrations, it's not part of the integrations api reference just yet

Oh I see!  I saw both the cloudflare & ExpressiveCode repo's where having typing issues, kinda had the same issues locally with all my AIK integrations which made me think there might be a typing issue going on again... maybe its just pnpm being weird then...
on another note, maybe we need a AstroDB AIK plugin... I'd be willing to help with it!  im just not to sure how how this advanced hooks work yet... still learning!

Actually, this is currently popping up in my astro-gists playground when i look at the integrations list...
Type 'AstroIntegration' is not assignable to type 'false | AstroIntegration | (false | AstroIntegration | null | undefined)[] | null | undefined'.
  Type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroIntegration' is not assignable to type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroIntegration'.
    The types of 'hooks['astro:config:setup']' are incompatible between these types.
      Type '((options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; ... 10 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/core/logger/core").AstroInteg...' is not assignable to type '((options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; ... 11 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node<EMAIL_ADDRESS>        Type '(options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 9 more ...; logger<EMAIL_ADDRESS>is not assignable to type '(options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; ... 11 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node<EMAIL_ADDRESS>          Types of parameters 'options' and 'options' are incompatible.
            Type '{ config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | ... 1 more ... | "preview"; ... 10 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_<EMAIL_ADDRESS>is not assignable to type '{ config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 9 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/core/logger/core").As...'.
              The types of 'config.integrations' are incompatible between these types.
                Type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroIntegration[]' is not assignable to type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroIntegration[]'.
                  Type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroIntegration' is not assignable to type 'import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroIntegration'.
                    The types of 'hooks['astro:config:setup']' are incompatible between these types.
                      Type '((options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; ... 11 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node<EMAIL_ADDRESS>is not assignable to type '((options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; ... 10 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/core/logger/core").AstroInteg...'.
                        Type '(options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; ... 11 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node<EMAIL_ADDRESS>is not assignable to type '(options: { config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 9 more ...; logger<EMAIL_ADDRESS>                          Types of parameters 'options' and 'options' are incompatible.
                            Type '{ config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | "build" | "preview"; isRestart: boolean; ... 9 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.4.11/node_modules/astro/dist/core/logger/core").As...' is not assignable to type '{ config: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_@types+node@20.11.25_typescript@5.4.2/node_modules/astro/dist/@types/astro").AstroConfig; command: "dev" | ... 1 more ... | "preview"; ... 10 more ...; logger: import("E:/git-repo/astro-gists/node_modules/.pnpm/astro@4.5.0_<EMAIL_ADDRESS>                              The types of 'config.markdown.shikiConfig' are incompatible between these types.
                                Property 'themes' is missing in type '{ langs: LanguageRegistration[]; theme: ("andromeeda" | "aurora-x" | "catppuccin-frappe" | "catppuccin-latte" | "catppuccin-macchiato" | "catppuccin-mocha" | ... 31 more ... | ThemeRegistrationRaw) & ("andromeeda" | ... 37 more ... | undefined); experimentalThemes: Record<...>; wrap: boolean | null; transformers: Sh...' but required in type '{ langs: LanguageRegistration[]; theme: ("andromeeda" | "aurora-x" | "ayu-dark" | "catppuccin-frappe" | "catppuccin-latte" | "catppuccin-macchiato" | "catppuccin-mocha" | ... 35 more ... | ThemeRegistrationRaw) & ("andromeeda" | ... 42 more ... | undefined); themes: Record<...>; wrap: boolean | null; transformers: S...'.ts(2322)

Yeah this error is expected because the AstroIntegration type is different in 4.5 than previous versions. Given our current plugin system, having a plugin to support the hook won't work. I think it's a matter of optional deps really but I'm not comfortable enough to tell you what the solution is exactly

I have changed the main description to simply update to the new AstroIntegration type in that case, as IMO given what you mention about the plugin system option, It would probably just be simplier to use the DB's option once the AstroIntegration type is updated...

To be clear, the work required to make it work is really small but this is not my main concern! I'm more concerned about the fact that upgrading aik astro peer dep to 4.5 means any integration author using aik will also have their minimal astro version st to 4.5. Not ideal

I think there might be a way to add support without moving the peer requirement.
We just have to make the code work for subtypes and the types be derived from Astro (which I think they already are)

Do you have an example?


i don't want to show selected item in list of dropdown.

Can you provide some description for your issue?

Duplicate of #194


LoggerSetLevel not working?

#include <a_samp>
#include <a_spdlog>

#define SERVER_LOG "server"

main()
{

}

public OnGameModeInit()
{
    LoggerSetAsyncMode(4096);

    BasicLogger(SERVER_LOG, "logs/server_log.txt");

    LoggerSetLevel(SPDLOG_LEVEL: TRACE);
    printf("Set log level to TRACE");

    LogDebug(SERVER_LOG, "1: This is an debug message");
    LogInfo(SERVER_LOG, "1: This is an info message");

    LoggerSetLevel(SPDLOG_LEVEL: INFO);
    printf("Set log level to INFO");

    LogDebug(SERVER_LOG, "2: This is an debug message");
    LogInfo(SERVER_LOG, "2: This is an info message");

    LogFlush(SERVER_LOG);

    return 1;
}

public OnGameModeExit()
{
    DropAllLogger();

    return 1;
}

Gives me:
[2017-05-08 20:54:33.919] [server] [debug] 1: This is an debug message
[2017-05-08 20:54:33.919] [server] [info] 1: This is an info message
[2017-05-08 20:54:33.919] [server] [debug] 2: This is an debug message
[2017-05-08 20:54:33.919] [server] [info] 2: This is an info message

Unless my understanding is wrong here, shouldn't LoggerSetLevel(INFO) disable any lower log levels (so LogTrace and LogDebug?

Hi,
this was a mistake made by me.
This should work right now see commit
Use this version (dont forget to use the new a_spdlog.inc)!
https://github.com/Sphinxila/samp-plugin-spdlog/releases/tag/v.1.0.0


Application configurations could be set using page.

all options (excluding agent options) could be set on agent.

Like this...


Delete Duplicate folder

There are currently 2 folders for CodeChef Problems. Copy the contents of CodeChef_Problems into CodeChef_problems and delete the CodeChef_Problems folder.
I am not able to do this since both folders automatically merge when cloning on Windows machine.
So if anyone with Mac or Linux OS are able to do this, then please do and send a PR.
Note: Since this involves deletion and modification of files/folders, it would be better if  only those having prior experience with Git and Github take up this issue. So please reply here if you would like to take up this issue.

Solved by #138.  Closing this.


ENHANCEMENT REQUEST (KVM)(Kubernetes): Resize compute offering for kubernetes clusters in a stopped state

ISSUE TYPE

Enhancement Request

COMPONENT NAME

CLOUDSTACK VERSION

4.17.1 +

CONFIGURATION

KVM hypervisors
OS / ENVIRONMENT

n/a
SUMMARY

Scaling compute offerings for underlaying KVM based VMs for k8s clusters when they are in a stopped state. You can resize KVM VMs in cloudstack in a stopped state, it would be ideal to allow resizing of machines for kubernetes clusters as well (KVM)
STEPS TO REPRODUCE

1. Stop a running KVM kubernetes cluster (API or UI)
2. 'Scale' compute offering for VMs in that cluster (API or UI)
3. Start KVM kubernetes cluster with the new compute offering (API or UI)

EXPECTED RESULTS

Change compute offering for KVM based kubernetes clusters in a stopped state

ACTUAL RESULTS

Live scale of compute offering size in kubernetes is not supported for KVM (so we should enable it for stopped state)

Improvement added in https://github.com/apache/cloudstack/pull/7475. This issue can be closed once confirmed


the journey begins | aigeek

http://aigeek.hexo.s3.bucket.s3-website-eu-west-1.amazonaws.com/2023/01/14/the-journey-begins/
AI is becoming increasingly present in our daily lives, from self-driving cars to stock and currency trading, disease diagnosis, code-writing, copyright-free artwork creation and resume generation. it

first comment


documentation =)

client_max_body_size to the sample config on docs/index.md
fix typos

Documented in b43a915 but fixed a typo in 9ad059a


Does not compile under React Native 0.40

I have upgraded my react native project to 0.40. Everything works fine, except for react-native-webview-bridge which produces loads of compile errors. This might have something to do with https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d

Need iOS header updates like this.
See https://github.com/facebook/react-native/releases/tag/v0.40.0


ENH: Added logging to compute endpoint

Includes expression being computed and total time to compute

Just update the issue in the whatsnew. Thanks you for adding the logs!

Updated the issue in the whatsnew.  Thanks!


RenderPassSsao: improve SSAO blur performance

This PR suggests splitting one large blur pass from "RenderPass based SSAO" into four smaller blur passes without compromising quality.

Main
PR

Tested on MacBook 14" Pro (2021), used device.maxPixelRatio = window.devicePixelRatio; to increase resolution of framebuffers.
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Hi @querielo - that's definitely a good way to speed it up. But I wonder why doing 4 passes instead of just typical two separable passes?

Hi. @mvaligursky
The main idea is that the first two passes weaken the high-frequency signal. The next two passes are used to eliminate low-frequency signal (there are strided/interleaved blurs with a large step, applied diagonally).
Experimentally, it seems that increasing the filter kernel size is necessary to remove low-frequency SSAO patterns. For example, using a 17x17 kernel on my computer results in a noticeable slowdown, but it appears to achieve the effect of four passes.
The suggested four-pass approach is just one way to implement blurring. An advanced developer could add RenderPassDepthAwareBlur to afterPasses themselves, depending on the specific SSAO pattern generated.

4 passes
2 passes, 11x11
2 passes, 17x17

I had a bit of a play with your branch. My findings:

two pass BOX blur with 9 samples seems to be equivalent to the current 9x9 filter, as expected. I assume this is faster.
two pass GAUSSIAN blur with 9 samples is a lot lower quality compared to that - see especially around the yellow torches
four pass you had set up seems to match in quality with the two pass BOX with 9 samples - so I'm not sure we need to use 4 passes.

I think the main reason you need 4 passes is the use of the GAUSSIAN weights instead of BOX.

And so my recommendation is: switch it to 2 pass BOX filtering. We can expose the number of taps to the user as that controls the quality vs the cost.

@mvaligursky I switched the blur to 2 pass BOX filtering.

Offtop: It looks like 6f29e1b005f2ab2a38f75fb45739387561d1d50a breaks the background.

Offtop: It looks like 6f29e1b breaks the background.

It just got brighter as a result of this https://github.com/playcanvas/engine/pull/6687 I suspect?

Looking much better, thanks!
I'd suggest to remove the option / API to change the blur type. Box looks better than Gaussian, and so the SSAO should just use Box. Only expose values that the user would benefit from adjusting.

I'd suggest to remove the option / API to change the blur type. Box looks better than Gaussian, and so the SSAO should just use Box. Only expose values that the user would benefit from adjusting.

Are you certain?
Stage: https://engine-m742xowmh-playcanvas.vercel.app/#/graphics/ambient-occlusion
To me, it seems that enlarging the kernel size of Box displaces dark areas from their correct position. However, Gaussian necessitates a larger kernel to conceal the SSAO pattern.
https://github.com/playcanvas/engine/assets/104348270/fdf04009-01de-4ffb-8765-94e13c8a9a20

@mvaligursky Are you certain? Stage: https://engine-m742xowmh-playcanvas.vercel.app/#/graphics/ambient-occlusion To me, it seems that enlarging the kernel size of Box displaces dark areas from their correct position more quickly than hiding SSAO artifacts. However, Gaussian necessitates a larger kernel to conceal the SSAO pattern.

yeah interesting. It almost feel like the the bilateral weight function should be improved
float bilateralWeight(in float depth, in float sampleDepth) {
    float diff = (sampleDepth - depth);
    return max(0.0, 1.0 - diff * diff);
}

to detect the depth discontinuity better, as currently it blurs over those small edges. Maybe we can try something like this to have a control over it by the sigma value:
float bilateralWeight(in float depth, in float sampleDepth, in float sigma) {
    float diff = (sampleDepth - depth);
    return exp(-diff * diff / (2.0 * sigma * sigma));
}

but agreed, the Gaussian blur in general should be slightly better, at a higher cost, so maybe leave it in.

Hi @querielo - have you had some time to look at these?

@querielo - please let me know if you have time to finished this PR. I'm keen to continue on some improvements too (https://github.com/playcanvas/engine/issues/6658) but would prefer to avoid larger conflicts with the changes.
If you don't have time, I can take over this PR.

@querielo - please let me know if you have time to finished this PR. I'm keen to continue on some improvements too (#6658) but would prefer to avoid larger conflicts with the changes.
If you don't have time, I can take over this PR.

guess thats a no...

yep, it's on my list to get to in a week or so. Definitely not forgotten.

Yes. Sorry, I'm too busy right now and therefore don't have time to fix it.

closing this due to https://github.com/playcanvas/engine/pull/6870
Thanks @querielo


Only report log collection progress in sourcekit-lsp diagnose if we’ve made meaningful progress

Especially when we didn’t have a redrawing progress indicator, we would spam the output with out making progress that was visible to the user because the overall progress just shows a percentage without any decimal digits. To fix this, only report progress when we’ve made at least 1% of progress in log collection.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows


plenty of warnings when compiling with Swift 5

Please be sure to include:

what OS you are developing on (Linux or macOS, including the version)

macOS 10.14

for macOS, what version of Xcode you are using (xcodebuild -version),
for Linux, what version of Swift (swift --version)

Swift 5.0 dev snapshot 3rd March 2019

what version of Swift is your code set to compile with (i.e. from project
settings, etc.)

Swift 5.0 dev snapshot 3rd March 2019

what branch/tag of SwiftProtobuf you are using (1.0.0, etc.)

master from today:
commit 3f569345a6162ef32d22ee7c0dfa8457705a48b5 (HEAD -> master, origin/master, origin/HEAD)
Author: Thomas Van Lenten<EMAIL_ADDRESS>Date:   Thu Mar 21 17:39:05 2019 -0400

    Update the generated_swift_names_* protos.

if you are getting compile errors, please be sure include all errors/warnings,
sometimes the error before the one you are stuck on is important.

/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Message+BinaryAdditions.swift:36:14: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
    try data.withUnsafeMutableBytes { (pointer: UnsafeMutablePointer<UInt8>) in
             ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Message+BinaryAdditions.swift:107:16: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
      try data.withUnsafeBytes { (pointer: UnsafePointer<UInt8>) in
               ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Message+JSONAdditions.swift:92:22: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
    try jsonUTF8Data.withUnsafeBytes { (bytes:UnsafePointer<UInt8>) in
                     ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Message+JSONArrayAdditions.swift:94:29: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
    return try jsonUTF8Data.withUnsafeBytes { (bytes:UnsafePointer<UInt8>) in
                            ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Message+TextFormatAdditions.swift:56:18: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
        try data.withUnsafeBytes { (bytes: UnsafePointer<UInt8>) in
                 ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/Google_Protobuf_Any+Extensions.swift:69:18: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
        try data.withUnsafeBytes { (bytes: UnsafePointer<UInt8>) in
                 ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/TextFormatScanner.swift:358:12: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
      data.withUnsafeMutableBytes {
           ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/TextFormatEncoder.swift:266:15: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
        value.withUnsafeBytes { (p: UnsafePointer<UInt8>) in
              ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/TextFormatEncodingVisitor.swift:71:17: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
      try bytes.withUnsafeBytes { (p: UnsafePointer<UInt8>) -> () in
                ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/TextFormatEncodingVisitor.swift:100:21: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
              bytes.withUnsafeBytes { (p: UnsafePointer<UInt8>) -> () in
                    ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONEncoder.swift:73:44: warning: 'init(bytes:)' is deprecated: use `init(_:)` instead
    internal var dataResult: Data { return Data(bytes: data) }
                                           ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONEncoder.swift:336:19: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
            value.withUnsafeBytes { (p: UnsafePointer<UInt8>) in
                  ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONScanner.swift:192:15: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
    try value.withUnsafeMutableBytes {
              ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONScanner.swift:850:25: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
        let n = try raw.withUnsafeBytes {
                        ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONScanner.swift:909:25: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
        let n = try raw.withUnsafeBytes {
                        ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONScanner.swift:973:27: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
          let n = try raw.withUnsafeBytes {
                          ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/JSONScanner.swift:1044:27: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
          let n = try raw.withUnsafeBytes {
                          ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/AnyMessageStorage.swift:54:16: warning: 'init(bytes:)' is deprecated: use `init(_:)` instead
  var result = Data(bytes: [asciiOpenCurlyBracket])
               ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/AnyMessageStorage.swift:69:19: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
  try contentJSON.withUnsafeBytes { (bytes:UnsafePointer<UInt8>) in
                  ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDecoder.swift:879:23: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
                field.withUnsafeMutableBytes { (pointer: UnsafeMutablePointer<UInt8>) in
                      ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDecoder.swift:1207:30: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
                    try data.withUnsafeBytes { (pointer: UnsafePointer<UInt8>) in
                             ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDecoder.swift:1248:33: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
                        payload.withUnsafeMutableBytes { (pointer: UnsafeMutablePointer<UInt8>) in
                                ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDelimited.swift:58:10: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
    data.withUnsafeMutableBytes { (pointer: UnsafeMutablePointer<UInt8>) in
         ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDelimited.swift:64:10: warning: 'withUnsafeBytes' is deprecated: use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead
    data.withUnsafeBytes { (pointer: UnsafePointer<UInt8>) in
         ^
/Users/johannes/devel/swift-protobuf/Sources/SwiftProtobuf/BinaryDelimited.swift:157:10: warning: 'withUnsafeMutableBytes' is deprecated: use `withUnsafeMutableBytes<R>(_: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R` instead
    data.withUnsafeMutableBytes { (pointer: UnsafeMutablePointer<UInt8>) in
         ^
/Users/johannes/devel/swift-protobuf/Sources/Conformance/main.swift:39:12: warning: 'init(bytes:)' is deprecated: use `init(_:)` instead
    return Data(bytes: buff)
           ^
[6/6] Linking ./.build/x86_64-apple-macosx/debug/protoc-gen-swift

lastly, if it all possible, provide a snippet of .proto and/or source
that shows the problem.

n/a
Thank you!

See #843, this is actively being worked on.

apologies!

apologies!

No worries, we didn't have an issue open for it in parallel.  Just wanted to make sure folks that saw this were aware so they didn't duplicate the work looking to update things.  😄

Update:
PRs #844 and #848 fixed most of these (especially, the 200+ warnings about Data(bytes:) being deprecated).
There are now 24 warnings about withUnsafeBytes and withUnsafeMutableBytes deprecations that are being worked on in #843.


htmx problem

I am trying to implement the functionality to bulk update as set out in https://htmx.org/examples/bulk-update/
It seems that the swap of the tbody element isn't being done properly since the checkboxes are not visible but they do appear in the html, and the button elements are repeated. (which seems to indicate that it is not just the tbody which is being swapped but other elements on the page (or maybe the whole page)
In your experience with htmx, do you have any tips about where to start troubleshooting this?

I'm not sure what the problem would be. I haven't tried out that functionality yet and I would need to see the complete code that you're working with. If you post it, I can take a look (feel free to reopen this ticket with that). I would recommend opening a ticket with the htmx project or checking out their Discord.


feature: Go to definition inside lsp hover

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
It's not possible to Go to definition inside the lsp hover window. Discussed in #1987
Describe the solution you'd like
Being able to press the keymap Go to definition and it working
Describe alternatives you've considered
can't think of one
Additional context
No response

That's not possible


add 'uninitialCommands' feature

I want a feature to stop running threads or close used resources safely at the end of the console.
Some kind of library, that use their own user threads such as web server framework, suppose that we use Ctrl+C to interrupt the threads. In this situation, Ctrl+D causes freeze 'sbt console' because sbt wait for the user threads to exit eternally.

Thanks, harrah!


Mapbox GL

Is there a chance that mapbox-gl-js will return? I saw that it was included in earlier versions, wasn't it working well?
~Ben

Absolutelly!  Technically you can already use it - by setting up your own labs instance with the fonts and js libs, and pointing it to the maps.wikimedia.org PBF files. We simply haven't had enough time to work on it, but patches are welcome :))
We need:

a well documented way to generate font PBF files (IIRC, we need to use node-fontnik or another Mapbox script)
Adapt Mapbox's GL style to use our tileset
evaluate if we have any large tiles (e.g. above 500kb for now), and reduce their size

This issue was moved to kartotherian/kartotherian#18


EN hint text on "Change your mobile phone number" page

Discrepancy on https://staging.covid-hcportal.cdssandbox.xyz/en/profiles/fd158aeb-055b-40a7-9242-fbb27ff42b2b/edit/phone
Confirm phone number hint text: Enter the phone number again
Figma: https://www.figma.com/file/znPqLTQQDcUkaNjdDcShiz/Exposure-Notification-Health-Portal?node-id=7627%3A50385
Confirm phone number hint text: Enter the same mobile number as above

Pull Request for this issue has been created - https://github.com/cds-snc/covid-alert-portal/pull/733

Merged in stage and production.


generate esm code & add vitest for better testing strategy.

This solves issue #1 and makes it easier to test things using vitest

Thank you, just tested the changes in a vite project and it worked well.


Fixed UI errors

Fixes: #83
Screenshots:

Before
After

@Shruti025  I have merged your PR , gr8 work !.


Add error message fix in qr grad

Add a fix for the bug in the error message in the qr grad check for matrix shapes.

Is there a bug report? Or an example where the error is wrong? Can we add a test so that future change reversing the order in the comparison gets blocked if wrong?

@mihaimaruseac So the check works correctly, all the test cases are covered correctly - the only thing wrong is the text of the message: it should say 'nrows > ncols' vs 'ncols > nrows' . (My bad, I wrote the initial code).
Note the correct test cases in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/kernel_tests/qr_op_test.py

Eg where the incorrect message would show up:
import numpy as np
import tensorflow as tf
np.random.seed(42)

# nrows > ncols
nrows, ncols = 3, 2
a = np.random.uniform(-1, 1, (3, 2)).astype(np.float32)
atf = tf.convert_to_tensor(a)

with tf.GradientTape() as g:
  g.watch(atf)
  ret = tf.linalg.qr(atf, True) # full_matrices=True

g.gradient(ret, atf)

with output:
Traceback (most recent call last):
  File "/Users/denisaroberts/Desktop/eg.py", line 12, in <module>
    g.gradient(ret, atf)
  File "/Users/denisaroberts/tf/lib/python3.7/site-packages/tensorflow/python/eager/backprop.py", line 1083, in gradient
    unconnected_gradients=unconnected_gradients)
  File "/Users/denisaroberts/tf/lib/python3.7/site-packages/tensorflow/python/eager/imperative_grad.py", line 77, in imperative_grad
    compat.as_str(unconnected_gradients.value))
  File "/Users/denisaroberts/tf/lib/python3.7/site-packages/tensorflow/python/eager/backprop.py", line 162, in _gradient_function
    return grad_fn(mock_op, *out_grads)
  File "/Users/denisaroberts/tf/lib/python3.7/site-packages/tensorflow/python/ops/linalg_grad.py", line 498, in _QrGrad
    raise NotImplementedError("QrGrad not implemented when ncols > nrows "
NotImplementedError: QrGrad not implemented when ncols > nrows and full_matrices is true.

If it is possible to transform this example into a test that would be great.
Thank you for the PR and the context

@mihaimaruseac Will do. To be crystal clear - you mean a test that asserts that the correct message for the check is issued when "nrows > ncols and full_matrices=True" ?

Yes, a test that checks that the error message contains not implemented when ncols > nrows and full_matrices is true

@mihaimaruseac Added test.


Question on using a sequence length > the max length I can hold in a batch due to memory usage for training

For running extremely large sequence lengths, I can break up the sequence among batches and use the inference step to save the hidden states between passes. However, step does not work during training as there seems to be a problem with overwriting the variables before loss.backward() can be run.
How might you modify the forward pass to allow running the same parallel scan as used during training, but connect previous hidden states from other batches?

That's an interesting problem
I guess you would have to make N sequential parallel scans, each one starting with a hidden state equals to the last hidden state of the previous pscan.
Just to make sure we understand each other :

Concerning starting a pscan with a hidden state that is not zero (the code supposed that H[0] = 0), I recently answered an issue about that.
Hope that helps

Hello again, just wanted to inform you that I have started working on your question, you can follow the progress on the mem-update branch. Splitting in chunks (like you asked) is very useful to reduce the memory usage, and it has been a long time I wanted to do a "memory update" for mamba.py so :)


while-loops C tutorial

Populate C file with a tutorial and challenge.

@HenokB I already assigned a different issue to you. Please complete that first before requesting to be assigned to another issue. Thanks :)


Adding adopt me button and improve cards

Is your feature request related to a problem? Please describe.
A button would give user attention to adopt me.  Ex. Now it's not capturing the attention of users.(I'm in GSSOC'23" as a contributor.)
Describe alternatives you've considered
A proper button is highlighted on the page and improved styling of cards.
Additional context

(can I take this up as a part of gssoc 23')

currently its not needed for the website


Windows build is broken

It seems #754 has broken windows builds. Look here for more details on where/how it fails. Can confirm it fails on baremetal Windows as well.
CC @tridao @sgrigory

This is reproducible on my home PC as well using the latest commit of FA2. I cannot build any version that's >= 2.4.3

Same here


Bug in quickstart example in github pages

CACHE_FILE variable has not been defined in the quickstart example prior to its use.

It actually is defined in the header of the jupyter notebook corresponding to the quickstart page, but is hidden for the documentation. I changed it to be based on environment variables - hope that clears up the confusion!

It actually is defined in the header of the jupyter notebook corresponding to the quickstart page, but is hidden for the documentation. I changed it to be based on environment variables - hope that clears up the confusion!


Can't start AEM with latest or 6.5.0 image on mac m1

Bug Report
Current Behavior
I'm trying to prepare a local dev environment following instructions in the readme file, but during running, the docker image throws errors and the image is not up and running.
log
I tried next commands:
docker run --platform linux/amd64 --name author -e "AEM_RUNMODE=-Dsling.run.modes=author,crx3,crx3tar,dev" -p4502:8080 -d -p34502:58242 aemdesign/aem
docker run --platform linux/amd64 --name author -e "AEM_RUNMODE=-Dsling.run.modes=author,crx3,crx3tar,dev" -p4502:8080 -d -p34502:58242 aemdesign/aem:6.5.0
docker run --name author -e "AEM_RUNMODE=-Dsling.run.modes=author,crx3,crx3tar,dev" -p4502:8080 -d -p34502:58242 aemdesign/aem
docker run  --name author -e "AEM_RUNMODE=-Dsling.run.modes=author,crx3,crx3tar,dev" -p4502:8080 -d -p34502:58242 aemdesign/aem:6.5.0
Expected behavior/code
I'm expecting to have up and running AEM in the docker container.
Environment

AEM 6.5.0 / also tried lastest <IP_ADDRESS>-jdk11
JDK 1.8 and JDK 11
MacBook pro M1 PRO
macOS Monterey

Hope you tried one of the ARM images https://github.com/aem-design/docker-aem/tree/<IP_ADDRESS>-jdk11-arm

Huh that was long time ago :D
Not relevant anymore


CacheManager repository function has changed signature in L11

Laravel Version
11.0.3
PHP Version
8.3
Database Driver & Version
No response
Description
From Laravel 11, the CacheManager repository function has changed signature. This wasn't like that in Laravel 10.
As there is nothing about that in the upgrade guide, I think that we should add an empty array as default config attribute.
Steps To Reproduce
Just call the CacheManager repository function without the second argument.

Seems you already sent in a PR so let's see how that goes. Thanks!


Create B1

Node Name: ade4u
Node ID: a2bbb8d017c8c6c0
https://dashboard.testnet.concordium.com/node/a2bbb8d017c8c6c0
Full logs will be submitted

@serCJm It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

confirmed:B4
address:4PJSEpdQpAhBGRKk62p1hhfaRX8VSXYprA1i8kfRyeCFaYJWBr
baker:98

confirmed:B4
address:4PJSEpdQpAhBGRKk62p1hhfaRX8VSXYprA1i8kfRyeCFaYJWBr
baker:98


Open VSX

Hey, I have requested this on Serendipity before (https://github.com/Serendipity-Theme/vs-code/issues/17) but not on the old version, and would be great to have it on there too!
I personally use Serendipity sunset v1 because of the added contrast

You got it!
Get it here:

https://open-vsx.org/extension/wicked-labs/old-serendipity

Ty!!

Ty!!

Welcome!