MacBook version

Is your feature request related to a problem?
The problem is that the Runestone app appears to be available on iPhone/iPad.
What solution would you like?
I would love it to be available on MacBook as well, with synchronisation between all devices via iCloud.
What alternatives have you considered?
Other code editors like Textastic.
Any additional context?
No response

This issue seems related to the Runestone Text Editor app rather than the open-source Runestone framework, which this repository contains. I'll take note of your feature request and close this issue.


All sortings

I would like to add the remaining sorting techniques in the repo.
-> Count sort
-> Radix sort
-> Bucket sort
-> Shell sort

Can I work on this.

i am intrested to work on this issue.please assign it to me i can even make these sorting techniques in java  also

I can work on this task, I have learnt many sorting algorithms like counting sort, radix sort, insertion sort, selection sort, merge sort, quick sort, bubble sort, along with clear concept on each and every sorting algorithm's time and space complexity, and also their recursive relations.

@aaryahjolia Can you issue me this task under GSSOC label?


Header in Vivid-3 docs

Change Header + Side-nav in our current docs:

move Vivid logo from the side-nav to the header - when the logo is in the side-nav and we collapse the sid-nav we "lose" our Vivid logo. We want the logo to always be displayed 😍

Change the logo to

OR back to this

(Your choice @yinonov @rachelbt)

Make the logo a shortcut to the homepage? I notice currently the logo is not interactable so if we navigate to a different page we have no access back to the homepage.

Notice this ticket as well https://github.com/Vonage/vivid-3/issues/496
Once we fix the side nav I would want the doc to look something like this

Or this (depending on the logo)

@jshenkman
for Visual QA:

now the header is starched above the side-drawer
in main page: added the grey in the first part
in all component page - added bg to the component name. (didn't add the image - leaving it to another PR).
please check both desktop & mobile
there might be some breaking in mobile due to the typography and lone names of the components member (e.g. Accessibility).
Thanks

Oh, one more thing - can we have a different page template/layout for component pages and design system pages?
In these design system/foundation pages I made nicer graphics like this for color

And also the typography on the color page is too big, in the first section. So I think we should deal with it separately?

@rachelbt looks amazing!!!

Header is perfect. logo size and position is great.
For now, it's great. I would like to change the graphics instead of Vivid logo something else, maybe like these clouds - but we can deal with it in another PR :)

Love the colored strip! But I think it should be one shade darker so instead of purple-500 purple-600 (in current tokens I think its purple-70 #871EFF)
In general, I would like the strip to be a bit bigger (the height) and contain also the page's tabs and maybe a short component description like this -

Looks good also on mobile.
Great job looks amazing!!!!

I changed the color.
Adding images in in process we will add the decorative images after that will be done in a separate PR.
Different template is for another PR


Crash while generating

Hi,
I'm getting a Guix Software crash when I try to generate ressources.
Is there a log file somewhere I can send you and where is it located?
Thank you.

@Merc359 I'm probably going to need your project so that I can duplicate the issue. Can you zip everything up for me? We would never disclose your project outside our immediate need to replicate the issue.

Hi Jdeere,
I could send you our code via wetransfer or another way. Can you give me your email address so I can proceed?
Thank you

Hello @Merc359 , please use<EMAIL_ADDRESS>Thanks!

Fixed in GUIX Studio update <IP_ADDRESS>


Add Graceful Shutdown behavior

Add the following method Shutdown(ctx context.Context) on the server.
Also see for RunContext(ctx context.Context) ?

See v0.3.0


[Bug]: Regression in detectOpenHandles for DNSCHANNEL

Version
v30.0.0-alpha.2
Steps to reproduce
I'm using knex in a project that gets false positives for open handles, but it can be reproduced with this test:
import { promises } from "dns";

const { Resolver } = promises;
const resolver = new Resolver();
const servers = resolver.getServers();
console.log(servers);

describe("foo", () => {
  it("works", () => {});
});

Expected behavior
I expected jest --detectOpenHandles to not report anything, because the above code doesn't hang jest, it does actually exit cleanly.
Actual behavior
Jest does exit cleanly, but shows an error about an open handle:
 PASS  src/foo.test.ts (31 MB heap size)
  foo
    ✓ works (1 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.094 s, estimated 1 s
Ran all test suites matching foo.test.ts.

Jest has detected the following 1 open handle potentially keeping Jest from exiting:

  ●  DNSCHANNEL

      3 | const { Resolver } = promises;
      4 | const resolver = new Resolver();
    > 5 | const servers = resolver.getServers();
        |              ^
      6 | console.log(servers);
      7 |
      8 | describe("foo", () => {

Additional context
It looks like the DNSCHANNEL false positive was originally fixed here:
https://github.com/jestjs/jest/pull/11470/files
But then a refactor of detectOpenHandles (to dedupe stack traces) regressed the behavior (by removing the check as a potentially speculative clean up separate from deduping the stack traces?):
https://github.com/jestjs/jest/pull/13417/files
My reproduction is really just a copy/paste of #11470 's reproduction from #9982.
From the conversation in https://github.com/jestjs/jest/pull/13417/files#r990874803 , it kinda seems like maybe @liuxingbaoyu didn't understand why these types were being ignored, and more than just DNSCHANNEL needs to be added back to the "if type then early return" check?
Also cc @Mr0grog who fixed the original DNSCHANNEL false positive.
Environment
System:
    OS: Linux 6.2 Ubuntu 23.04 23.04 (Lunar Lobster)
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900K
  Binaries:
    Node: 20.6.1 - ~/.asdf/installs/nodejs/20.6.1/bin/node
    Yarn: 3.6.3 - ~/.asdf/installs/nodejs/20.6.1/bin/yarn
    npm: 10.2.1 - ~/other/joist/node_modules/.bin/npm
    bun: 1.0.4 - ~/.bun/bin/bun

https://github.com/jestjs/jest/pull/13417/files#r991756357
Actually the difference lies here.
Some people use detectOpenHandles to detect resources that have not been cleaned up, while most people use it to detect what is preventing the process from exiting.
My initial PR was for the former.
Now since I realize that gc() doesn't collect them 100% of the time, and this causes behavior changes, I will open a PR later to restore this.
By the way, if you remove the reference to servers, it will not be reported. (But this doesn't seem to be 100% true, although I learned from the nodejs repository that v8.writeHeapSnapshot() is more aggressive than gc())
import { promises } from "dns";

const { Resolver } = promises;
const resolver = new Resolver();
let servers = resolver.getServers();
console.log(servers);
servers = null;

describe("foo", () => {
   it("works", () => {});
});

But then a refactor of detectOpenHandles (to dedupe stack traces) regressed the behavior (by removing the check as a potentially speculative clean up separate from deduping the stack traces?): #13417

Oh, yeah, this seems surprising to me, too. That said, I like what that change did to surface multiple open handles from from the same stack trace! While working on #11470 I made a note suggesting something similar, but never had time to get around to it: https://github.com/jestjs/jest/pull/11470/files#r641328430

Some people use detectOpenHandles to detect resources that have not been cleaned up, while most people use it to detect what is preventing the process from exiting.
My initial PR was for the former.

Yeah… I guess I think of its purpose as being specifically about the latter and not about the former, which is why I made the changes in #11470. The --detectOpenHandles docs seem to suggest the same thing:

Attempt to collect and print open handles preventing Jest from exiting cleanly. Use this in cases where you need to use --forceExit in order for Jest to exit to potentially track down the reason.

One of the comments on #13417 suggest the same thing : https://github.com/jestjs/jest/pull/13417/files#r991756357

Now since I realize that gc() doesn't collect them 100% of the time, and this causes behavior changes, I will open a PR later to restore this… I learned from the nodejs repository that v8.writeHeapSnapshot() is more aggressive than gc()

@liuxingbaoyu This is probably not only about GC. In #11429 I added an asyncSleep() call because some resources don’t get cleaned up (not just garbage collected, but not actually released by Node.js internals) until after callbacks from user code run. Since the user code might trigger other things that take some time, it might take a while before some handles that are released as far as JS code is concerned are actually released as far as Node.js internals are concerned.
You shortened that sleep from 100 ms to two sleeps (first 0 ms, then 30 ms). I saw a lot of cases where 0 was not enough (see this change where I realized that: https://github.com/jestjs/jest/pull/11429/commits/0fab1e4cd05e1e86a0597fd4a81999c56832f9ef), but I don’t remember what timings I was typically seeing in my experiments. 30 might be fine, or it might be a bit too short.

Thank you for your extremely detailed explanation!

This is probably not only about GC. In https://github.com/jestjs/jest/pull/11429 I added an asyncSleep() call because some resources don’t get cleaned up (not just garbage collected, but not actually released by Node.js internals) until after callbacks from user code run. Since the user code might trigger other things that take some time, it might take a while before some handles that are released as far as JS code is concerned are actually released as far as Node.js internals are concerned.
You shortened that sleep from 100 ms to two sleeps (first 0 ms, then 30 ms). I saw a lot of cases where 0 was not enough (see this change where I realized that: https://github.com/jestjs/jest/commit/0fab1e4cd05e1e86a0597fd4a81999c56832f9ef), but I don’t remember what timings I was typically seeing in my experiments. 30 might be fine, or it might be a bit too short.

Yes! I forgot about it, some nodejs internal objects need to go through some event loop before they are destroyed.
30ms is just a value I estimate, because now if there are still resources that have not been destroyed after 30ms, it will run a gc.
:)


Bridge request for Twitter Home timeline

Bridge request

I know there already is a twitter bridge, but it doesn't support displaying the home timeline of a user (which merges user tweets and the accouts he follows)
General information

Host URI for the bridge (i.e. https://github.com): twitter.com

Which information would you like to see?

My home timeline on twitter

How should the information be displayed/formatted?

Each tweet should be an independant feed entry

Which of the following parameters do you expect?

[X] Title
[X] URI (link to the original article)
[X] Author
[X] Timestamp
[X] Content (the content of the article)
[X] Enclosures (pictures, videos, etc...)
[ ] Categories (categories, tags, etc...)

Options

[ ] Limit number of returned items

Default limit: 5

[X] Load full articles

Cache articles (articles are stored in a local cache on first request): yes
Cache timeout (max = 24 hours): 24 hours

[X] Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)

Timeout (default = 5 minutes, max = 24 hours): 5 minutes

I would take a look at how to extend TwitterBridge to add home timeline

I think that would require you to be logged into Twitter, which is something RSS-Bridge does not support.

OK, I will close issue and continue to use tweetledee to access my home timeline.

My workaround is to create 2 bridges: One for ?action=display&bridge=Twitter&context=By+username&u=... to get a feed of my own tweets + retweets. Another one ?action=display&bridge=Twitter&context=By+list&user=...&list=follow where "follow" is a Twitter list where I added all Twitter users that I want to follow.
Of course, this is cumbersome if one follows many users. Another drawback is that the Twitter bridge for "context=By+list" does not show the author of the tweet. A similar issue exists for "context=By+username" in case of retweets.


OTG Test - TE-6.2: Route Removal In Non Default VRF

OTG conversion for TE-6.2: Route Removal In Non Default VRF
Fixes #743
Test log link here

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 46.888%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
580

Relevant Lines:
1237

💛  - Coveralls

/gcbrun


[feature] Allow mobile wallet browsers to indicate default injected connector

What problem does this new feature solve?
As of now, when users visit dapps on mobile in-wallet browsers they are presented full choice of wallets with injected mobile wallet being highlighted as installed. We can further improve on this by allowing such wallet browsers to append w3mPreferInjected=true etc. to url and indicate which injected connector to use by default, thus resulting in a more seamless ux (there is no reason to show other wallets to users in these use case).
Describe the solution you'd like

Document w3mPreferInjected=true
Implement w3mPreferInjected=true handling in modal

@nico-limo
Mobile - if OKX is not already submitted in https://cloud.walletconnect.com, you can use this modal option to add it in manually https://docs.walletconnect.com/2.0/web3modal/options#mobilewallets-optional as well as add custom image for it via https://docs.walletconnect.com/2.0/web3modal/options#walletimages-optional
Injected - Web3Modal with wagmi, supports all EIP-1193 compliant wallets out of the box.


Project Title, Description, and Summary

Subtask for Milestone 2 Google Doc

Finished Title, Description and Summary and added to google doc


chore(master): release 1.5.0

:robot: I have created a release beep boop
1.5.0 (2024-04-05)
Features

slashcommands: version command (491d417)

Bug Fixes

template string (49a716a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Blvckleg/BingusBoingus/releases/tag/v1.5.0 :sunflower:


Cloudflare Tunnel ssl issue

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[x] I agree to have read this project Security Policy

Description

👟 Reproduction steps
I followed the steps on the wiki for cloudflared.
👀 Expected behavior
It is supposed to give the website a ssl.
😓 Actual Behavior
I got no ssl for the website
🐻 Uptime-Kuma Version
1.21.3
💻 Operating System and Arch
Ubuntu 22.04 (docker)
🌐 Browser
Brave 1.52.122 (Chromium 114.0.5735.110)
🐋 Docker Version
24.0.2
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Have you added https:// manually at the beginning of url?

@louislam That works but how can i make it automatically make it into https?

This may help:
https://developers.cloudflare.com/ssl/edge-certificates/additional-options/always-use-https/

/\ This helped


[DO NOT MERGE] [Key Vault] Identifier parser feedback after 9642

I merged this PR without addressing all of the feedback: https://github.com/Azure/azure-sdk-for-js/pull/9642
Here's the rest of the feedback, I believe!
Namely:

No more collections.
No validations.
The id property in the result type should be sourceId.

For the item related to cleaning up the generated folder, I've made a new issue: https://github.com/Azure/azure-sdk-for-js/issues/10737
Reviews appreciated.

Added "DO NOT MERGE" to the title since we haven't agreed on the names.

.Net PR is merged by this point: https://github.com/Azure/azure-sdk-for-net/pull/14601

As per Ramya over Teams:

Lets go with parseKeyVaultCertificateId(), KeyVaultCertificateId and sourceId for now. I still find it odd that souceId needs to be present in the KeyVaultCertificateId, but we can log an issue for that to discuss further

/check-enforcer override

/check-enforcer evaluate


coreutils-full depends on bootstrap openssl

Describe the bug
I've built a minimal system and noticed that there are two openssls in the system closure. One of those comes via coreutils-full and is the bootstrap openssl. It's my understanding that this should not leak into the system closure.
Steps To Reproduce
$ nix-store -qR $(nix-instantiate -A pkgs.coreutils-full)| grep openssl
/nix/store/8959fxyfcpqz4bll7wz3y2h40xbzasfg-openssl-3.0.10.tar.gz.drv
/nix/store/cklrwbwi889pp2fdsswdjvn12sdy5i5j-openssl-disable-kernel-detection.patch
/nix/store/gpndc5qlbi8yiyy2wj6k8hk3rhvxrch8-openssl-3.0.10.drv

$ nix-instantiate -A pkgs.openssl
/nix/store/w413fn4wzsw1jrfs8k2xmp4v1nky3y6z-openssl-3.0.10.drv!bin

$ nix-diff /nix/store/w413fn4wzsw1jrfs8k2xmp4v1nky3y6z-openssl-3.0.10.drv /nix/store/gpndc5qlbi8yiyy2wj6k8hk3rhvxrch8-openssl-3.0.10.drv
- /nix/store/w413fn4wzsw1jrfs8k2xmp4v1nky3y6z-openssl-3.0.10.drv:{out}
+ /nix/store/gpndc5qlbi8yiyy2wj6k8hk3rhvxrch8-openssl-3.0.10.drv:{out}
• The builders do not match
    - /nix/store/xdqlrixlspkks50m9b0mpvag65m3pf2w-bash-5.2-p15/bin/bash
    + /nix/store/dsn6vl7x1hbn1akgpxync19gpx2dzy8w-bootstrap-tools/bin/bash
• The set of input derivation names do not match:
    - bash-5.2-p15
    - stdenv-linux
    + bootstrap-stage4-stdenv-linux
    + bootstrap-tools
...

Expected behavior
coreutils-full depends on pkgs.openssl instead of the bootstrap openssl.
Notify maintainers

Metadata
This happens at least for the last couple of years in Nixpkgs. I've tested 20.03 and it has the same issue.

This hacky(?) workaround is:
   coreutils =  callPackage ../tools/misc/coreutils { };
-  coreutils-full = coreutils.override { minimal = false; };
+  coreutils-full = coreutils.override { minimal = false;
+                                        # XXX prevent bootstrap openssl to leak into the closure
+                                        inherit openssl; };


Sending commands to vehicle with specific mav_sys_id

Hi,
I am trying to control multiple vehicles which works in SITL (with docker on MacOS) that stated in with . After I am starting 2 vehicles in SITL, I am changing MAV_SYS_ID parameter and output port of one of them. I know that MAVSDK-Python works with MAVLINK protocol but is there any chance to control vehicle with specific  MAV_SYS_ID? I am asking this because, both of my vehicles have same UUID. You can see my code example attached and it is slightly different from example file named "takeoff_and_land.py"
 .
In this example of code, when I run it, both devices seen connected but arm and takeoff commands only given for first written device. I searched for answer in this Issues section but i couldn't find anything related. I examine source files but I couldn't find the place where I should change. Only there is an issue #102 but it is not done yet as I understood.
If any other suggestions to work this system, I am open for that either.
Thank you for your answer, have a nice day.

Thanks for the question. I hope we can get back to you soon.

when I run it, both devices seen connected but arm and takeoff commands only given for first written device.

Yes, that's exactly what the code should be doing. You do:
await drone1.action.arm()
await drone1.action.takeoff()
await asyncio.sleep(5)
await drone1.action.land()

Which is asking drone1 to arm, takeoff and land 5 seconds later. If you want both drones to do that, you should do something like:
await drone1.action.arm()
await drone2.action.arm()

await drone1.action.takeoff()
await drone2.action.takeoff()

await asyncio.sleep(5)

await drone1.action.land()
await drone2.action.land()

Does that make sense?

Hey, firstly, thank you for your responses. I am sorry, I just notice that I sent screenshot with missing part. Below this piece of code, I already did same commands for drone2. Problem in here as i said, UUID's of both device seen same and even though I am giving commands to drone2, system sends it to the drone1. Because it thinks that they are same device in my opinion.

I am trying to control multiple vehicles which works in SITL (with docker on MacOS) that stated in with . After I am starting 2 vehicles in SITL, I am changing MAV_SYS_ID parameter and output port of one of them. I know that MAVSDK-Python works with MAVLINK protocol but is there any chance to control vehicle with specific MAV_SYS_ID? I am asking this because, both of my vehicles have same UUID. You can see my code example attached and it is slightly different from example file named "takeoff_and_land.py"

As I stated here, I am using docker image that pushed to github by you -which really helped me to run SITL on my device- and when I am running twice this docker image in 2 terminals, they are having same UUID and this leads to misunderstanding from mavlink side as I understand.
I don't know if I could express my problem but I hope I did.
Thank you for your answer again, have a nice day.

The UUID is an issue if both run on the same UDP connection. But that's not your case here: because you run two instances of mavsdk_server, only one of them can bind to e.g. 14540. So you need to tell both instances to listen to a different MAVLink port (and also gRPC port), e.g.:
./mavsdk_server -p 50050 udp://:14540
./mavsdk_server -p 50051 udp://:14541

Then, in the python code, you need to connect the two Systems to the right instance of mavsdk_server:
drone1 = System(mavsdk_server_address="localhost", port=50050)
await drone1.connect()
drone2 = System(mavsdk_server_address="localhost", port=50051)
await drone2.connect()

Finally, you need your two SITL instances to broadcast on a different port. One on 14540 (drone1), and the other one on 14541 (drone2). My px4-gazebo-headless image doesn't do that, though. But there are scripts in PX4/Firmware to run multiple drones, and that should do just that :+1:.


Please invite me to the Recode-Hive GitHub Community Organization

Name
Sk Mirajul Islam
Discord Username (if applicable)
sk_miraj
Additional Context
I am excited to join this community because it’s a hub of collaboration, innovation, and learning. The open-source ecosystem thrives here, offering endless opportunities to contribute to impactful projects, learn from experienced developers, and grow as a professional. By engaging in this community, I hope to share my skills, collaborate with diverse teams, and improve both my technical abilities and my understanding of collaborative software development. The community’s focus on mentorship and fostering an inclusive environment aligns with my desire to give back and learn through hands-on experiences.

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/recodehive/people

Sure, thank you so much!


Refactored the demos

I extracted styles and javascript from all the demo files,
explicitly declared several magic constants in mnist and cifar demos,
unified the javascript for mnist and cifar10 into one js file,
moved js and css files to respective folders and updated references in html
added ability to test with own image in cifar10 and mnist demos
still left to do:
refactor and/or unify the javascript files for the rest of the demos

Whoa, nice! This looks like an extensive commit; I assume you verified that the demos work? I skimmed through the changes but I don't think I'll have time for a thorough look.

Yes, I tested all the demos and they behave correctly. I also checked the console for errors and unimported js/css files, all clear :)

looks good, great, thank you!

My pleasure! Great job on the whole project :)

@pavelpep should it be <image_channels rather than <3 here and here?
Thanks for the work!
(Should I do a pull request if I spot such error?)

@cbovar nice catch! You are correct, it should be <image_channels instead of <3


nydusify convert will download blobs for all platforms

nydusify convert is slow when I convert golang image：
nydusify convert  --source golang:latest --target myrepo/golang:latest

The size of the image is 297.12 MB , but it takes 8 minutes to pull the image :
INFO[2023-03-07T16:38:20+08:00] pulling image docker.io/library/golang:latest  module=converter
INFO[2023-03-07T16:46:38+08:00] pulled image docker.io/library/golang:latest, elapse 8m18.683841192s  module=converter

The size of the tmp/blobs/sha256 directory is 6.2G. It seems that nydusify has downloaded blobs for all platforms.
nydusify version:
nydusify -v
Nydusify version
Version	: v2.2.0
Revision	: a38f6b8d6257af90d59880265335dd55fab07668
Go version	: go1.18.10
Build time	: 2023-03-01T10:03:11

Thanks for the report, this is indeed a bug, will fix it later.

Hi @mofishzz, it has been fixed in https://github.com/dragonflyoss/image-service/pull/1146, PTAL.


EPUB: Fix broken links

This brings us down to 10 epubcheck warnings. This is done with a lua filter that rewrites links with regular expressions.
References #480.

Your comment says:
-- Performs the following transformations on Links:
--
--     Case 1:
--         [text]({{ site.baseurl }}/stuff/#more-stuff) -> [text](#more-stuff)
--     Case 2:
--         [text]({{ site.baseurl }}/stuff/)        -> [text](#stuff)
--
-- Links that do not match the forms above are kept as is.

Isn't that the wrong rewrite? It seems this would send /DeBruijn/ to #DeBruijn, which is wrong, and /DeBruijn/#11370 to #11370 which is also wrong?

The tag #DeBruijn works because of the following code in rewrite-links.lua:
-- Add identifiers to chapter headings (level 2). The identifier is based on the
-- 'permalink' field of that chapter's YAML metadata block.
function Header (el)
    if el.level == 2 then
        local title = pandoc.utils.stringify(el.content[1])
        el.identifier = title:match("^(%w+):")
    end
    return el
end

which transforms headers of the form
# DeBruijn: other stuff

to the form
# DeBruijn: other stuff {#DeBruijn}

The header above can now be referenced from any markdown document included in the EPUB (not just DeBruijn.lagda.md) like so: [this is a link to DeBruijn](#DeBruijn). This works because pandoc essentially concatenates all the markdown files together when making the EPUB.
Did I address your concern?

By the way, when mapping /DeBruijn/#11370 to #11370, I'm assuming that there isn't another link with the name /DeBruijn/#11370 (which would also map to #11370).

This works because pandoc essentially concatenates all the markdown files together when making the EPUB.

Ah! I suspected as much. Not incredibly neat, but I suppose it works.

By the way, when mapping /DeBruijn/#11370 to #11370, I'm assuming that there isn't another link with the name /DeBruijn/#11370 (which would also map to #11370). This simplifies the link transformation since we don't need to know which chapter #11370 is in.

I don't know for sure, but I don't think we can guarantee this? However, I'd have to investigate.

Oh, right. You said:

This works because Pandoc essentially concatenates all the markdown files together when making the EPUB.
However, that's done in include-files.lua, isn't it? That script is already generating the chapter headings:

-- Before shifting headings, add a title heading at the beginning of the chapter.
local heading = pandoc.Header(1, pandoc.Str(pandoc.utils.stringify(document.meta.title)))
document.blocks:insert(1, heading)

At this point, we have both the filename and the chapter name. Therefore, we could traverse all anchors in the chapter and prefix them with the chapter name, e.g., name="<anchor>" to `name="-".
We then wouldn't have to worry about collisions in the IDs assigned by Agda, and just traverse all the links in the document and map {{ site.baseurl }}/<chaper>/#<anchor> to #<chapter>-#<anchor>.

However, that's not something Pandoc does out of the box, right?

I'm not totally sure, but I believe pandoc does do it out the box. This article Making an ebook with pandoc.

At this point, we have both the filename and the chapter name. Therefore, we could traverse all anchors in the chapter and prefix them with the chapter name, e.g., name="" to `name="-".
We then wouldn't have to worry about collisions in the IDs assigned by Agda, and just traverse all the links in the document and map {{ site.baseurl }}//# to #-#.

That's what I wanted to avoid doing 😛 . But now that you describe its benefits, it does sound like a more robust solution. I'll look into that!

@wenkokke Just pushed my changes. I'm now generating header identifiers the way you recommended.

Just pushed the new changes, thanks for the super quick review!

Thanks, @mreed20!


Improve modal accessibility

I'm attempting to improve the accessibility of some angular-ui modals, and am wondering if more can be done out of the box to make them workable by default. In general, modal accessibility is a bit complex and app developers almost always get it wrong, so it'd be great if the default experience could be better. But I'm unfortunately not familiar with Angular internals, so I'm hitting a bit of a wall. I've built accessible modals outside of Angular, so let me spec out what is required and see what improvements might be made.
You're already setting role="dialog" which is a good start, but there's a lot more that can be done. Here is a good primer:
https://www.marcozehe.de/2015/02/05/advanced-aria-tip-2-accessible-modal-dialogs/
TLDR:

Modals need an aria-labelledby and aria-describedby set to IDs of their titles and their descriptions, respectively. It's almost always safe to set aria-labelledby to the title heading or div, but perhaps an optional directive could be added for cases when this algorithm is wrong.

aria-describedby is set on the dialog's text, if applicable. This is harder to get right algorithmically, so perhaps a directive would do the trick.

Focus needs to be set within the dialog to its default control. Here another directive would be useful, but another algorithmic fallback would be assigning focus to the first focusable dialog content.

Not in the article, but a gotcha that stumped me for hours: all other document content elements need aria-hidden=true, but the dialog parent needs aria-hidden=false. I did this by surrounding all my top-level, non-dialog page content in a separate div, then concatenating the dialogs outside that. I.e.

    ...page content

    ...

When alertDialog is shown, chrome gets aria-hidden=true and focus is redirected to the dialog. When it vanishes, chrome gets aria-hidden=false. There seems to be a backdrop element added. If that encompasses all non-modal content, it might be enough to set that to aria-hidden.
This all involves populating dialog titles and descriptions with IDs, or perhaps referring to existing IDs if they're already set. Unfortunately I don't know enough about Angular internals to pull this off.
It'd be great if the out-of-the-box experience for your dialogs can be improved. I was just looking at another library that uses yours, so the trickle-down of this change would be pretty impressive. Happy to help in an advisory/testing capacity if needed.
Thanks!

Hi guys, Im implementing the feature to ensure that "tab" key only will change focus inside the modal, bootstrap makes this, but I found one problem.
In angular-ui bootstrap we support modal stack, but in boostrap not as you can look in this issue https://github.com/twbs/bootstrap/issues/5431.
So, when I implemented the feature the test "$modal multiple modals it should allow opening of multiple modals" fail with error "Maximum call stack size exceeded" as expected.
What do you suggest?

Closing in favor of #4772.


⚠ Bofrost.nl has degraded performance

In 130a474, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 2033 ms

Resolved: Bofrost.nl performance has improved in f84f88c.


Show when was the ticket last updated.

Currently we can see when was the ticket created , we want to see when was it last updated with changes as well.

May I resolve this issue?
Suggested Changes

Last updated time should be shown below ticket creation time.
And there should be mention which time is creation time and which one is updation time.

Hi,
Yes you can resolve the issue 👍🏼
Implement the suggested changes .
On Wed, 25 Dec 2024 at 10:36 PM, Madhav Dhall @.***>
wrote:

May I resolve this issue?
Suggested Changes

Last updated time should be shown below ticket creation time.
And there should be mention which time is creation time and which
one is updation time.

—
Reply to this email directly, view it on GitHub
https://github.com/IMGIITRoorkee/Ticketify/issues/12#issuecomment-2561953823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFJUWYCMM33S6RDCHSF3H432HLQZFAVCNFSM6AAAAABTVOSTFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRHE2TGOBSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Kindly review the PR linked @himani-r5


Error on Build

HI There,
I have a problem on installation via yarn:
https://gist.github.com/waynevanson/2e3bdd68da8f22cb702e5f17c1fc5dcb
If I download just this package, it should work right? I'm running Linux and have never dealt with these kind of issues beforehand. ANY guidance is appreciated.

Hello, sorry for the delay, I've been offline for quite a while.
So, as I can see the problem has to do with C++ addon compilation during installation. Most likely it is a C++11 related problem.
I have a Linux CI for this package, it shows no sign of errors you have. That means your invironment is probably different. Could you please check which version of GCC (if not CLANG) you have in the system? To compile this addon you will need at least 4.5+
PS: N-API will probably fix that kind of struggle altogether, when I get to it, some day.

Thank you for replying.
$ gcc --version
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

CLANG not installed.
So this package is not using N-API, is that correct?

The addon is written with V8 api. When I rewrite it to N-API, there will be no compilation step on the user side.
Ok, here's what I found: "gcc-7 requires include  for std::function". So you probably can switch to gcc6 for the installation to succeed. And in the meanwhile I will also add #include <functional> to the module, but unsure if today.
Note that this module is far from completion and only few classes work, the rest are yet to be filled with the implementations. So if you find a part of functionality missing, feel free to create more issues or PRs to speed it up.

This package is now released as N-API addon, so it doesn't have the compilation step during the installation. See<EMAIL_ADDRESS>


Include census builder git commit sha1 in census

Options:

Include as metadata in the census SOMA object metadata.
Include as new file in the cell-census storage dir.
Include in releases.json.

Option 1 seems best, but requires a schema change.
Option 2 is easiest, but a bit messy (adds a new, loose file).
Option 3 would be reasonable if/when we automate updating of releases.json. Also, doesn't connect the git commit as tightly as other options.

Option 1 seems best to me. I don't think it requires a schema change, as long as it does not conflict with other schema fields.  There are already lots of other metadata stored in that collection for similar reasons, and not documented in the official schema.

For the first option that Andrew mentions there may be some confusion as to what "metadata" we are referring to.
It could be interpreted for the sha1 to be included in either of:
a) census["census_info"]["summary"] as an extra row  -- This requires a schema change.
b) census._metadata as an extra key-value pair -- This does not require a schema change.
Currently census._metadata has the following keys ['census_schema_version', 'created_on', 'cxg_schema_version', 'soma_encoding_version', 'soma_object_type']. These likely the metadata bruce is referring to.

Can I get a brief explanation of the reason to include the sha1 commit in the the census build? I can give better guidance upon that.
For example, is this intended only for internal purposes?

Can I get a brief explanation of the reason to include the sha1 commit in the the census build?

Reproducibility: 1) "how exactly was this census built?" The sha1 provides the answer. 2) It can be used to infer which version of the API was can access the census, though we might want that to be a more explicit API release version than a SHA1
Internal: Troubleshooting any build issues, particularly between census builds where data may have changed in an unexpected way.  We can diff code between the builder SHA1s.

census._metadata sounds like the right place to me

Got it! Thanks, and yes I agree with census._metadata for this uses. So let's go with that option.
Discussion -- Do you have a recommendation for where to document what's been stored census._metadata or do you think it is fine to leave it as self explanatory.? Most external users and some internal users are likely to be unaware of it.

Do you have a recommendation for where to document what's been stored census._metadata or do you think it is fine to leave it as self explanatory.?

I don't think these fields will be self-explanatory to everyone, so documentation can't hurt.  I do see the issue with putting it in the schema doc itself, since this is metadata about the "physical" SOMA object and not the scientific data it embodies. So not strongly advocating for that. But I don't know where else to put this other than in a README in the repo.
(Some of the existing _metadata fields could be part of the schema, arguably! E.g., it should be able to self-report its own version.  But this becomes a philosophical debate about the nature of the schema.)


URLLIB  ERROR:HTTP ERROR 428.

DevTools listening on ws://<IP_ADDRESS>:54496/devtools/browser/23b59684-c0ff-437a-b6ab-281edcb07bdf
[0516/171602.913:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[0516/171606.190:INFO:CONSOLE(465)] "An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.", source: https://imasdk.googleapis.com/js/sdkloader/ima3.js (465)
[0516/171606.199:INFO:CONSOLE(0)] "An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.", source: about:srcdoc (0)
[0516/171606.370:INFO:CONSOLE(0)] "Access to XMLHttpRequest at 'https://ao-block-ater.mushroomtrack.com/bcdn_token=d6CCUMif4eXwH5tm5XG0ioOjhYxJn44Gdsad237Vv_Q&expires=1684235763&token_path=%2Fvod%2F/vod/8000/8803/8803.m3u8' from origin 'https://jable.tv' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.", source: https://jable.tv/videos/salo-017/ (0)
[0516/171607.605:INFO:CONSOLE(0)] "Access to XMLHttpRequest at 'https://ao-block-ater.mushroomtrack.com/bcdn_token=d6CCUMif4eXwH5tm5XG0ioOjhYxJn44Gdsad237Vv_Q&expires=1684235763&token_path=%2Fvod%2F/vod/8000/8803/8803.m3u8' from origin 'https://jable.tv' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.", source: https://jable.tv/videos/salo-017/ (0)
[0516/171607.642:INFO:CONSOLE(0)] "Uncaught (in promise) undefined", source: https://jable.tv/videos/salo-017/ (0)
result: <re.Match object; span=(52100, 52258), match='https://ao-block-ater.mushroomtrack.com/bcdn_toke>
m3u8url: https://ao-block-ater.mushroomtrack.com/bcdn_token=d6CCUMif4eXwH5tm5XG0ioOjhYxJn44Gdsad237Vv_Q&expires=1684235763&token_path=%2Fvod%2F/vod/8000/8803/8803.m3u8
Traceback (most recent call last):
File "main.py", line 26, in
download(url)
File "D:\SoftWare\jabletvdownload\download.py", line 60, in download
urllib.request.urlretrieve(m3u8url, m3u8file)
File "D:\SoftWare\Python\lib\urllib\request.py", line 247, in urlretrieve
with contextlib.closing(urlopen(url, data)) as fp:
File "D:\SoftWare\Python\lib\urllib\request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "D:\SoftWare\Python\lib\urllib\request.py", line 531, in open
response = meth(req, response)
File "D:\SoftWare\Python\lib\urllib\request.py", line 640, in http_response
response = self.parent.error(
File "D:\SoftWare\Python\lib\urllib\request.py", line 569, in error
return self._call_chain(*args)
File "D:\SoftWare\Python\lib\urllib\request.py", line 502, in _call_chain
result = func(*args)
File "D:\SoftWare\Python\lib\urllib\request.py", line 649, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 428:

也遇到了 ........


Update URL value in box-edit cask for latest version

This afternoon I tried to install the box-edit cask but received 404 errors. After looking at Box's site for downloads it appears the URL to the disk image has changed.
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[*] brew cask audit --download {{cask_file}} is error-free.
[*] brew cask style --fix {{cask_file}} reports no offenses.
[/] The commit message includes the cask’s name and version.
This is my first attempt to contribute to homebrew-cask and am not sure if I hit all these points exactly as you like but I'm happy to improve.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Thank you for your contribution.


Archive node pruning

Opening this to test my SQL changes. Do not review yet. This is now ready for review.
Checklist:

[ ] Tests were added for the new behavior
[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

This PR

adds support for pruning blocks and their commands from the archive database

this accepts any of block height, number of blocks (from maximum recorded block), timestamp
the implementation is a thin wrapper around a sequence of SQL delete statements

restructures the toplevel archive CLI to support multiple subcommands

previous toplevel command is now under run, new command is prune

keep it in archive node and make sure the pruning doesn't delete the genesis block.

I think this is probably the right approach. I'll try to figure something out.

I interpreted

For example, anyone running your Data API implementation should be able to optionally configure the node to delete historical state related to blocks that are over 1000 blocks old.

As meaning that the archive node would automatically continuously delete blocks over 1000 blocks old (ie only ever have 1000 blocks in storage). It's valuable to have this one-off command too, though.

If we have that, coda client status (or maybe another command) should reveal that windowing.

keep it in archive node and make sure the pruning doesn't delete the genesis block.

I think this is probably the right approach. I'll try to figure something out.

I changed my mind on this, GraphQL command is added in #5367.

If we have that, coda client status (or maybe another command) should reveal that windowing.

@psteckler I'm not sure that we can add this there, since it's a property of the archive node rather than the coda daemon.

I've updated the SQL that this uses. This now

stops automatically removing the internal commands from blocks, since they may be identical to other internal commands

this was causing the unit test failure

uses more idiomatic SQL for the user-command and block deletions
tidies up the unused internal commands, ledger hashes and public keys

these were previously overlooked

expands the scope of the unit test to check that the commands are properly preserved or deleted, as appropriate.

Note that we still don't tidy up 'unused' user commands, since they may have been registered when entering the pool but not yet entered into a block.


core::SymbolRef() -> core::Symbols::noSymbol()

Motivation

We should be more explicit. Nearly every new usage of this was introduced in
#3859, merged a few hours ago.
Test plan

Existing tests.

thanks my droogs


Implement Gradle plugin

Need to implement gradle plugin, which will be available from gradlePluginPortal - https://plugins.gradle.org/
plugin id dev.icerock.gradle.shaper
plugin should support adding local list of template directories by git or local paths, also should support overriding of any params.
plugin should create gradle task shaper. when we run this task gradle should read 2 args of cli - first is template name, second is output directory. also all interactive logic should be used too (filling of params)
configuration sample:
plugins {
    id("dev.icerock.gradle.shaper") version("0.4.0")
}

shaper {
    templates {
        git("https://github.com/icerockdev/shaper-templates.git")
        directory(file("templates"))
    }
    params {
        set("packageName", "dev.icerock.sample")
    }
}

usage sample:
./gradlew shaper kmm-template mpp-library/feature

can be helpful - https://github.com/strongself/Generamba/wiki/Rambafile-Structure


Carthage support?

It'd be nice to document how to use EarlGrey with Carthage.
I read through configure_earlgrey_pods and my guess is that Carthage isn't supported at this time.

@bootstraponline, we have Carthage support in the roadmap and will add in in the upcoming releases. Thanks.

It'd be nice to share the EarlGrey scheme. Currently it's possible to add EarlGrey to Cartfile.private and it'll pick up the 1.0.0 tag.

github "google/EarlGrey" ~> 1.0.0
Unfortunately Carthage is unable to build EarlGrey since the only shared scheme is for OCMock. Example of sharing the scheme.

@bootstraponline, would you take a look at https://github.com/google/EarlGrey/pull/65/files and check it that works? I'll send a PR out for Swift support as soon as this is in.

thanks, I'll test it right now

Fixed by https://github.com/google/EarlGrey/issues/65


Using connect and mapStateToProps not providing the updated state.

I am using react-data-grid and redux store to save the data user inputs on the grid/table. To access the current state, I am using props from mapStateToProps method.
But mapStateToProps is not providing the updated state.
Refer: Line numbers 151 to 156 of:
https://github.com/rupav/candis/blob/4bee19750b9449137ad85e99fdc38e1fdb52f996/candis/app/client/app/component/widget/DataEditor.jsx
props.row.update() on Line num 151 updates the redux-store (rows value), which is not gets reflected in the next call from mapDispatchToProps Line num. 156 . Although accessing store directly (without connect), provides me the updated state: Line num. 154

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

Sure, link to question: https://stackoverflow.com/questions/51691645/using-connect-and-mapstatetoprops-not-providing-the-updated-state


MP metrics ignores class-level annotation for a method with a method-level annotation of the same type

Environment Details

Helidon Version: 1.x, 2.x
Helidon SE or Helidon MP MP
JDK version: n/a
OS: n/a
Docker version (if applicable): n/a

Problem Description
The MP spec allows annotations at both the class level and the method level. For example, here is the text for @Counted:

When a type/class is annotated, the implementation must register a counter for each of the constructors and non-private methods using the Annotated Naming Convention.

When a non-private method is annotated, the implementation must register a counter for the method using the Annotated Naming Convention.

It would seem that, although the spec does not mention this scenario explicitly, if the same type of annotation (e.g., @Counted) is used at the class level and on a method, then two metrics would be created and updated when that method is invoked.
In fact, Helidon currently implements only the explicit method-level metric in this case; the method-level metric implied by the class-level annotation is neither created nor updated.
Steps to reproduce

In the existing HelloWorldResource in MP metrics tests, add @Counted(name = "classLevel") at the class level.
To the message method in that class, add @Counted(name = "methodLevel", absolute = true). (The absolute setting is not necessary but makes finding the counter metric slightly easier.)
Set a breakpoint in one of the tests (e.g., HelloWorldTest#testMetrics).

The this.registry field which holds all the application metrics contains the counter for the explicit method-level annotation, but no counter implied by the class-level annotation.

In an exchange on the MP metrics gitter discussion, I confirmed that this is indeed an ambiguous area of the spec but that the TCK does not care one way or the other. Because it is possible that some Helidon users already count on the existing behavior, this is not a bug so I am closing it.


Zally issue creation sometimes omits commits

We observed that some of the merges in this repository don't create a Zally issue, when they should have done so.
Examples:

#579 (build), #598 (build)

Analysis:
It looks like the result of https://api.github.com/repos/zalando/restful-api-guidelines/pulls/598/files (and similar) didn't return useful results (possibly an error?), which resulted in a error of jq, and then the rest of the script thought that nothing changed, and decided not to create a Zally issue.
GitHub's commit information API lags a bit behind the actual commits. So when it doesn't return anything, we might need to wait a bit and retry, when this happened.

Other missed (and relevant) PRs:

#564 (compound key identifiers),
→ manually created as https://github.com/zalando/zally/issues/1182
#560 (naming conventions for enums)
→ manually included in https://github.com/zalando/zally/issues/1183

Potential (partial) solution:

wait a moment before fetching the files for a merged PR.
(if feasible) in the error case, wait a bit and try again
in case of doubt, create an issue

We invested a bit more time to figure out what happened.

The travis-deploy.sh script is trying to figure out which PR belongs to the merge commit. It is using jq's capture("#(?<n>[0-9]+) ") to find the PR number from the merge commit. This finds Merge pull request #591 from zalando/gh-589-fix-link, but not Added naming convention for enums (#560). If it fails, no issue is created.
After that, the script is trying to look at the files for the PR, to check whether a file in chapters changed.
This sometimes fails, because the Github API doesn't return any data yet – in this case, no issue is created.

To make it more robust, we would need to:

fix the regexp
add a loop for the second request too
as a fallback, if we didn't get anything, still create an issue.

Lets assume that #628 was finally fixing the issue.


chunking_eval_experiment

Identifying the best documents chunking strategy is key Building GenAI solution powered By RAG
Finding the right combination of the Chunking Strategy, Chunks size and Chunks overlap is a balance between responses accuracy, latency and cost
The goal of the notebook is to define a tool / framework allowing to test quickly multiple combinations of the three parameters above
This notebook demonstrates how to  evaluate different chunking strategies, chunk sizing and overlap using RAGA framework for evaluation, Claude 3 Sonnet on Bedrock for LLM, FAISS for Vector Store and RAGA for Evaluation
tools and libraries used

LLM : anthropic.claude-3-sonnet on Bedrock
Embbeding: amazon.titan-embed-text-v1 on Bedrock
Vector Store: FAISS
RAG Retriever results evaluation :RAGA  (context_recall,context_precision, answer_relevancy)
Evaluated Chunking strategy

NLTKTextSplitter
LatexTextSplitter
MarkdownTextSplitter
RecursiveCharacterTextSplitter
SpacyTextSplitter

Dataset: AWS 2019-2022 Shareholder-Letter

Workflow

Install required libraries
Create a bedrock Client
Load documents example in a local folder
Use a custom function "textsplitterStrategy" with 3 params : Strategy , chunk size and overlap
Run the function for 5 chunking strategies and load the documents in FAISS (5 stores)
Use Claude3 Sonnet and RAGA to evaluate context_recall,context_precision, answer_relevancy
plot the evaluation results

Please re do this PR following the new layout and the process for creating the required file . We request all files to have a presence on the Cookbook / Recipes Website which is fronting this github repo now. Some of the mandatory sections of the notebook need to include

Overview.
What are we demonstrating .
What use case .
What will you learn.
What is the architectural pattern and why we select this. With a diagram
What are the libraries to install
What model did we choose and why this model
Every cell needs to have a markup


interfaces with a generic type that imported automatically has different behavior with manually

Describe the bug
interfaces with a generic type that imported automatically has different behavior with manually
typings.d.ts
export interface Response<T>{
     data: T
}

vite.config.ts
{
     from: 'src/typings/response.d.ts',
     imports: ['Response']
     type: true,
},

auto-import.d.ts
declare global {
      export type { Response } from 'src/typings/response.d.ts'
}

However, when it comes into usage:
// an error occurs, it says that Type 'Response' is not generic.
const result: Response<string> = await fetch(url)

But if I import it manually:
// it works.
import type { Response } from '@typings/response'
const result: Response<string> = await fetch(url)

Reproduction
https://stackblitz.com/edit/vitejs-vite-reqjfj?file=vite.config.ts,src%2Ftypings%2Fresponse.d.ts,src%2FApp.vue,package.json,src%2Fmain.ts&terminal=dev
System Info
System:
   OS: Windows 10 10.0.19045
   CPU: (12) x64 AMD Ryzen 5 3600X 6-Core Processor
   Memory: 5.85 GB / 15.95 GB
Binaries:
   Node: 20.9.0 - C:\DevTool\node\node.EXE
   Yarn: 1.22.21 - C:\DevTool\node\yarn.CMD
   npm: 10.1.0 - C:\DevTool\node\npm.CMD
   pnpm: 8.10.5 - C:\DevTool\node\pnpm.CMD
Browsers:
   Edge: Spartan (44.19041.3636.0), Chromium (119.0.2151.58)
   Internet Explorer: 11.0.19041.3636

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

I don't think there is a way to solve this. The issue is because there is a built-in global type Response exists, and we can't override it. I'd suggest to rename the type to be more explicit.


Not able to crosscompile libocpp for arm processor

OCPP Version
OCPP1.6
Describe the bug
Make Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.83.0/BoostConfig.cmake:141 (find_package):
[cmake]   Found package configuration file:
[cmake]
[cmake]     /usr/lib/x86_64-linux-gnu/cmake/boost_log_setup-1.83.0/boost_log_setup-config.cmake
[cmake]
[cmake]   but it set boost_log_setup_FOUND to FALSE so package "boost_log_setup" is
[cmake]   considered to be NOT FOUND.  Reason given by package:
[cmake]
[cmake]   No suitable build variant has been found.
[cmake]
[cmake]   The following variants have been tried and rejected:
[cmake]
[cmake]   * libboost_log_setup.so.1.83.0 (64 bit, need 32)
[cmake]
[cmake]   * libboost_log_setup.a (64 bit, need 32)
[cmake]
[cmake] Call Stack (most recent call first):
[cmake]   /usr/lib/x86_64-linux-gnu/cmake/Boost-1.83.0/BoostConfig.cmake:262 (boost_find_component)
[cmake]   /usr/share/cmake-3.28/Modules/FindBoost.cmake:594 (find_package)
[cmake]   /home/pheonix/EVerest_OCPP/everest-workspace/liblog/CMakeLists.txt:28 (find_package)
[cmake]
To Reproduce
No response
Anything else?
No response

Hi,
We are cross compiling for ARM so it is possible for sure. It looks like it is complaining that the boost libraries installed are 64 bit and it needs a 32 bit library. That might be something to investigate.
Kind regards,
Marc

Hi marc,
Thanks for your response could you help with the process to crosscompile it would be of great help


Subgraph isomorphism: meet SDL requirements

graph_status is removed
function renaming
added some asserts

/intelci: run

/intelci: run

/intelci: run

@Mergifyio backport rls/2021.3-rls


Angus Council mixed content issues

Accessing resource downloads for some websites that are HTTP-based like Angus Council aren't working due to mixed content restrictions on modern browsers.
For example, this dataset: https://opendata.scot/datasets/angus+council-school+covid-19+-+positive+cases+and+isolations/
has a link to http://data.angus.gov.uk/geoserver/services/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=services%3Aedn_schoolscovidcases2&outputFormat=csv
which actually redirects via HTTPS to https://data.angus.gov.uk/geoserver/services/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=services%3Aedn_schoolscovidcases2&outputFormat=csv if opened in a new tab. This doesn't work when trying to download in the same tab though and creates the following error:

Potential fixes

Speak to publisher (Angus Council) and ask them to fix their HTTPS redirects (hard)
Write some sort of URL rewriting tool to convert all the links to HTTPS (medium?)

Addressed in https://github.com/OpenDataScotland/jkan/pull/38


Property 'ref' does not exist on type 'IntrinsicAttributes & FastOmit<ViewProps, never>'.

Environment

System:

OS: macOS 13.4.1
CPU: (8) arm64 Apple M1
Memory: 105.88 MB / 16.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 18.16.1 - ~/.nvm/versions/node/v18.16.1/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.5.1 - /opt/homebrew/bin/npm

npmPackages:

styled-components: ^6.0.7 => 6.0.7

Reproduction
codesandbox

Any solutions?

I am also having this issue. It appears this is an issue for V6 versions and makes styled-components V6 unusable for react-native.

FYI - I've found that if you use styled as a function rather than using the static properties, refs seem to type properly:
This example does not work:
import React, { useRef } from 'react';
import { TextInput } from 'react-native';
import styled from 'styled-components/native';

const StyledTextInput = styled.TextInput.``;

function App(): JSX.Element {
  const ref = useRef(null);

  return (
      <StyledTextInput
        ref={ref} //  Type '{ ref: MutableRefObject<null>; }' is not assignable to type 'IntrinsicAttributes & FastOmit<Substitute<FastOmit<TextInputProps, never>, FastOmit<{}, never>>, keyof ExecutionProps> & FastOmit<...> & { ...; }'
      />
  );
}

This example does work:
import React, { useRef } from 'react';
import { TextInput } from 'react-native';
import styled from 'styled-components/native';

const StyledTextInput = styled(TextInput)``;

function App(): JSX.Element {
  const ref = useRef(null);

  return (
      <StyledTextInput
        ref={ref}
      />
  );
}

+1

FYI - I've found that if you use styled as a function rather than using the static properties, refs seem to type properly:
This example does not work:
import React, { useRef } from 'react';
import { TextInput } from 'react-native';
import styled from 'styled-components/native';

const StyledTextInput = styled.TextInput``;

function App(): JSX.Element {
  const ref = useRef(null);

  return (
      <StyledTextInput
        ref={ref} //  Type '{ ref: MutableRefObject<null>; }' is not assignable to type 'IntrinsicAttributes & FastOmit<Substitute<FastOmit<TextInputProps, never>, FastOmit<{}, never>>, keyof ExecutionProps> & FastOmit<...> & { ...; }'
      />
  );
}

This example does work:
import React, { useRef } from 'react';
import { TextInput } from 'react-native';
import styled from 'styled-components/native';

const StyledTextInput = styled(TextInput)``;

function App(): JSX.Element {
  const ref = useRef(null);

  return (
      <StyledTextInput
        ref={ref}
      />
  );
}

Using styled(TextInput) worked for me, but this doesn't smell good

Same here. TS now throws "Type 'RefObject<TextInputProps & { value: string; setNativeProps: ({ text }: { text: string; }) => void; focus: () => void; }>' is not assignable to type 'Ref | undefined'"

Same issue.
Using styled(View) works though.

+1


Problems with memfile_buffer_count > 1

Problem Description
We do have a problem with out of order messages receiving with a memfile_buffer_count > 1  and more than one subscriber.
For the shown usecase we have two subscribers (one of them checking the order of the incoming messages), and one publisher.
(Memfile acknowledge turned OFF)
At a higher frequency (e.g. ~60Hz), setting buffer count to 2 leads to multiple messages arriving out of order.
This also leads to eCAL Monitor reporting package losses (which might not actually be package losses, just, well, packages arriving out of order).
memfile_buffer_count = 2

memfile_buffer_count =  1

Some "fun facts":

These measures were taken when debugging from VS Studio (RelWithDeb mode).
With a buffer count of 2, the send frequency is significantly lower, than with one
Without the debugger attached there are no package losses and no out of order messages. So it is probably some timing problems in

The issue has also been discussed here: #986
How to reproduce
Checkout https://github.com/eclipse-ecal/ecal/tree/feature/out-of-order-messages and run either test_pubsub (contains a test for this scenario) or the triple
message_out_of_order_publisher
message_out_of_order_crazy_subscriber
message_out_of_order_lazy_subscriber

How did you get eCAL?
I don't know
Environment
Current master build of eCAL, Windows
eCAL System Information
No response

Just one small update, we do get out of order messages while debugging, even in an 1:1 scenario (no blocking subscriber).

Fixed by #1022

May I know if this is a real fix or just a work around to reject out of order? Rejecting it is not ideal as i will have gaps in the data if it is supposed to be time series (IMU data for integration). Would like to know the root cause.

No, atm this is just a workaround.
I really did a lot of debugging, i was able (in debug mode only) to reproduce the issue on Windows, but not really pin it down.
With the current implementation, there are X different threads, waiting for signalling on X mutexes for the X memory files. They are basically acting independently, and there is nothing that can be done to prevent this from happening 😞
Anyways, I would really recommend to set memfile_buffer_count = 1, or are you experiencing problems with this setting? In theory you can achieve higher write speeds with  > 1, but in reality, in most cases it is sufficient.

@KerstinKeller Thanks for the insights. Yes, I understand now the implementation. I few pointers:

Yes I am currently reverting back to buffer count = 1.
The reason I want to have multiple buffer, is that i want to have less chance of losing high frequency data. But now the contrary happens, sadly.
What makes more sense as the implementation, is to have one publisher and one subscriber and multiple memory files. One subscriber will make sure reading sequence can be predicably controlled. The one publisher, can publish to the first buffer when it is released by the subscriber, and if not, try write to the next buffer. It is more like a circular buffer implementation here.
The reason why this is helpful, is that the subscriber thread may not be waken up by Linux kernel that frequently, and publisher may send the message in bursts (e.g. IMU packets may contain a few measurements in a single USB callback, so ecal publisher would be sending a few messages back to back). So having a >1 circular buffer would help.

@chengguizi @KerstinKeller Hi guys, I also met this problem using the 5.12 release. In my case, the topic frequency is 100 with only one subscriber. Do you have any solutions to fix the drops or unordered msgs?

Are you using 5.12.1? The problem should have been fixed there...

Are you using 5.12.1? The problem should have been fixed there...

Hi there, actually 5.12.0. I only use UDP publisher to fix this dropping problem of shm. 1 mem file causes drops with no error logs and 2 mem files cause unordered msg.

Do you have anything that can reproduce the drops? Have you activated the acknowledgement to prevent drops?

Hi, it would be really good to better understand your use case. So if you switch to local udp transport, do you still get the 100 Hz pub/sub transmission frequency? If not then probably your subscriber is "to slow" to process the data. If this would be the case you can simple switch on the shm acknowledgement feature as @KerstinKeller recommended. Then you force the publisher to block until the memory is copied and processed by the the subscriber and you should not loose data anymore.

Hi, my 100-hz publisher is publishing msg processed from the power board. And I also have a 1000-hz publisher with IMU data. These subscriber's callback functions will not block, and there will be no frequency reduction if I switch on only UDP mc mode.

Do you have any code to reproduce the behavior? What platform exactly are you running on?


patchy fixes for elliptic pairing precompiles

to_big_endian was returning numbers in Montgomery representation. This converts them to standard, as ecadd and ecmul precompiles expect https://github.com/ethereum/EIPs/pull/213

Thank you, I've confirmed that the tests are passing now. @NikVolf This should be an additional conversion function though as ethereum precompile representation is of no concern to this library.


Add Errorbars class

Potential solution for default error bar style values. In plain.yml, write :
colour: "same as curve"
line_width: "same as curve"
...
Then, when plotting, as usual, check if value for parameter "colour" is given. If not, use default value specified in plain.yml. But if specified value if plain.yml is "same as curve", check what the values are for the curve and set those for the error bars instead.


avoid loose conditions in rules and macros

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
This PR mitigates possible bypasses due to too loose conditions.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

rule(macro: python_running_sdchecks): macro removed
rule(Change thread namespace): remove python_running_sdchecks exception

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from leogr after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 69823b7e6d4ad3a9994f269be54344081e3c5849

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Plan for updating the Type Provider Authoring SDK

We need to update the Type Provider Authoring SDK (currently called FSharp.TypeProviders.StarterPack).
This is most urgently driven by two needs: using type providers when compiling PCL and .NET Core components.  We also need our type providers to be "portable" where possible, so that they can at least be used regardless of whether the F# compiler is run using .NET Core or .NET Framework.
Here are the steps to happiness:

Support the authoring of type providers which can do PCL code generation when running in a .NET Framework hosted compiler.  See PR #78.  Also put in place basic testing and better CI in this repo, see also PR #78
Support the authoring of type providers which can do CoreCLR (or “platform standard”) code generation when running in a .NET Framework hosted compiler.  This should just be a matter of finding the right reference DLLs.
Support the authoring of type providers which can do CoreCLR (or “platform standard”) code generation when running in a CoreCLR hosted compiler.  This may be trickier as all the code in the SDK needs to be made CoreCLR-friendly
Support the authoring of type providers which are themselves PCL or CoreCLR or “platform standard” components, and can be used in binary form in either compilers, and can generate code for any target.  This should drop out for free from step 3, but we need to check & test
Rename the SDK to "FSharp.TypeProviders.Authoring" or the like
Greatly improve the docs, for example addressing #66.  We would like the docs to be at least as good as the MSDN docs and walkthroughs.

As part of this I will improve and update the docs in that repo so that they are at least up to the standard of an F# community project like FSharp.Data.   There are also good quality docs on MSDN and some other good resources, linked here.  Updating the MSDN content would also be great, if only to link across.

Another possible step to consider:

Add multiple platform targets to the Type Provider NuGet for both the Desktop and NetStandard targeting SDKs.  NuGet would then pick the right one based on the target of the type provider being authored.

@dsyme
I think the right place for this API is in the compiler.  The re-mapping is going to be dependent on the set of referenced assemblies, I would prefer the compiler ensured the right thing happened rather than a library SDK.
I am also not sure about the purpose of : typeof in the example.  There should be no circumstance where referencing a type depends on the version of mscorlib that is loaded in process.
I think you may be using the typeof in order to pass into the Api the name of the type, A string is probably the better way of doing that.  In a world containing reference assemblies we shouldn't expect the type providers to load and execute the types they are specifying.  They may want to reify and use real types but we shouldn't require it.  After all the type from a reference assembly has absolutely no behavior.  Also for the coreclr, the set of assemblies will be the minimum set necessary to run the compiler, and the version of any assembly loaded and executed will be the one in the coreclr directory.
The type provider even with load contexts may have no opportunity to specify alternate versions of assemblies already executing.  One final thing when we do AOT compilation, we will probably want to restrict reflectable apis, to the absolute minimum necessary set for the compiler to operate.
I think this location is fine for VS2015, but moving on, I think would prefer if the compiler managed this and the API did not have types as input values.
Kevin

I think the right place for this API is in the compiler. The re-mapping is going to be dependent on the set of referenced assemblies, I would prefer the compiler ensured the right thing happened rather than a library SDK.

I'm sympathetic to this and some this can be seen as a preliminary cut of that for some future compiler addition.  I don't think a full authoring API should be in the compiler DLL, but rather a type/member binding facility.

I am also not sure about the purpose of : typeof in the example. There should be no circumstance where referencing a type depends on the version of mscorlib that is loaded in process.

This problem runs deep with how type providers are have always been authored, and it's considerably worse than typeof: Quotation literals <@ ... @> are like typeof - they produce quotation values which reference System.Type and other System.Reflection objects which are associated with the running mscorlib. Quotations literals are used by pretty much all type providers to describe the code to generate. Let's call these QRunning quotations.  There are QRunning quotations in the example in the README, and in every other type provider sample on the web.
Let's call quotation values created directly (using the quotation API Expr.Call etc. without using quotation literals) and which are independent of the running mscorlib QTarget quotations. The compiler expects to receive QTarget quotations from the type provider.
The primary contribution of this PR is to allow the creation and manipulation of QTarget quotation values and types (see AssemblyReader, AssemblyReaderReflection).
For now, the API for authoring remains largely unchanged: the author uses typeof and QRunning quotations and the AssemblyReplacer remaps QRunning to QTarget behind the scenes (based on searching the set of target referenced assemblies for matching type and method names).
I agree that the use of QRunning quotations to author quotations is wrong. However, it is done for three reasons

Remapping gives a transition story for existing type providers like FSharp.Data which make very, very widespread use of typeof and QRunning quotations
Remapping works well in the cases where you are targeting a PCL/.NETCore subset
Most difficult is that fact that authoring type providers without using typeof and QRunning quotations and remapping is brutally hard (both to write the code and get it right).  It's not impossible and we will need to document how to do it.  But specifying types by string names without even using typeof<Foo>.FullName (the moral equivalent of manual remapping) is a nightmare. Specifying code this way is even worse.

With regard to AOT - if we really want to eliminate the compiler reliance on receiving even QTarget System.Type/System.MethodInfo/quotations values, then we would need to change the ITypeProvider API to avoid transacting these types altogether, and instead use a completely independent representation of types, symbols and code.  There would be some advantages to this (it would reduce the compiler exposure to .NET primitives greatly and clarify exactly which parts of System.Type etc. are relevant - a much smaller subset than the entire System.Type API).  I'll think this over, thanks.

I have 2 items in wish list

Productization of https://github.com/fsprojects/TPCombinators.
Ability to emit generics from type providers.

I'm planning on being at the post F# Exchange (London) hackday on the 16th April. I'll have some distractions, but I was planning to spend some of the time doing some maintenance of this repo and getting a framework for testing and documentation in place.
It would be an excellent time for people to either meet up, or if you can ping me pull requests/specific infrastructure requests in advance I'll try to fit in as much as I can. Unfortunately I don't really have the spare bandwidth at the moment to help out with the actual changes to the APIs required.

As an aside I'm planning to kill the (somewhat unreliable) source NuGet package and recommend paket file references for all TP development. If anyone currently uses the NuGet and has it as a preferred option, please let me know how and why.

I would appreciate understanding what the unreliability of nuget is caused by.  Since they both use the same service for providing the packages.  It would seem that service unreliability was the only real variable in the system, so it would be nice to know why the "nuget client" is unreliable, perhaps it can get fixed, regardless of the choice of dependency management for TypeProvider development within the fsharp. repos.
Thanks
Kevin

@KevinRansom the problem is not in the package, it's in the fact that nuget packages have very limited support for content files and how to handle them. Meanwhile, "github referencing" a file in paket is a first class concept.
There have been several reported issues with the nuget package over time, such as what order it adds content files, having no control over which content files it adds (it's all or nothing) and similar issues.

updates for .net core?

I just tried to compile a Type Provider with .NET Core. Most of the Reflection methods can be polyfilled with packages like System.Reflection.Extensions or System.Reflection.TypeExtensions but the showstopper is the helper types inherit from classes like System.Type which don't have a public constructor in NETStandard. Would there be any hack to overcome this obstacle for the time being?

@alfonsogarciacaro The Type() constructor appears to be protected https://github.com/dotnet/coreclr/blob/master/src/mscorlib/src/System/Type.cs#L56.  At least in the raw code, though perhaps not in the facade assemblies.

I get many errors so only the first one hundred are printed. I cannot see the error concerning System.Type but there're some for other types from System.Reflection like:
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1248,5): error FS0509: Method or object constructor 'ParameterInfo' not found
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1266,5): error FS0509: Method or object constructor 'ParameterInfo' not found
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1354,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1356,17): error FS0856: This override takes a different number of arguments to the corresponding abstract member
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1357,17): error FS0856: This override takes a different number of arguments to the corresponding abstract member
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1358,17): error FS0859: No abstract property was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1360,17): error FS0859: No abstract property was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1361,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1362,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1284,5): error FS0509: Method or object constructor 'ConstructorInfo' not found
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1440,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1454,17): error FS0859: No abstract property was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1459,17): error FS0856: This override takes a different number of arguments to the corresponding abstract member
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1460,17): error FS0859: No abstract property was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1461,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1462,17): error FS0855: No abstract or interface member was found that corresponds to this override
C:\tmp\FSharp.Data.GraphQL.Client\ProvidedTypes.fs(1365,5): error FS0509: Method or object constructor 'MethodInfo' not found

The constructor of ParameterInfo is also protected but still cannot inherit from it.
You can reproduce the issue by cloning the FSharp.Data.GraphQL repo and trying to build the following project.json:
https://github.com/bazingatechnologies/FSharp.Data.GraphQL/blob/dev/src/netcore/FSharp.Data.GraphQL.Client/project.json

Has any of the plans here evolved over the last 7 months?

Another vote for a fleshed-out .NETStandard story (besides just waiting). It's going to be some time before netstandard2.0 is ready for production use--especially for those building client-side products. Ideally, TP's like FSharp.Data.DesignTime would run against netstandard2.0 at build-time but still emit code which targets more mature runtimes like netstandard1.5 or netstandard1.6. This would also enable most of us to use pre-release netstandard2.0 today with only a modest amount of technical risk.

This work has been completed (apart from a few niggling bugs)


405 Error

I followed the README to set the lokka client:
    var Lokka = require('lokka').Lokka;
    var Transport = require('lokka-transport-http').Transport;
    var client = new Lokka({
        transport: new Transport('http://graphql-swapi.parseapp.com/')
    });

    var query = `
{
  allFilms {
    films {
      title
      characterConnection {
        characters {
          name
          starshipConnection{
            starships{
              name
            }
          }
          filmConnection{
            films{
              title
            }
          }
          vehicleConnection{
            vehicles{
              name
            }
          }
        }
      }
    }
  }
} `
    client.query(query).then(
        function(result){
            if(result.data){
                client.cache.setItemPayload(query, vars, result);
                callback(null, result);
             }
             else{
                callback(result);
             }
        },
        function(error){
            callback(error, null);
        }
    )

However, when I tried to run my app, it stills gave me CORS error:
Fetch API cannot load http://graphql-swapi.parseapp.com/. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. The response had HTTP status code 405. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Can any one help me to solve this issue?
Thanks in advance.

Solved by adding a proxy to the server, and send the request from client to the proxy, rather than to graphql server directly.


Function to share holos with a specific e2?

Maybe something like holoShare(N, E) or holoShare(E). Similar to the global holograms (using a negative index allows you to control the holograms from any e2). Would this be possible and/or easy to implement? It would be very useful for cases where you don't want to have to keep respawning a lot of holograms just to edit a few lines of code (yes, global holograms work fine for this UNLESS you want multiple copies of the contraption out at once). Alternatively, would it be possible to enable propcore functions such as setAng and setPos to work on hologram entities?

All of the hologram modification functions would need to modified or duplicated to incorporate shared hologram indices. Not feasible imo.

@thegrb93 Object oriented functions like setPos,setAng,setScale,setModel would work just as well. I had at one point written them but I think I got stuck on setScale for some reason.

how about a sudo feature?
sudo(OtherChip, UserDefinedFunction)
The UserDefinedFunction would run in the context of OtherChip, if it is your own chip.

how about a sudo feature?
sudo(OtherChip, UserDefinedFunction)
The UserDefinedFunction would run in the context of OtherChip, if it is your own chip.
What do you think about this, @thegrb93 @Divran

That'd work, kind of overkill, but useful for many situations, however does e2 behave correctly when moving between e2 contexts? I don't know enough about the internals to make that kind of judgement.
@shadowscion well pr your progress and ppl can help or add suggestions

probably just have to make the E2 context a stack instead of a simple variable

You'd have to make a PR and prove its safety. I'm not ever going to work on e2 internals so that's up to someone else, but I'll add/fix e2 functions.
This request just seems strange to e2 because most things are never shared between them, e.g. sounds, effects, etc, but if @shadowscion makes a PR for this, I'm sure it would be merged.

I am worried about the object oriented approach because you'd have to make sure the hologram object and entity object can never mix, but I think that's most likely not a problem for e2. Is kind of a problem for starfall though.


Can't login

Installed with default parameters on my PC.
OS: Artix
Method: docker-compose
Docker and docker-compose version: Latest
Can't log in. Nothing happens after pressing the login button. Doesn't seem to be doing anything even after entering wrong credentials.

What do your docker-compose logs say?
You can ask them through:
docker-compose logs backend and
docker-compose logs frontend

What do your docker-compose logs say?
You can ask them through:
docker-compose logs backend and
docker-compose logs frontend

docker-compose logs backend: https://paste.ee/p/zCqjR
docker-compose logs frontend: https://paste.ee/p/dUNl7

docker-compose logs backend: https://paste.ee/p/zCqjR
docker-compose logs frontend: https://paste.ee/p/dUNl7

The backend crashes because it says it is a illegal instruction to create the admin user. That's a new one.

The backend crashes because it says it is a illegal instruction to create the admin user. That's a new one.

I can't seem to reproduce the error. It works fine when I start with a fresh database. I am also kind of confused why the migration isn't shown in the backend.

I can't seem to reproduce the error. It works fine when I start with a fresh database. I am also kind of confused why the migration isn't shown in the backend.

Yes it happens every time. I don't know if I am missing anything .... or hardware configuration is a problem... i have 4gb ram and intel dual core processor...its quite old PC though.

Yes it happens every time. I don't know if I am missing anything .... or hardware configuration is a problem... i have 4gb ram and intel dual core processor...its quite old PC though.

Okay, could you maybe start librephotos just with sudo docker-compose up. Without the -d? Maybe then it logs more information. It should not be a resource issue yet.

Okay, could you maybe start librephotos just with sudo docker-compose up. Without the -d? Maybe then it logs more information. It should not be a resource issue yet.

Here: https://paste.ee/p/fOt6W

Here: https://paste.ee/p/fOt6W

It seems like the original docker container never got shut down. Could you run docker-compose down and then docker-compose up and then send me the log?

It seems like the original docker container never got shut down. Could you run docker-compose down and then docker-compose up and then send me the log?

I had this issue as well. FF dev tools said /api/auth/token/obtain was not found (ns bad URI maybe? Should've saved that snippet).
Didn't see much useful in the logs.
I went into the backend container, ran (from /code) /miniconda/bin/python manage.py migrate and received the following:
root@e7d0d435a2bf:/code# /miniconda/bin/python manage.py migrate
Operations to perform:
  Apply all migrations: admin, api, auth, contenttypes, database, sessions
Running migrations:
  No migrations to apply.

Brought the stack down and back up- working. If I have time I'll attempt the same fresh (this is just a demo install for me) and see if it is the same issue. Don't know why it wouldn't be correctly applying the db migrations though.

I had this issue as well. FF dev tools said /api/auth/token/obtain was not found (ns bad URI maybe? Should've saved that snippet).
Didn't see much useful in the logs.
I went into the backend container, ran (from /code) /miniconda/bin/python manage.py migrate and received the following:
root@e7d0d435a2bf:/code# /miniconda/bin/python manage.py migrate
Operations to perform:
  Apply all migrations: admin, api, auth, contenttypes, database, sessions
Running migrations:
  No migrations to apply.

Brought the stack down and back up- working. If I have time I'll attempt the same fresh (this is just a demo install for me) and see if it is the same issue. Don't know why it wouldn't be correctly applying the db migrations though.

I could reproduce this on a fresh install.  Seems like the Python interpreter in the backend container uses SSE 4.1 instructions which fails on some older CPUs (like my good old Phenom 1090T).  Thank you very much, throwaway876, with your comment I was able to dig down.  I got the same illegal instruction, installed gdb inside the backend container and  got:
(gdb) run manage.py migrate
Starting program: /miniconda/bin/python manage.py migrate
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 18153]
[New Thread 0x7f22f9577640 (LWP 18184)]
[New Thread 0x7f22f8d76640 (LWP 18185)]
[New Thread 0x7f22f0575640 (LWP 18186)]
[New Thread 0x7f22dfd74640 (LWP 18187)]
[New Thread 0x7f22df573640 (LWP 18188)]

Thread 1 "python" received signal SIGILL, Illegal instruction.
0x00007f22fc602cf7 in ?? ()
   from /miniconda/lib/python3.8/site-packages/dlib-19.21.99-py3.8-linux-x86_64.egg/_dlib_pybind11.cpython-38-x86_64-linux-gnu.so
(gdb) x/i 0x7f22fc602cf7
=> 0x7f22fc602cf7:	pinsrq $0x1,%rax,%xmm0

pinsrqis a SSE 4.1 instruction, cat /proc/cpuinfo only reports sse4a for my machine.

I could reproduce this on a fresh install.  Seems like the Python interpreter in the backend container uses SSE 4.1 instructions which fails on some older CPUs (like my good old Phenom 1090T).  Thank you very much, throwaway876, with your comment I was able to dig down.  I got the same illegal instruction, installed gdb inside the backend container and  got:
(gdb) run manage.py migrate
Starting program: /miniconda/bin/python manage.py migrate
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 18153]
[New Thread 0x7f22f9577640 (LWP 18184)]
[New Thread 0x7f22f8d76640 (LWP 18185)]
[New Thread 0x7f22f0575640 (LWP 18186)]
[New Thread 0x7f22dfd74640 (LWP 18187)]
[New Thread 0x7f22df573640 (LWP 18188)]

Thread 1 "python" received signal SIGILL, Illegal instruction.
0x00007f22fc602cf7 in ?? ()
   from /miniconda/lib/python3.8/site-packages/dlib-19.21.99-py3.8-linux-x86_64.egg/_dlib_pybind11.cpython-38-x86_64-linux-gnu.so
(gdb) x/i 0x7f22fc602cf7
=> 0x7f22fc602cf7:	pinsrq $0x1,%rax,%xmm0

pinsrqis a SSE 4.1 instruction, cat /proc/cpuinfo only reports sse4a for my machine.

@turnbeutelvergesser I have added a parameter to disable sse4 instructions. The build should be ready in a hour or so. Could you please do a docker-compose down, docker-compose pull and docker-compose up, to try if it works then?

@turnbeutelvergesser I have added a parameter to disable sse4 instructions. The build should be ready in a hour or so. Could you please do a docker-compose down, docker-compose pull and docker-compose up, to try if it works then?

Now it works, I can see a fresh install.  need to have a look around then.
I don't think you'd need to support old CPUs indefinitely, but maybe there could be a better error message.  What I don't know is how much SSE4.1 will buy in Python in this case tough...
Thank you very much!

Now it works, I can see a fresh install.  need to have a look around then.
I don't think you'd need to support old CPUs indefinitely, but maybe there could be a better error message.  What I don't know is how much SSE4.1 will buy in Python in this case tough...
Thank you very much!

@Suleman-Elahi We moved the admin creation to a django command. It should work now for you. Could you test it?

@Suleman-Elahi We moved the admin creation to a django command. It should work now for you. Could you test it?

@derneuere I tried it today on a new PC. This is i5 and has 6 GB ram and it doesn't seem to be working here as well. Tried with default config and admin/admin as login credentials.
Terminal: https://paste.ee/p/NEEiA
Fronted: https://paste.ee/p/g93uE
Backend: https://paste.ee/p/Iqxlr

@derneuere I tried it today on a new PC. This is i5 and has 6 GB ram and it doesn't seem to be working here as well. Tried with default config and admin/admin as login credentials.
Terminal: https://paste.ee/p/NEEiA
Fronted: https://paste.ee/p/g93uE
Backend: https://paste.ee/p/Iqxlr

What OS are you using? How does your docker-compose.yml file look like? How did you configure you .env file?

What OS are you using? How does your docker-compose.yml file look like? How did you configure you .env file?

@derneuere I just started with the default parameters. Didn't change anything in docker-compose or env file.

@derneuere I just started with the default parameters. Didn't change anything in docker-compose or env file.


Password salting

We will need to hash the passwords for storage.
On user login, we can rehash the presented password and query for salted password. If they match, allow login.

Awesome!


Collatz conjecture

ref

@larshp - please review and share feedback.

@Dwivedirahul44 can you please edit your original comment and write "closes #225 " - this  will automatically close the referenced issue when this PR is merged. No need to use hyperlinks, just # + issue number.
Thanks

@Dwivedirahul44 can you please edit your original comment and write "closes #225 " - this will automatically close the referenced issue when this PR is merged. No need to use hyperlinks, just # + issue number. Thanks

thanks a lot, I learned something new.

facing error on fetch configlet


fix(bolt): update opengb -> backend env var name

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1058  👈
#1056
#1054
#1053
#1052
#1051
#1049
#1048
#1047
#1046
#1045
#1044
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite