Fix some things I noticed when reviewing

📝 Summary

Fix broken link to installing section.
Add pipe (|) to table header line, technically invalid without it.
Change "schema" -> "scheme", common mistake.
Fix a few problems in privnet instructions; noteably add a missing word.
Fix a few minor problems in comments.
Remove misleading/contradicting comment about finding best fee.

⛱ Motivation and Context
I can't help but fix small things when I see them.
📚 References
https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Syntax

✅ I have run these commands

[x] make lint
[x] make test
[x] make run-mergemock-integration
[x] go mod tidy

That's great, thanks!

Codecov Report

Merging #191 (a4cb1f4) into main (bce4551) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   72.47%   72.47%
=======================================
  Files           6        6
  Lines         614      614
=======================================
  Hits          445      445
  Misses        144      144
  Partials       25       25

Flag
Coverage Δ

unittests
72.47% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cmd/mev-boost/main.go
4.87% <ø> (ø)

server/relay_entry.go
84.21% <ø> (ø)

server/service.go
82.43% <100.00%> (ø)

Continue to review full report at Codecov.

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


Added helper macro based sig offset update.

Modified the SIGUPD* macros to use a helper macro for offset sanitation.

I don't think this works. SIGALGN should always be max(FLEN,XLEN), and you have simply be XLEN when FLEN is 64 (line 89)

Oops. Copy pasta error. Fixed it.


DO_NOT_MERGE Unsafe xdao

Want to : generate warning when operation on a dao is not using context oriented methods such as put_(...) or inX(x).put(...).
Solution: wrap daos in unsafeXDAO decorator which overrides the non-context-oriented methods by logging a warning and delegating to the next decorator
Problem with soln: doesn't work if user wants the context set via .inX(someX) since it will be interpreted as a non-context oriented operation. Only works when using underscore_ methods, which defeats the purpose since inX is supposed to be used for setting the context anyways.
Soln to problem: Override 'inX' in UnsafeXDAO to so that whenever 'inX' is called, it sets some flag xIsSet, and have the non-context-oriented methods check this flag before logging the warning.
Problem with soln to problem: Should xIsSet be cleared everytime a non-context-oriented method is used?
ex where it shouldn't be cleared -
 dao = dao.inX(x); dao.find(); dao.remove(); // both of these should not produce warnings
ex where it should -
dao.inX(x).find();  dao.remove(); // this should produce warning
Solution to problem with soln to problem: pass this.setXIsSet to the ProxyDAO in the method inX so in the first case, we still have a reference to the dao where x is set, but will still need X to be set in the second line of second case

@googlebot I consent


[tvmc] unify all logs on a single logger 'TVMC'

Publish all tvmc logs under a single "TVMC" logger. This is mainly backporting logger based on code-review comments in the context of #6537. Also using the opportunity to improve some messages.
cc @comaniac @mbaret

CI failed at pytorch/test_lstm, which seens irrelevant
: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-6577/1/pipeline/
@leandron for the time-being, you can push a dummy commit to re-trigger the CI.
@masahi please help take a look at the failure. Thanks.

Thanks. I noticed - it running already 👍🏻

Thanks @leandron


bug: rc0: swipe left problem if prev page was not cached

Type: bug
Platform: mobile webview
you have  on page A and go to the nested page and swipe left to go back to page A:
expected - invoke stateProvider for state A(hit controller etc)
actual - it goes to a blank page since it doesn't use stateProvider and jus trying to return to the previously cached page

Swipe to go back requires that the previous page is cached. We played with it quite a bit, and it was actually a large part of why we added page caching in the first place. Loading a page on swipe to go back adds an unacceptable lag. We're open to PRs that can address this, but currently this is deliberately not supported.

Thanks, that answers the question.
It would be valuable for your guys to document it for the users

I think that "swipe to go back" on should be disabled on pages that are not cached. Blank screens is in no way a good user experience!
Fixed with:
$ionicConfigProvider.views.swipeBackEnabled(false);

Joseph
http://workservis.ru/kontrakt
24.03.2015, 18:05, "Joseph Finlayson" notifications@github.com:I think that "swipe to go back" on should be disabled on pages that are not cached. Blank screens is in no way a good user experience!
Fixed with:
$ionicConfigProvider.views.swipeBackEnabled(false);
—Reply to this email directly or .

It's a big problem

Blank screens is in no way a good user experience!
+1 I think there should be a bulletproof solution.

+1 we need a solution for this

+1

+1
Fixed with:
$ionicConfigProvider.views.swipeBackEnabled(false);

+1

+1

This is s big problem should be supported ASAP

+1

+1
@perrygovier, what whould you say causes the lag ?
My 2 cents : the cause of the lag is one of the following :

template render
controller initialization
angular scope apply

If the cause is not the template render phase, a potential solution maybe the following : the view that is not cached is rendered during the swipe and the controller initialization is called when the animation ends. That way the user sees an empty view, for which the content is loaded when he actually decides to go back to this view.

I solved the problem by using the $ionicView.beforeEnter event. I let the views in the cache, as it is the default, but refresh the view model in controller on the event 'beforeEnter':
$scope.$on('$ionicView.beforeEnter', function() {
MyService.reloadData(...);
});
Seems to work with all the swipe back gestures.

interesting, I'll check this workaround in my project. thanks!

Is it fixed now?

I am facing the same issue, does anyone have any idea?


Lazyvim: Error executing luv callback

Hello, whenever I'm working with Blade files, this error always pops up:
Error executing luv callback:
...ravel.nvim/lua/laravel/repositories/views_repository.lua:37: attempt to index a nil value
stack traceback:
	...ravel.nvim/lua/laravel/repositories/views_repository.lua:37: in function 'f'
	/usr/local/share/nvim/runtime/lua/vim/iter.lua:334: in function 'map'
	...ravel.nvim/lua/laravel/repositories/views_repository.lua:35: in function 'on_exit'
	...cal/share/nvim/lazy/plenary.nvim/lua/plenary/scandir.lua:242: in function <...cal/share/nvim/lazy/plenary.nvim/lua/plenary/scandir.lua:231>

My setup is:

Ubuntu & MacOS (Both show this error)
Lazyvim

Here is my configuration:
return {
  {
    "adalessa/laravel.nvim",
    dependencies = {
      "tpope/vim-dotenv",
      "nvim-telescope/telescope.nvim",
      "MunifTanjim/nui.nvim",
      "kevinhwang91/promise-async",
    },
    cmd = { "Laravel" },
    keys = {
      { "<leader>la", ":Laravel artisan<cr>" },
      { "<leader>lr", ":Laravel routes<cr>" },
      { "<leader>lm", ":Laravel related<cr>" },
    },
    event = { "VeryLazy" },
    opts = {},
    config = true,
  },
}`

@ngunyimacharia I have pushed a change in master https://github.com/adalessa/laravel.nvim/commit/d9d7791676e374717e945411007aed1c0d8c26cc, could you test it ?
This does not happen to me hard to reproduce, for where it happen I assume the scan dir for the views returns a value as null, I have filter it out before processing.

Thank you for the fix. The issue I was having has been resolved. Loving the plugin so far. 💯


P1 is slower then with the official plotter on Apple M1

Phase 1 x 3 threads is very slow and takes near 12000 sec on this plotter and 8000 sec on the official.
Phases 2-3 are a lot faster.
I'm running this plotter and the official on Mac Mini M1 8Gb in parallel and the times (see the logs) are consistent (±5%) for near 10 plots.
Increasing or decreasing the number of threads changes P1 time proportionally and CPU load matches the number of threads. Looks like some part of the code in P1 is very slow on M1.
I tried to compile blake3 with Neon optimization but there was no noticeable difference (but I'm not sure I did it correctly).
Number of Threads: 3
Number of Buckets: 2^8 (256)
Working Directory:   /Volumes/Ssd/
Working Directory 2: /Volumes/Ssd/
[P1] Table 1 took 72.4602 sec
[P1] Table 2 took 2076.52 sec, found<PHONE_NUMBER> matches
[P1] Table 3 took 1913.38 sec, found<PHONE_NUMBER> matches
[P1] Table 4 took 1994.51 sec, found<PHONE_NUMBER> matches
[P1] Table 5 took 1977.62 sec, found<PHONE_NUMBER> matches
[P1] Table 6 took 1927.94 sec, found<PHONE_NUMBER> matches
[P1] Table 7 took 1854.06 sec, found<PHONE_NUMBER> matches
Phase 1 took 11817.1 sec
[P2] max_table_size =<PHONE_NUMBER>
[P2] Table 7 scan took 67.0795 sec
[P2] Table 7 rewrite took 167.657 sec, dropped 0 entries (0 %)
[P2] Table 6 scan took 49.6439 sec
[P2] Table 6 rewrite took 161.086 sec, dropped 581335439 entries (13.537 %)
[P2] Table 5 scan took 48.5578 sec
[P2] Table 5 rewrite took 165.725 sec, dropped 762006235 entries (17.743 %)
[P2] Table 4 scan took 77.3157 sec
[P2] Table 4 rewrite took 172.827 sec, dropped 828937658 entries (19.3005 %)
[P2] Table 3 scan took 63.3097 sec
[P2] Table 3 rewrite took 173.473 sec, dropped 855163362 entries (19.9107 %)
[P2] Table 2 scan took 63.343 sec
[P2] Table 2 rewrite took 173.166 sec, dropped 865626392 entries (20.1544 %)
Phase 2 took 1384.03 sec
Wrote plot header with 268 bytes
[P3-1] Table 2 took 178.291 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 2 took 140.773 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
[P3-1] Table 3 took 204.599 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 3 took 129.617 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
[P3-1] Table 4 took 205.747 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 4 took 133.933 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
[P3-1] Table 5 took 210.537 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 5 took 136.023 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
[P3-1] Table 6 took 245.516 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 6 took 148.065 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
[P3-1] Table 7 took 202.205 sec, wrote<PHONE_NUMBER> right entries
[P3-2] Table 7 took 162.538 sec, wrote<PHONE_NUMBER> left entries,<PHONE_NUMBER> final
Phase 3 took 2098.65 sec, wrote<PHONE_NUMBER>6 entries to final plot
[P4] Starting to write C1 and C3 tables
[P4] Finished writing C1 and C3 tables
[P4] Writing C2 table
[P4] Finished writing C2 table
Phase 4 took 173.8 sec, final plot size is<PHONE_NUMBER>42 bytes
Total plot creation time was 15473.7 sec

Official plotter:
Plot size is: 32
Buffer size is: 2100MiB
Using 128 buckets
Using 3 threads of stripe size 65536

Starting phase 1/4: Forward Propagation into tmp files... Tue Jun 15 11:28:38 2021
Computing table 1
F1 complete, time: 151.115 seconds. CPU (121.940%) Tue Jun 15 11:31:09 2021
Computing table 2
Forward propagation table time: 676.289 seconds. CPU (256.780%) Tue Jun 15 11:42:25 2021
Computing table 3
Forward propagation table time: 1083.887 seconds. CPU (195.780%) Tue Jun 15 12:00:29 2021
Computing table 4
Forward propagation table time: 1559.755 seconds. CPU (161.350%) Tue Jun 15 12:26:29 2021
Computing table 5
Forward propagation table time: 1844.393 seconds. CPU (129.990%) Tue Jun 15 12:57:13 2021
Computing table 6
Forward propagation table time: 1494.853 seconds. CPU (163.980%) Tue Jun 15 13:22:08 2021
Computing table 7
Forward propagation table time: 1238.328 seconds. CPU (175.620%) Tue Jun 15 13:42:47 2021
Time for phase 1 = 8048.673 seconds. CPU (168.760%) Tue Jun 15 13:42:47 2021
Time for phase 2 = 2379.965 seconds. CPU (89.520%) Tue Jun 15 14:22:27 2021
Time for phase 3 = 7283.112 seconds. CPU (88.040%) Tue Jun 15 16:23:50 2021
Time for phase 4 = 496.174 seconds. CPU (75.050%) Tue Jun 15 16:32:06 2021
Total time = 18207.924 seconds. CPU (123.560%) Tue Jun 15 16:32:06 2021

M1 is an 8-core processor, yet you are assigning only 3-threads, which essentially use 2-threads which is same as official plotter + overhead of pipelining.  As Steve Jobs would say, "You're holding it wrong." :)

@fiveangle I'm using it in the best way I could based on experiments with different settings. It has 4 high performance + 4 low performance cores (and low are like 15% of high, they make negligible difference for plotting).
But it's irrelevant here. The point is that with the same settings this plotter is slower than official for P1 on M1, but it's much faster on Intel/AMD.

Fair enough... if there is any condition where the gm plotter is faster than the new mm algo, the mm plotter would ideally sub in gm algo for its built-in algo, but in the end, does it really matter ?  The goal of mm is to maximize performance and assigning just 3x of 8x cores is not the typical use case.  unless you're saying that assigning 4x cores also has the same problem ?
btw, I suspect the reason the 686 results are far better is not that there is a bottleneck on M1, but because it appears the threads parameter is ignored in some way on 686, because cpu usage is > "200%" on the process set to 2 threads on 686.  See 2 jobs (1x mm, 1x gm) started at same time:

Table 1 took 196.312 sec on M1 4 cores MadMax (256 buckets)
Table 1 took 137.027 sec on M1 2 cores standard plotter (128 buckets)
Have you tried mm-plotter with 128 buckets? Will probably use more ram but with the ram integrated in the M1 there could be benefits. I will at least try in my next attempt.

are you guys sure you're taken care of all the necessary requirements ?

Yes
It utilises the cores almost to max:

So with the performance is still suboptimal with 4-8 threads, that is actually real news !
I have a dual-core system kicking around somewhere in storage that I might try a test with gm vs mm to see if in fact the mm plotter is far faster on 686 when the plotter doesn't have >2 cores to potentially grab.


improved emotion template loading

1. Why is this change necessary?
This change simplifies the loading of the emotion components template files
2. What does this change do, exactly?
There was a big if/elseif/else-block where every part loaded the template of a component in the same way, so I removed it and left only the last general part of the block
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @uehler,
thanks for your PR.
With your change even the core template files are checked via "template_exists", which results in unnecessary file checks. This can have a negative performance impact.


it seems mypy on CI doesn't work

see https://github.com/kmyk/online-judge-tools/pull/218

:ok_hand:


GuideLine should be replaced by Annotations

In v2 of G2Plot setting GuideLine does nothing, the config has moved to annotations
E.g. https://g2plot.antv.vision/en/docs/api/plots/column#-line-annotation

@ElderJames this issue has been resolved in PR #102 .

Thank you @MaggiGorengAyam .


Latest lodestar dev build is incompatible due to unexpected SSZ responses

Lodestar recently introduced SSZ serialization for endpoints that do not require SSZ serialization according to spec: PR-6749
This unfortunately breaks compatibility with this library because go-eth2-client uses a generic Accept header that prefers SSZ responses for all endpoints.
In particular it breaks s.Genesis() as the response is always decoded as JSON data, which breaks with SSZ responses.
I'm pretty sure there are more endpoints with the same problem.
I think this should be fixed on go-eth2-client side, so the lib only asks for SSZ encoded data if the underlying implementation is capable of parsing the SSZ response.

Nice catch @pk910, I have not tested the branch against Vouch since I was just using Kurtosis for client interop testing. Definitely agree here that the client should only sent media types in Accept header which it can actually handle.

#145 should address this; please could you take a look to see if you're happy with this and I'll merge it?
Note that I want to add support for SSZ to all of the endpoints, so ultimately should be able to remove the flag but for a quick fix this is the easiest way to proceed.

https://github.com/attestantio/go-eth2-client/pull/145 should address this; please could you take a look to see if you're happy with this and I'll merge it?

LGTM

Looks good 👍

v0.21.6 is now available with #145 .


Ticking Block Entity server start

Description
After playing a bit with the Target block, I ended up restarting the server to update the pack from 1.0.2 to 1.1.0 (Stoneblock 3) and it wont launch until i switch Forge to remove Erroring tile entities.
It doesnt actually remove the block, however the server does launch, but interracting with the computer then crashes the server.
To Reproduce
Computer connected with no startup program (so no program should have been running)
2 target block:

1 connected to a train station
1 connected to 3 tunnels

Software (please complete the following information):

Minecraft Version: 1.18.2
Mod Version 1.3
ModLoader Forge
Server running on Linux (Ubuntu)

ModPack: Stoneblock 3

Crash on startup:
crash-2022-11-07_09.17.38-server.txt

Crash upon clicking the computer
crash-2022-11-07_09.25.52-server.txt

I'll look into it later thx

Hey, I also looked at it now and found the error, I'll publish a patch for it later

Got fixed via commit b97db00c364fdc0a7988fb56ca625a727816de14 and published under v1.3.1


feat(core): plugin postCompile lifecycle

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[x] If this is a new API or substantial change: the PR has an accompanying issue (closes #5616) and the maintainers have approved on my working plan.

Motivation

Adds the ability for plugins to decide when to do additional steps during a dev build, since there is no postStart just postBuild. This enables plugins to do more with dev builds.
Test Plan

I didn't see a strategy for testing plugin life cycle events, this is a TBD before we merge it needs to have a test for sure.
Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

#5616

Hey
After taking a look I find it confusing that this lifecycle would only apply to dev and not prod, because in the end both compile?
Don't you want to create an index also on prod builds?
Also, it looks to me that you can achieve this in userland through webpack plugins, without introducing a new lifecycle
  function myPlugin() {
    return {
      name: 'my-plugin',
      configureWebpack(config) {
        config.plugins?.push({
          apply: (compiler) => {
            compiler.hooks.done.tap('done', async () => {
              console.log('create index');
            });
          },
        });
      },
    };
  },

Isn't that solution good enough?

@slorber ideally it would internally check if an index was created already and choose not to reproduce it based on some conditions like time since last generation or something similar.
Yes this could be implemented as a webpack configuration in the plugin itself, though it does couple that plugin to expecting webpack when that could change in the future. Having a stable API regardless of the internal implementation does lend better to a healthier plugin ecosystem.

Having a stable API regardless of the internal implementation

If we migrate off Webpack we'll have a much much bigger mess to fix than making a new lifecycle.

Totally agree, I think having a webpack hook to utilize makes sense, will try that out. Does it make sense to have a postStart hook? Given the workaround here, that seems to also handle postStart requirements.

I have yet to see a postStart use-case, though. Also, does it run immediately after Ctrl + C, or immediately after the dev server is prepared, or every time after it's reloaded? I do feel like having a lifecycle after and only after the dev server is prepared is worth it, provided a strong non-workaroundable use-case exists.

I think it would be after the dev server is prepared. It would happen once at startup and not get called again when rebuilding occurs.
The use case for me is to build the local search index when the dev server starts, similarly when the production build occurs via postBuild.

Could you open a feature request first? We can investigate if it can be done with configureWebpack().devServer first.

This is the discussion for postStart https://github.com/facebook/docusaurus/discussions/5616 which led me to try and implement postCompile. I can create a feature request and link the discussion.

I created the feature request @Josh-Cena https://github.com/facebook/docusaurus/issues/7749


Include links in the markdown

The result.markdown doesn't include links. I've a use case where I'll be passing the markdown to LLM to identify the product details. Here I want to get the product details url also. But the result.markdown doesn't have links.

@ManojBhamsagar-Draup Hi, thx using Crawl4ai. The marked result contains links. Would you be willing to give me your code? Let me look at the code snippet you have with the URL, and everything. Thank you.

@ManojBhamsagar-Draup Hi, thx using Crawl4ai. The marked result contains links. Would you be willing to give me your code? Let me look at the code snippet you have with the URL, and everything. Thank you.

Yes, here I'm trying to scrape apple careers:
import asyncio
from crawl4ai import AsyncWebCrawler
import base64
async def main():
async with AsyncWebCrawler(verbose=True) as crawler:
result = await crawler.arun(url="https://jobs.apple.com/en-us/search?page=1")
print(f"Basic crawl result: {result.markdown}")
asyncio.run(main())

@ManojBhamsagar-Draup Oh, it's my bad - you're right. Well, you can get all the external and internal links in the result.links and then you can add them to your markdown and pass them to your large language model. However, I'm going to add this extra flag that you can use if you want the links in the metadata or not in the next version, which I'm going to drop within one or two days. The version is 0.3.7 Thanks for reporting this; it's very helpful.

@unclecode sure Thanks ✌

@ManojBhamsagar-Draup That’s right! In the new version, when you set the flag to true, the links will be wrapped within the markdown, exactly like the example we shared 😎

@ManojBhamsagar-Draup That’s right! In the new version, when you set the flag to true, the links will be wrapped within the markdown, exactly like the example we shared 😎

@unclecode that's great

@ManojBhamsagar-Draup We already added more granularity to control how you want to handle internal and external links for images as well as anchor tags. The following code demonstrates a better way of using this feature. I also provided a very lengthy explanation in this issue (https://github.com/unclecode/crawl4ai/issues/184), and I hope it will be helpful.
async def main():
    async with AsyncWebCrawler(headless = True, sleep_on_close = True) as crawler:
        url = "https://janineintheworld.com/places-to-visit-in-central-mexico"
        result = await crawler.arun(
            url=url,
            # bypass_cache=True,
            word_count_threshold = 10,
            excluded_tags = ['form'], # Optional - Default is None, this adds more control over the content extraction for markdown
            exclude_external_links = False, # Default is True
            exclude_social_media_links = True, # Default is True
            exclude_external_images = True, # Default is False
            # social_media_domains = ["facebook.com", "twitter.com", "instagram.com", ...] Here you can add more domains, default supported domains are in config.py

            html2text = {
                "escape_dot": False,
                # Add more options here
            }
        )
        # Save markdown to file
        with open(os.path.join(__data, "mexico_places.md"), "w") as f:
            f.write(result.markdown)

    print("Done")


Bump Kolibri wheel to latest develop

Use the Kolibri wheel file created in Buildkite from latest commit in the develop branch. This includes the patch we were temporarily carrying. So remove the patch.
https://phabricator.endlessm.com/T33895

I will test by running the APK from Jenkins in an emulator before merging.


feat: Update cell strain links.

Resolves #912
Rather than adding additional logic to the InfoLink component that would only be used for cell strains, this adds a specific CellStrainInfoLink.  This PR also moves the InfoLink components to their own files.
Lastly, this PR uses the fractal file structure - it fits here anyway, but it would be great to know if there's broader buy in for using this pattern.  If so, I'll move over the Hygen template from CZID so we won't have to manually set up the folder/file structure for each component we add.

@daniel-ji when are the backend changes going out for this?  The links will be broken for a while if this goes out too early, so maybe we can coordinate.

Maybe a better way to approach this:
in datasetInfoLinks.ts:
NIH_ONTOLOGY_PATTERN = /NCBITaxon:[0-9]+/
OBO_PATTERN = /[a-zA-Z]+:[0-9]+/

in InfoLink.tsx or something like that (no need for a separate component?)
// NOTE: no need to pass in isOBO parameter, we just do the checking in this component
if (id) {
	let link = undefined;
	if !isNaN(id) {
		link = `${NIH}${id}`;
	} else if id.match(NIH_ONTOLOGY_PATTERN) {
		link = `${NIH}${id.replace("NCBITaxon:","");
	} else if id.match(WORMBASE_PATTERN) {
		link = `${WORMBASE}${id.replaceAll(':', '_')}
	} else if id.match(OBO_PATTERN) {
		link = `${OBO}${id.replaceAll(':', '_')}`;
	}
	// don't link otherwise
	...
}

Thoughts?

Also one small thing, but it might be better to refer to everything that's NIH right now to be NCBI? Since NCBI is the specific organization that manages the taxonomy IDs, while NIH is the parent organization and they have various other suborgs that have different IDs / links. So instead of NIH as a constant, maybe NCBI and like NCBI_PATTERN instead of NIH_PATTERN or something like that. Thanks!


[Bug]: The project CODEFORCES_API not opening

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Hello @anuragverma108  @apu52
when we click on the page the page goes 404. IT seems the project lacks .HTML FILE.
Expected behavior
It is always better to something then nothing. Since one can not new create html file(dont know the context).
I recommend to have a completely new project!! RPS GAME--
Computer Opponent: Develop an opponent that can make intelligent choices, providing a challenging gameplay experience for the human player.
Autoplay Mode: Include an autoplay mode where the computer player competes against itself.
Real-time Scoring: Keep track of the scores for both the human player and the computer opponent in real-time. Display the scores prominently on the game interface to provide a sense of competition and progress.
Implementing persistent scoring in a rock-paper-scissors game, ensuring scores are not lost even after page reloads unless and until player resets the score.
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I'm a SSOC'24 contributor
[X] I have starred the repository

@sakshiglaze under which event are you participating?

@heysagnik I am participating in both. But if there is something you can mark only one please mark it under gssoc.

@sakshiglaze assigned you


Fix SSR collisions caused by static style collisions and group ID minimums

Resolve #3561
Resolve #3482
Resolve #3411
Resolve #3321
Resolve #3094
Resolve #3522
Summary
Server-side rendering collisions were increasingly common in seemingly random cases, which was caused by a previous change that allowed new groups to have lower specificity and group IDs than all rehydrated groups. (See #3233)
Additionally, the hash was applied incorrectly (compare to main branch), where static styles would use cssStatic.length rather than cssStatic. This was previously broken due to changes in the hashing function. Overall however, this was causing issues when component IDs collided in hashes already, since cssStatic.length wouldn't do anything to alter the hash provided. We could still use cssStatic.length.toString(16) or an equivalent input, however, I've made this change to align with main for now, since the difference didn't make sense anyway.
Set of changes

Revert #3233 but preserve change in getGroupForId
Fix typo in ComponentStyle relating to phash(x, cssStatic.length)

An initial prerelease version to verify this fix has been released under a tag:

Package
Version

styled-components@pr3563
5.3.1-pr3563

This will automatically enable this PR's patch.


Compilation errors in nexus versions >= 0.11.5

I'm using nexus together with apollo server and noticed that the following schema:
import path from 'path';
import { makeSchema, objectType } from 'nexus';

const Query = objectType({
  name: 'Query',
  definition(t) {
    t.string('_empty', {
      resolve: () => {
        return '';
      },
    });
  },
});

const schema = makeSchema({
  types: [Query],
  outputs: {
    schema: path.join(__dirname, '../schema.graphql'),
    typegen: path.join(__dirname, '../src/generated/typegen.ts'),
  },
});

export { schema };

produces these compilation errors:
node_modules/nexus/dist/builder.d.ts:203:6 - error TS2707: Generic type 'GraphQLObjectType<TSource, TContext>' requires between 0 and 2 type arguments.

203   ): GraphQLObjectType<
         ~~~~~~~~~~~~~~~~~~
204     any,
    ~~~~~~~~
...
208     }
    ~~~~~
209   >;
    ~~~

node_modules/nexus/dist/builder.d.ts:227:6 - error TS2707: Generic type 'GraphQLObjectType<TSource, TContext>' requires between 0 and 2 type arguments.

227   ): GraphQLObjectType<
         ~~~~~~~~~~~~~~~~~~
228     any,
    ~~~~~~~~
...
232     }
    ~~~~~
233   >[];
    ~~~

node_modules/nexus/dist/utils.d.ts:15:9 - error TS2707: Generic type 'GraphQLObjectType<TSource, TContext>' requires between 0 and 2 type arguments.

 15   type: GraphQLObjectType<
            ~~~~~~~~~~~~~~~~~~
 16     any,
    ~~~~~~~~
...
 20     }
    ~~~~~
 21   >,
    ~~~

I've noticed the following:

Running everything in dev mode using ts-node-dev --no-notify --transpileOnly --respawn src/server.tsworks without any issues (Using ts-node version 8.0.1, typescript version 3.2.4)
Compilation works when downgrading to Nexus 0.11.4 while both 0.11.5 and 0.11.6 yield the errors shown above

I'm using Node v10.5.0 and my package dependencies are as follows:
"dependencies": {
    "@okgrow/graphql-scalars": "^0.4.5",
    "apollo-datasource-rest": "^0.3.2",
    "apollo-server": "^2.3.1",
    "apollo-server-express": "^2.3.1",
    "config": "^3.0.1",
    "express": "^4.16.4",
    "graphql": "^14.0.2",
    "graphql-iso-date": "^3.6.1",
    "graphql-tools": "^4.0.4",
    "graphql-type-json": "^0.2.1",
    "jsonwebtoken": "^8.5.0",
    "moment": "^2.24.0",
    "nexus": "0.11.5",
    "uuid": "^3.3.2"
  },
  "devDependencies": {
    "@types/config": "0.0.34",
    "@types/graphql-iso-date": "^3.3.1",
    "@types/graphql-type-json": "^0.1.3",
    "@types/jsonwebtoken": "^8.3.2",
    "@types/uuid": "^3.4.4",
    "@typescript-eslint/eslint-plugin": "^1.2.0",
    "@typescript-eslint/eslint-plugin-tslint": "^1.3.0",
    "@typescript-eslint/parser": "^1.3.0",
    "cross-env": "^5.2.0",
    "eslint": "^5.13.0",
    "eslint-config-airbnb-base": "^13.1.0",
    "eslint-config-prettier": "^4.0.0",
    "eslint-import-resolver-typescript": "^1.1.1",
    "eslint-plugin-import": "^2.16.0",
    "eslint-plugin-prettier": "^3.0.1",
    "nodemon": "^1.18.9",
    "prettier": "1.16.4",
    "rimraf": "^2.6.3",
    "ts-node": "^8.0.1",
    "tslint": "^5.12.1",
    "ts-node-dev": "^1.0.0-pre.30",
    "typescript": "^3.1.6"
  }

Can you check your lockfile npm or yarn to see what version of @types/graphql is being pulled in - I'm guessing it's an older one than the one nexus was built with, as that's the only thing I see that might be causing the issue.
I believe the version you have does not specify GraphQLObjectType args as having a default, and the build .d.ts has:
export declare const isInterfaceField: (
  type: GraphQLObjectType<
    any,
    any,
    {
      [key: string]: any;
    }
  >,
  fieldName: string
) => boolean;

Anyway, adding "@types/graphql": "^14.0.7" to your devDependencies should fix it.

Changing to ^14.0.7 has indeed solved the issue, thank you very much for your swift response!


Current Accumulative Consumption for export

Describe the feature
Like the very helpful recent 'current_accumulative_consumption' being added, a way to see the "current_accumulative_export" for today would be helpful. Currently using the previous which doesn't match up the days with current vs previous together.
Expected behaviour
Add feature for current_accumulative_export for electricity
Use Case
Can see in the energy usage dashboard that it displays the current_accumulative_consumption and current_accumulative_export on the same day.
Confirmation

[X] By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
[ ] I am willing/able to help contribute to the solution of this feature

Hello. I've not been able to confirm if this data is available via the API and I don't have export to confirm. Can you see today's export consumption in the app (not live demand)

Hi, Doesn't appear so,  shows  "Your data's on its way" for Export.  Hopefully they add the feature in the future

You'd have to contact octopus directly


Remove isCustomNetwork

Description
The network controller state isCustomNetwork has been removed. This state was redundant; you can determine whether the current selected network is custom or not by checking the providerConfig state.
The one usage of this state in other packages was the transaction controller. It has been updated to use the provider configuration state instead.
Changes

BREAKING: Remove isCustomNetwork state

To check whether the current selected network is a custom network or not, check the providerConfig.type property. If it's set to NetworkType.rpc then it's a custom network, otherwise it's a built-in network.

References
Closes #1020
Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation for new or updated code as appropriate (note: this will usually be JSDoc)
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

This depends upon #1196


Update existing shared link

If I have shared a link with someone, then continue working on the diagram, I would like to be able to update the drawing that it points to (effective "save" instead of "save as..."). Is this possible with the (awesome!) E2E encryption?

e2e encryption doesn't really change much. The challenge is more about authentication. You must prove that you are the owner of the particular id so you can change it. Because we don't have a notion of ownership right now, we can't really do that.
I'm not sure we want to start adding authentication right now. We now have collaboration mode that partially addresses this. I'll go ahead and close this for now.


Confusing Error: strict mode: unknown keyword: "0" error when not seemingly using any unknown keywords

What version of Ajv are you using? Does the issue happen if you use the latest version?
This happens when I'm using the latest current verison of Ajv (currently v8.12.0)
Ajv options object

{
  "strict": true
}

JSON Schema

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "ABC": {
      "type": "array",
      "items": [
        {
          "type": "string"
        }
      ]
    }
  },
  "type": "array",
  "items": [
    {
      "type": "boolean"
    }
  ],
  "additionalItems": {
    "$ref": "#/definitions/ABC/items"
  }
}

Sample data
No data required because this is a bug in strict mode validating the schema itself.
{}

Your code

RunKit: https://runkit.com/hyperupcall/ajv-issue
(the runkit link is very useful, i was confused for an embarrasingly long time because it used a very old node.js and ajv version which had different results - i'm mentioning this in case this feedback is useful)
const Ajv = require("ajv")
const ajv = new Ajv(options)

const validate = ajv.compile(schema)

const valid = validate(data)
if (!valid) console.log(validate.errors)

Validation result, data AFTER validation, error messages
node index.js
/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/index.js:120
        throw e;
        ^

Error: strict mode: unknown keyword: "0"
    at checkStrictMode (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/util.js:174:15)
    at checkUnknownRules (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/util.js:32:13)
    at checkKeywords (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/validate/index.js:120:34)
    at subschemaCode (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/validate/index.js:89:9)
    at KeywordCxt.subschema (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/validate/index.js:438:9)
    at inlineRefSchema (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/vocabularies/core/ref.js:38:32)
    at Object.code (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/vocabularies/core/ref.js:24:16)
    at keywordCode (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/validate/index.js:464:13)
    at /tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/validate/index.js:185:25
    at CodeGen.code (/tmp/tmp.tu8EDBQWrp/node_modules/ajv/dist/compile/codegen/index.js:439:13)

Node.js v20.4.0

What results did you expect?
It seems that the error is that I'm trying to $ref an array, when it is expecting an object (perhaps items/0). The confusing error seems to go away when I collapse the $ref.
The unknown keyword: "0" is confusing because to me because I don't have a property called 0 anywhere - which means I can't grep where in this schema the error is located. Maybe the error can be made less confusing.
Are you going to resolve the issue?
Unfortunately, I cannot fix this issue myself.

I came across this error too. Couldn't understand it. In the end, my issue was having a $ref within a properties object. Whoopsie!

your additionalItems points to array, schema must be an object.


Wrong description of logical with negate andn instruction

Hi @ptomsich, @aswaterman,
I was going through the bitmanip public review specification and I found that the andn instruction from logical with negate group has the wrong description, the description says that we need to perform bitwise logical and, which should either be bitwise or logical and not bitwise logical and.
Thanks.

For better or worse, “bitwise logical” unambiguously means “bitwise”. This may be a divergence between C language parlance and computer-architecture parlance, but there’s no bug here.

Thanks @aswaterman for clearing the point


instanceof with child elements of iframe documents.

I'm not entirely sure whether this one should be called a suggestion or a bug, due to the interactions it involves and how that might be related to TypeScript's design.  Tested with 2.6.2 and 2.7.1.
Our problem can best be explained by examining the following two blocks of code first:
Code Set 1
var frame = document.getElementById('myFrame') as HTMLIFrameElement
var ele = frame.contentDocument.getElementById('input1') as HTMLInputElement;
// ...
if(ele instanceof HTMLInputElement) {
  console.log('Yep, it\'s an HTMLInputElement.');
} else {
  console.log('HTMLInputElement constructor mismatch!')
}

Expected behavior:
Console log:
> Yep, it's an HTMLInputElement.
Actual behavior:
> HTMLInputElement constructor mismatch!
The short version - any element within an HTMLIFrameElement's internal document is based upon a different constructor set, as the HTMLIFrameElement has its own Window instance (.contentWindow).  In the general case, this is good JavaScript design that helps to isolate documents within an HTMLIFrameElement from the master document.

https://stackoverflow.com/questions/26248599/instanceof-htmlelement-in-iframe-is-not-element-or-object
https://stackoverflow.com/questions/43587286/why-does-instanceof-return-false-on-chrome-safari-and-edge-and-true-on-firefox

Code Set 2
var ele = document.getElementById('input1') as HTMLInputElement
// ...
var proto = window.HTMLInputElement  // Error is on this line.
if(ele instanceof proto) {
  console.log('Yep, it\'s an HTMLInputElement.');
}

Expected behavior:
Console log:
> Yep, it's an HTMLInputElement.
Actual behavior:
source.ts(__, __): error TS2339:  Property 'HTMLInputElement' does not exist on type 'Window'
Never mind the fact that it actually does exist there in JavaScript on all the major browsers; TypeScript doesn't acknowledge that the base window object (or .defaultView/.contentWindow property Window object) contains the original class constructors for its corresponding Document.
Overall desired behavior:
At present, the above two issues combine to make the following impossible in plain TypeScript without losing type information to some degree:
var frame = document.getElementById('myFrame') as HTMLIFrameElement
var ele: HTMLElement = frame.contentDocument.getElementById('input1');

if(ele instanceof ele.ownerDocument.defaultView.HTMLInputElement) {
  console.log("We have an instance of the IFrame's HTMLInputElement class!");
  console.log("It's value: " + ele.value);
}

Even if, within our own codebase, we extend Window via interface to have a property HTMLInputElement: () => HTMLInputElement to model the constructor all Window instances possess, ele.value's line will return an error because it will require a manual cast, unlike with a plain ele instanceof HTMLInputElement... which fails here because HTMLInputElement will correspond to the constructor from the base window: Window.  There's no way to do this at present that feels like 'proper' TypeScript.
The ideal scenario would thus be for the Window class to contain a readonly set of HTMLElement constructors (among others), which should allow for safe use of instanceof upon window.HTMLElement equivalent with that of upon top-level HTMLElement.

Search Terms:
iframe
instanceof
cross-frame
window
constructor

Never mind the fact that it actually does exist there in JavaScript on all the major browsers; TypeScript doesn't acknowledge that the base window object (or .defaultView/.contentWindow property Window object) contains the original class constructors for its corresponding Document.

Global declarations are intentionally elided from Window. you can always add them in your own code base by adding;
interface Window {
    HTMLInputElement : typeof HTMLInputElement ;
}

See https://github.com/Microsoft/TypeScript/issues/19816 for more details.

Thanks.


os: document Chown behavior when uid == -1 or gid == -1

What version of Go are you using (go version)?
https://golang.org/pkg/os/
Does this issue reproduce with the latest release?
Yes, checked tip docs as well: https://tip.golang.org/pkg/os/ (Build version devel +d3026dd30a Thu Apr 5 18:54:31 2018 +0000.)
What did you do?
I read some code like os.Chown(path, -1, gid) and was unsure what uid == -1 meant, so I checked the docs.
What did you expect to see?
Explanation of behavior when uid == -1 (for any of Chown, Lchown, and (*File).Chown).
What did you see instead?
I had to trace through the os code to learn that it calls syscall.Chown, then I had to check man 2 chown to learn:

One of the owner or group id's may be left unchanged by specifying it as -1.

I also consulted http://pubs.opengroup.org/onlinepubs/9699919799/functions/chown.html which states

If owner or group is specified as (uid_t)-1 or (gid_t)-1, respectively, the corresponding ID of the file shall not be changed.

so I believe this behavior should be okay to add to Godoc.

@ianlancetaylor, this is news to me that we do this (by accident?). Are we trying to be POSIX-ish here, or did that just happen?

NeedsFix because we need to document it either way. But we need to decide which way.

That's how POSIX works.  Passing the owner or group as -1 leaves it unchanged.  I note that we don't implement this feature on NaCl.  On Windows and Plan 9 we don't implement Chown at all.  So I think we should implement it in NaCl and document it in the os package.


New container qsmxt 2.0.0

There is a new container, use this command to test:
bash /neurocommand/local/fetch_and_run.sh qsmxt 2.0.0 20230503

and then add to apps.json to release:
https://github.com/NeuroDesk/neurocommand/edit/main/neurodesk/apps.json

@astewartau - can you test and add to app.json if all is good?


Finalize docs for v0.1

Drafts (or WIP notes at least) for all pages.

Rough drafts finalized, with the exception of the Theme page, where I'll need to include links & screenshots for the theme examples created via #43


Use machine/v1alpha1 from openshift/api

Implements OSASINFRA-2981
Follows up on https://github.com/openshift/api/pull/1129

/retest

e2e-openstack failed once because it failed to deploy and twice because of failed tests. I am not sure there's some amount of consistency in the test failures.
/retest

/test e2e-openstack

/retest

/retest

/retest

/retest

@pierreprinetti  Should these files be updated apis.go and register.go?

@pierreprinetti Should these files be updated apis.go and register.go?

The platform provider spec for OpenStack is still defined here in MAPO, so I believe that there should still exist register logic for this group.
Maybe @mdbooth can help us here

@pierreprinetti Should these files be updated apis.go and register.go?

The platform provider spec for OpenStack is still defined here in MAPO, so I believe that there should still exist register logic for this group.
Maybe @mdbooth can help us here

I vaguely recall that we didn't move it to openshift/api because nothing is using it. Try deleting it and see if it breaks anything important. If not, get it gone!

@pierreprinetti Should these files be updated apis.go and register.go?

The platform provider spec for OpenStack is still defined here in MAPO, so I believe that there should still exist register logic for this group.
Maybe @mdbooth can help us here

I vaguely recall that we didn't move it to openshift/api because nothing is using it. Try deleting it and see if it breaks anything important. If not, get it gone!

ok, I removed the whole thing in a separate commit, ready to be reverted if something blows up.

/cc MaysaMacedo

/test e2e-openstack

/test e2e-openstack
No need to retest NFV, as it is currently broken

/test e2e-openstack

/test e2e-openstack

/test e2e-openstack

/test e2e-openstack

/test e2e-openstack
A second try before digging in

/retest-required

/test e2e-openstack

/test e2e-openstack

We're past feature freeze. Does it need to ship in 4.12? If so, please reference a jira in the PR's title (although, it looks like prow is not actually enforcing FF yet?).

Not strictly, no.

/hold
Targeted at 4.13.

/hold cancel
ping @mandre @mdbooth
/meow


Improvement suggestion

Hi, i'm really in love with what you did and the fact that, it doesn't necessarily need to be added to an existing code (Controller) makes it more flexible.
However, i have an issue with the spell termination. If you say "whenDoingThis", this assume the action has already taken place, and some might not understand that "whenDoingThis" is occuring before.
So i would like to suggest renaming "when.." to "before...". This can increase the possibility because it will be possible to do something like "afterDoingThis".
Anyway, good job. I might use it on my upcoming projects.

I am happy to see that a lot of people like the idea right after it is released.
I consider what mentioned for the next major release.
Do not hesitate if you had other ideas as well.

I like this suggestion 👍
Awesome package @imanghafoori1  👏

I appreciate if you help me spreading the word and introduce it to other people.

I'm already on it :smile:

I reopen the issue so others can write their opinion.

HeyMan::beforeReadCommentFrom('github_user', 'adelinferaru')->expect('instance', 'CongratulationsInterface')->otherwise()->expect('instance', 'SuggestionInterface');
Nice job. Keep improving.

@adelinferaru
 HeyMan::thankYou();

I would be happy if you help me spread the word by sharing the link in laravel social groups .
So I can spend more time on coding.


ROX-15447 - On-Prem Reg Scanning P2: Ad-Hoc Delegation

Description
This PR builds on top of #6005 by adding a new ScanImage MsgToSensor to request a secured cluster to scan an image.
MsgToSensor's are async, to match requests to responses a new generic Waiter (and WaiterManager) data structure was created - responsible for  matching async requests/responses (via a UUID + channels).
Identified ad-hoc flows which result in an image scan:

Trigger
Service
gRPC API
REST API

roxctl image scan
ImageService
ScanImage
POST /v1/images/scan

jenkins plugin image scan
ImageService
ScanImage
POST /v1/images/scan

Image watch
ImageService
WatchImage
POST /v1/watchedimages

roxctl deployment check
DetectionService
DetectDeployTimeFromYAML
POST /v1/detect/deploy/yaml

roxctl image check
DetectionService
DetectBuildTime
POST /v1/detect/build

jenkins plugin image check
DetectionService
DetectBuildTime
POST /v1/detect/build

A new Delegable bool was added to Central's EnrichmentContext to determine if an image enrichment request is eligible for 'delegation'. The decision to delegate is contained within a new Delegator, used by the enricher.
Responses to ScanImage MsgToSensor are received via Central's ImageService (central/image/service/service_impl.go) via either EnrichLocalImageInternal or UpdateLocalScanStatusInternal, the latter is used only if a failure occurred before the actual enrichment started.
Checklist

[ ] Investigated and inspected CI test results
[x] Unit test and regression tests added
[x] Evaluated and added CHANGELOG entry if required
[x] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Unit tests, manual tests, log inspection
export BASE=https://$IP/v1/delegatedregistryconfig

## Get Clusters
❯ curl -k -u "$U:$P" "$BASE/clusters"

{"clusters":[{"id":"7ec075ad-28c8-496e-9e0c-3e56082e20a1","name":"local-scan","isValid":true}]}

## Configure Delegation
curl -k -u "$U:$P" "$BASE" -X PUT  --data-raw '{"enabledFor":"SPECIFIC", "defaultClusterId":"7ec075ad-28c8-496e-9e0c-3e56082e20a1", "registries":[{"path":"quay.io/argoproj"},{"path":"docker.io/grafana"},{"path":"docker.io/library/postgres"}]}'

{"enabledFor":"SPECIFIC","defaultClusterId":"7ec075ad-28c8-496e-9e0c-3e56082e20a1","registries":[{"path":"quay.io/argoproj","clusterId":""},{"path":"docker.io/grafana","clusterId":""},{"path":"docker.io/library/postgres","clusterId":""}]}

## Scan via Central
❯ roxctl image scan --image=docker.io/nginx:1.24.0

... successful scan json ....

Scan public images via Sensor:
## Scan via Sensor
❯ roxctl image scan --image=quay.io/argoproj/argocd:v2.7.2

... successful scan json ....

### central logs
Info: Sent scan request "0a517085-65ea-4316-996f-f1f32c092d16" to cluster "7ec075ad-28c8-496e-9e0c-3e56082e20a1" for "quay.io/argoproj/argocd:v2.7.2"
Debug: Scan response received for "0a517085-65ea-4316-996f-f1f32c092d16" and image "quay.io/argoproj/argocd:v2.7.2"

### sensor logs
Debug: Attempting image enrich for "quay.io/argoproj/argocd:v2.7.2" in namespace "" with 1 regs
Debug: Enriching image locally "quay.io/argoproj/argocd:v2.7.2" numRegs 1
Debug: Received image components from local Scanner for image quay.io/argoproj/argocd:v2.7.2
Debug: Retrieved image enrichment results for "quay.io/argoproj/argocd:v2.7.2" with id ""

## Scan via Sensor w/ Digest (twice to trigger cache)
❯ roxctl image scan --image=docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb
❯ roxctl image scan --image=docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb
... successful scan json ....

### central logs
Info: Sent scan request "1a37422f-ad30-4b38-8f1d-5829c3fcf679" to cluster "7ec075ad-28c8-496e-9e0c-3e56082e20a1" for "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb"
Debug: Scan response received for "1a37422f-ad30-4b38-8f1d-5829c3fcf679" and image "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb"

Debug: Delegated enrichment returning cached image for "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb"

### sensor logs
Debug: Attempting image enrich for "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb" in namespace "" with 0 regs
Debug: Enriching image locally "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb" numRegs 0
Debug: Received image components from local Scanner for image docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb
Debug: Retrieved image enrichment results for "docker.io/grafana/grafana@sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb" with id "sha256:2aafd24a138277142a86b6ed43b7537e1ec8226478f5240c459e9330a3461cdb"

Scan private images via sensor
Prep: install artifactory (with anon access allowed) and push nginx image
❯ oc get svc -n artifactory-jcr
NAME                                         TYPE           CLUSTER-IP       EXTERNAL-IP    PORT(S)                      AGE
jfrog-container-registry-artifactory         ClusterIP      <IP_ADDRESS>   <none>         8082/TCP,8081/TCP            178m
jfrog-container-registry-artifactory-nginx   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:32633/TCP,443:30825/TCP   178m

## Attempt scan image in artifactory
❯ roxctl image scan --image=<IP_ADDRESS>/docker/nginx
ERROR:	Scanning image failed: could not scan image: "<IP_ADDRESS>/docker/nginx": rpc error: code = Internal desc = image enrichment error: error getting metadata for image: <IP_ADDRESS>/docker/nginx:latest error: getting metadata from registry: "Autogenerated https://<IP_ADDRESS> for cluster local-scan": Failed to get the manifest digest : Head "https://<IP_ADDRESS>/v2/docker/nginx/manifests/latest": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). Retrying after 3 seconds...

## Set delegation for the Artifactory IP
curl -k -u "$U:$P" "$BASE" -X PUT  --data-raw '{"enabledFor":"SPECIFIC", "defaultClusterId":"7ec075ad-28c8-496e-9e0c-3e56082e20a1", "registries":[{"path":"<IP_ADDRESS>"}]}'

## Retry Scan
❯ roxctl image scan --image=<IP_ADDRESS>/docker/nginx

... successful scan json ....

### Central logs
Info: Sent scan request "f3fdb31d-45f1-4ee9-b11e-6ea7de8fac88" to cluster "7ec075ad-28c8-496e-9e0c-3e56082e20a1" for "<IP_ADDRESS>/docker/nginx:latest"
Debug: Scan response received for "f3fdb31d-45f1-4ee9-b11e-6ea7de8fac88" and image "<IP_ADDRESS>/docker/nginx:latest"

### Sensor logs
Debug: Attempting image enrich for "<IP_ADDRESS>/docker/nginx:latest" in namespace "" with 0 regs
Debug: Enriching image locally "<IP_ADDRESS>/docker/nginx:latest" numRegs 0
Debug: Received image components from local Scanner for image <IP_ADDRESS>/docker/nginx:latest
Debug: Retrieved image enrichment results for "<IP_ADDRESS>/docker/nginx:latest" with id ""

/retest

/retest


W3D5T2 not rendering properly on nbviewer

The nbviewer badge for for T2 lands on 400 : Bad Request and displays a plotly dictionary. Any ideas?

That is weird. I don't use plotly much so I don't know if this is a known issue. It does sound like plotly graphs fail to render in at least some static contexts. I was going to suggest reworking those plots to use matplotlib anyway since we wanted to avoid the overhead of a new library. Would that be alright?

It's also the 1st time I've encountered this problem - renders well on jupyter. github but not on nbviewer.
I totally agree that if we could display interactive 3D plots with matplotlib providing the same user experience as with plotly then we should go for that and avoid the hassle of an additional library. To my knowledge, 3D experience with matplotlib feels clunky but I'm not an expert.
Seeing it from the student's perspective:

fluid and interactive 3D plotting has a wow factor that homes in the message clearly and is sure to bleed into their future projects (just a few lines of code after all)
this is the last day of the course and they see an alternative to matplotlib

What do you think?

We've made a couple of other CCs remove some higher-level libraries to keep things running on the defined environment with minimal extra installs. If you think it's pedagogically important, it can be fine. FWIW I find the allure of interactive plots wears off pretty quickly...  But actually, in trying to gauge how useful the plots are, I ran the instructor version and I'm not sure it's doing the right thing? This is a screenshot of what the second 3D plot (which I gather is meant to show points on the surface of a sphere) looks like for me:

Weird, this is what I get when running the colab version:

Yes, something seems off with the github version.

I see the problem: the latent space coords cannot be cast to integer. This is the proper call:
plot_latent_3d(latent_test, y_test.int())

OK, the same problem is also happening with W2D5T2:
https://nbviewer.jupyter.org/github/NeuromatchAcademy/course-content/blob/master/tutorials/W2D5_ReinforcementLearning/W2D5_Tutorial2.ipynb

Fixed now that notebooks are stored without outputs.


Add trees from Bouckaert et al. 2018 Pama-Nyungan

https://www.nature.com/articles/s41559-018-0489-3#Ack1

Trees added in ec456341633c91061dffd15a810f1abe5d549d34, still waiting for taxon mapping

There are four mapping mismatches between what Bouckaert et al. 2018 say, and what we have listed for Bowern and Atkinson 2012:
Bouckaert et al say dira1238, we have dier1241
Bouckaert et al say mart1256, we have many1256
Bouckaert et al say ngiy1239, we have wang1291
Bouckaert et al say yuwa1242, we have gami1243

@kirbykat -- do you have any ideas about the mapping of the last 4 languages?

(I would assume that the two language datasets contain the same languages, and the B18 mapping was provided by the authors, so we should just be able to update the old B&A13 mapping to match the B18, right?)

@SimonGreenhill I'll check this out asap. What you say probably makes sense. My only concern is that it would lead to a realization that some of our PamaNyungan societies in D-PLACE have been mapped to the wrong glottocodes (relevant to: any more changes coming soon). I will try to look at this tonight.

Great, thanks. I think we'll aim for a new release of v1.2 next week to give people a stable permanent and citable version (i.e. don't work late)

[ ] Bouckaert et al say dira1238, we have dier1241
[ ] Bouckaert et al say mart1256, we have many1256
[ ] Bouckaert et al say ngiy1239, we have wang1291
[ ] Bouckaert et al say yuwa1242, we have gami1243


foundation-apps start server without port

i have successfully installed foundation-apps and its dependencies , id however like to know how to run the server without port ie htttp://localhost and not http://localhost:8080 or http://domain.com and not http://domain.com:8080

I'm afraid the port is required if using our dev environment. It's part of the gulp-connect plugin.

#SOLVED
i solved this in Laravel by using php artisan serve which basically run the php based server and configures server links automatically


Update require for recent versions of node

build/default -> build/Release

I've pushed gir.js to npmjs.org in order to simplify install instructions here https://github.com/antono/vala-object
If You going to push gir.js yorself - feel free to ping me and i'll yank my version and make name free.

you can own the npm name for now.  I'm not working on this at the moment.


Rock The Vote system

Implement RTV system as seen on CS servers for example. Players can initiate RTV with /callvote rtv as an example, which will initiate a vote with 5 maps (could be customizable) to pick from. The maps could be presented in a vsay style menu, where you can use numbers to pick the desired map. The vote lasts for the full 30 seconds (or until everyone has voted), after which the map with most votes will be loaded.
More info/reference to rtv:
https://forums.alliedmods.net/showthread.php?t=57106

Some design ideas:

callvote rtv - initiate rtv

vote yes will open up a vsay-style menu with 5 random maps to choose from, as well as option to keep current map
vote no will count as a "keep current map" vote

at any point (except during vote), players can use /rtv_nominate <mapname> to nominate one map for the next rtv vote, which will be used in place of a randomly picked one

1 nomination per player, to prevent abuse
nominations probably should not carry over to next map, otherwise nomination might be "blocked" for a long time if no rtv is initiated for a while

g_autoRtv <minutes> server setting that initiates rtv automatically after specified amount of time

this should be toggleable via standard vote, so it can be turned off if players want to

if a vote is tied between 2 or more maps after vote has ended (and "keep current map" has less votes), re-roll the vote, with only the tied maps, but no option to keep current, as players have expressed more desire to change the map at that point than keep the current


NETSDK1061 version mismatch error after update

I recently upgraded my Ubuntu packages (I saw some dotnet packages were updated during this), and now when I start VS Code I have a OmniSharp error:
[fail]: OmniSharp.MSBuild.ProjectLoader
        NETSDK1061: The project was restored using Microsoft.NETCore.App version 1.0.5, but with current settings, version 3.0.0 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.

I can still build & run normally, both from IDE and command line.
I have also tried a restore from command line, and it did not seem to fix the issue.
I don't think I was having this issue before updating the system packages.

    Path: /home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/run
    PID: 16818

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 18.4 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 16.4 - "/home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to '/home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin/MSBuild.dll'
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 16.4 - "/home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin"
            CscToolExe = csc.exe
            MSBuildToolsPath = /home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin
            CscToolPath = /home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin/Roslyn
            BypassFrameworkInstallChecks = true
            MSBuildExtensionsPath = /home/sky/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/project/hatch'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in '/project/hatch'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/project/hatch/hatch.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/project/hatch'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /project/hatch/hatch.csproj
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/project/hatch' on host 16060.
[fail]: OmniSharp.MSBuild.ProjectLoader
        NETSDK1061: The project was restored using Microsoft.NETCore.App version 1.0.5, but with current settings, version 3.0.0 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/project/hatch/hatch.csproj'.
/project/hatch/hatch.csproj
/project/hatch/hatch.csproj(0,0): Error: NETSDK1061: The project was restored using Microsoft.NETCore.App version 1.0.5, but with current settings, version 3.0.0 would be used instead. To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish. Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore. For more information, see https://aka.ms/dotnet-runtime-patch-selection.

[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /project/hatch/hatch.csproj

@sky-lake hmm. It sounds like the project.assets.json file may be stale. If you run dotnet restore against your project, does it load properly the next time it is opened?

Hello!
I just tried deleting the whole obj folder of both my exe and library project.  Then I tried executing dotnet restore for both in terminal.  When I load up VS code, I still get the error.  I don't get the error if from terminal I do dotnet build or dotnet publish

@sky-lake It seems you are running into some version of https://github.com/dotnet/sdk/issues/2682
Can you share your project file?

Interesting!  Here is my exe project file:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
   <DefineConstants Condition="'$(SET_PRIVBUILD)'=='true'">$(DefineConstants);PRIVBUILD</DefineConstants>
   <DefineConstants Condition="'$(SET_LOCALGAMETEXTPRIVATE)'=='true'">$(DefineConstants);LOCALGAMETEXTPRIVATE</DefineConstants>
  </PropertyGroup>

  <ItemGroup>
    <Compile Update="**\*.xaml.cs">
      <DependentUpon>%(Filename)</DependentUpon>
    </Compile>
    <AvaloniaResource Include="**\*.xaml">
      <SubType>Designer</SubType>
    </AvaloniaResource>
  </ItemGroup>
  <ItemGroup>
    <PackageReference Include="Avalonia" Version="0.9.0" />
    <PackageReference Include="Avalonia.Desktop" Version="0.9.0" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\core\core.csproj" />
  </ItemGroup>
</Project>

Here is my lib project file (core.csproj):
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <OutputType>Library</OutputType>
    <DefineConstants Condition="'$(SET_PRIVBUILD)'=='true'">$(DefineConstants);PRIVBUILD</DefineConstants>
    <DefineConstants Condition="'$(SET_LOCALGAMETEXTPRIVATE)'=='true'">$(DefineConstants);LOCALGAMETEXTPRIVATE</DefineConstants>
  </PropertyGroup>

   <!-- Embedded method:
  <ItemGroup>
   <Content Remove="GameText.xml" />
   <Content Remove="GameTextPrivate.xml" />
  </ItemGroup>
  <ItemGroup>
   <EmbeddedResource Include="GameText.xml" />
   <EmbeddedResource Include="GameTextPrivate.xml" />
  </ItemGroup>
  -->

  <ItemGroup>
   <Content Include="GameText.xml" />
   <Content Include="GameTextPrivate.xml" />  <!-- TODO: Don't include on public build, if it matters.-->
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" Version="12.0.3" />
  </ItemGroup>

</Project>

This is my first dotnet core project, so please forgive any newbie mistakes 🙏

Had the same issue. Aparently the sdk was working just fine, since a could build my projects via CLI while vscode couldn't resolve my dependencies.
Had to rollback the sdk version e set it in the project's gloabl.json file.
1 - Download past release https://dotnet.microsoft.com/download/dotnet-core/3.1
2 - Move the contents from /dotnet/sdk/3.1.107/ to /usr/share/dotnet/sdk/ (Ubuntu)
3 - Set previous version o global.json file:
{   "sdk": {     "version": "3.1.107"   } }

I think I'm having an issue similar to @michellamin and @sky-lake. I upgraded from 3.1.300 to 3.1.401 and vscode began showing numerous errors in code that don't prevent the CLI from correctly building and testing the project. (The errors are somewhat nonsensical; The type 'Enum' is defined in an assembly that is not referenced.) Looking through the logs, I saw the Microsoft.Build.Exceptions.InvalidProjectFileException: The SDK 'Microsoft.NET.Sdk' specified could not be found error, which is how I wound up here.
Downgrading to 3.1.302 seems to "fix" the omnisharp extension, in that the spurious errors are no longer generated.
Here's the interesting part. The Microsoft.Build.Exceptions.InvalidProjectFileException: error is still emitted in vscode's OmniSharp logs when using 3.1.302.
Perhaps Microsoft has been playing with its package layout, moved the SDK a few version back, and just recently moved the System, System.Void, etc. packages into that misplaced SDK?

@pyrrho Issues with using the latest .NET Core SDK with our included Mono should be resolved in this pre-release - https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.23.0

Can confirm the omnisharp that VS Code pulls via 'latest' appears to have fixed this issue as of yesterday
/home/sky/.vscode/extensions/ms-dotnettools.csharp-1.23.1/.omnisharp/1.37.1-beta.2/run

fixed in 1.23.1


Language setting and icon shape setting don't work

The first makes the app completely crash and the second doesn't change anything if you change it

The icon shape setting causes the application to restart.
Language setting Android T and above are required
Could you please provide your device model and system version if Icon Shpae does not work

The icon shape setting causes the application to restart. Language setting Android T and above are required
Could you please provide your device model and system version if Icon Shpae does not work

I have android 13, Xiaomi 11 Lite 5G NE, 8GB ram, 128GB internal memory

I tested it on Xiaomi devices, miui needs to be adapted, it will be released soon

I tested it on Xiaomi devices, miui needs to be adapted, it will be released soon

Ok, what about the language setting?

I tested it on Xiaomi devices, miui needs to be adapted, it will be released soon

Ok, what about the language setting?

This is a MIUI problem, I can only fix it to keep the app from crashing

The Icon Shape setting has been fixed. You can download the latest Beta to try it out.
https://github.com/hushenghao/AndroidEasterEggs/commit/f91c6e54e2ae0c5f2b21ee23b3faf5be82f71af1


Build is broken at HEAD

From ci.bazel.io (mac and Linux: https://ci.bazel.io/blue/organizations/jenkins/TensorFlow/detail/TensorFlow/1544/pipeline/):
ERROR: /home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD:14:14: Traceback (most recent call last):
	File "/home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD", line 12
		config_setting(name = "using_sycl_ccpp", values =..."})
	File "/home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD", line 14, in config_setting
		{"define": "using_sycl=true", "define": "using_trisycl=false"}
Duplicated key "define" when creating dictionary.
ERROR: /home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD:22:14: Traceback (most recent call last):
	File "/home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD", line 20
		config_setting(name = "using_sycl_trisycl", value..."})
	File "/home/ci/.cache/bazel/_bazel_ci/9630feff78264ece04615e9d6bad98b7/external/local_config_sycl/sycl/BUILD", line 22, in config_setting
		{"define": "using_sycl=true", "define": "using_trisycl=true"}
Duplicated key "define" when creating dictionary.

Repro:
$ bazel build @local_config_sycl//sycl:sycl
..........
ERROR: /usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD:14:14: Traceback (most recent call last):
        File "/usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD", line 12
                config_setting(name = "using_sycl_ccpp", values =..."})
        File "/usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD", line 14, in config_setting
                {"define": "using_sycl=true", "define": "using_trisycl=false"}
Duplicated key "define" when creating dictionary
ERROR: /usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD:22:14: Traceback (most recent call last):
        File "/usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD", line 20
                config_setting(name = "using_sycl_trisycl", value..."})
        File "/usr/local/google/home/dmarting/.cache/bazel/_bazel_dmarting/7d9873875fd56d2bc53371f0098a5332/external/local_config_sycl/sycl/BUILD", line 22, in config_setting
                {"define": "using_sycl=true", "define": "using_trisycl=true"}
Duplicated key "define" when creating dictionary
ERROR: error loading package '@local_config_sycl//sycl': Package 'sycl' contains errors
INFO: Elapsed time: 2.250s
FAILED: Build did NOT complete successfully (1 packages loaded)

After configuring.
Bisecting blame fe197f7dc5bd3b986141bcdaa27928206e74741a
/cc @gunan

+1

Fix is now merged.


From which release it is available

Hi dear Team, from which release can we already move to the new way of connector publishing?
10.0.7 works or later?

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

ID: 27f678d1-840c-d7d3-1e97-ca80666328c2
Version Independent ID: 2a0f90df-f8eb-d9e2-d5be-881734e72e21
Content: Create payment packaging for Application Explorer in Service Fabric deployments - Commerce | Dynamics 365
Content Source: articles/commerce/dev-itpro/payment-connector-package.md
Service: dynamics-365-commerce
Product: ****
Technology: ****
GitHub Login: @mugunthanm
Microsoft Alias: mumani

Thank you for your feedback. @mugunthanm can you please take a look?

This is supported starting from 10.0.10.


0.5.0: pytest is failing in tests/test_render.py::test_sphinx_build_directives unit

I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.

python3 -sBm build -w --no-isolation
because I'm calling build with --no-isolation I'm using during all processes only locally installed modules
install .whl file in </install/prefix> using 'installer` module
run pytest with $PYTHONPATH pointing to sitearch and sitelib inside </install/prefix>
build is performed in env which is cut off from access to the public network (pytest is executed with -m "not network")

Here is pytest output:
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-sphinx-autodoc2-0.5.0-2.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-sphinx-autodoc2-0.5.0-2.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra -m 'not network'
============================= test session starts ==============================
platform linux -- Python 3.8.18, pytest-7.4.3, pluggy-1.3.0
rootdir: /home/tkloczko/rpmbuild/BUILD/sphinx-autodoc2-0.5.0
configfile: pyproject.toml
testpaths: tests
plugins: datadir-1.5.0, regressions-2.5.0
collected 45 items

tests/test_analyse_module.py .....................................       [ 82%]
tests/test_database.py .                                                 [ 84%]
tests/test_render.py ......F                                             [100%]

=================================== FAILURES ===================================
_________________________ test_sphinx_build_directives _________________________

tmp_path = PosixPath('/tmp/pytest-of-tkloczko/pytest-10/test_sphinx_build_directives0')
file_regression = <pytest_regressions.file_regression.FileRegressionFixture object at 0x7fab683055e0>

    def test_sphinx_build_directives(tmp_path: Path, file_regression):
        """Test building the Sphinx docs, using directives."""
        build_package(tmp_path)
        source = tmp_path / "source"
        source.mkdir()
        source.joinpath("conf.py").write_text(
            dedent(
                """\
            project = "tester"
            extensions = ["autodoc2"]
            autodoc2_packages = [
                {
                    "path": "../package",
                    "auto_mode": False,
                }
            ]
            """
            ),
            "utf-8",
        )
        source.joinpath("index.rst").write_text(
            dedent(
                """\
            Test
            ====

            .. autodoc2-docstring:: package.func
               :literal:
               :literal-linenos:
               :literal-lexer: restructuredtext

            .. autodoc2-docstring:: package.func

            .. autodoc2-object:: package.func
               :literal:
               :literal-lexer: restructuredtext

            .. autodoc2-object:: package.func
               :literal:

               render_plugin = "myst"

            .. autodoc2-object:: package.func

            .. autodoc2-summary::

                package.func
                package.a1
            """
            ),
            "utf-8",
        )
        warnings = io.StringIO()
        build = tmp_path / "build"
        app = SphinxTestApp(
            buildername="html",
            srcdir=sphinx_path(source),
            builddir=sphinx_path(build),
            warning=warnings,
        )
        try:
            app.build()
        finally:
            app.cleanup()

        assert not warnings.getvalue()

        doctree = app.env.get_doctree("index")
        doctree["source"] = "index.rst"
        content = "\n".join([line.rstrip() for line in doctree.pformat().splitlines()])
>       file_regression.check(content, extension=".xml")
E       AssertionError: FILES DIFFER:
E       /tmp/pytest-of-tkloczko/pytest-10/test_sphinx_build_directives0/test_render/test_sphinx_build_directives.xml
E       /tmp/pytest-of-tkloczko/pytest-10/test_sphinx_build_directives0/test_render/test_sphinx_build_directives.obtained.xml
E       HTML DIFF: /tmp/pytest-of-tkloczko/pytest-10/test_sphinx_build_directives0/test_render/test_sphinx_build_directives.obtained.diff.html
E       ---
E       +++
E       @@ -1,4 +1,4 @@
E       -<document source="index.rst">
E       +<document source="index.rst" translation_progress="{'total': 0, 'translated': 0}">
E            <section ids="test" names="test">
E                <title>
E                    Test
E       @@ -25,7 +25,7 @@
E                            package.
E                        <desc_name classes="sig-name descname" xml:space="preserve">
E                            func
E       -                <desc_parameterlist xml:space="preserve">
E       +                <desc_parameterlist multi_line_parameter_list="False" xml:space="preserve">
E                            <desc_parameter xml:space="preserve">
E                                <desc_sig_name classes="n">
E                                    a

tests/test_render.py:226: AssertionError
=========================== short test summary info ============================
FAILED tests/test_render.py::test_sphinx_build_directives - AssertionError: F...
========================= 1 failed, 44 passed in 2.27s =========================

List of installed modules in build env:
Package                       Version
----------------------------- -------
alabaster                     0.7.13
astroid                       3.0.1
Babel                         2.13.1
build                         1.0.3
charset-normalizer            3.3.2
cppclean                      0.13
distro                        1.8.0
dnf                           4.18.1
docutils                      0.20.1
exceptiongroup                1.1.3
gpg                           1.23.0
idna                          3.4
imagesize                     1.4.1
importlib-metadata            6.8.0
iniconfig                     2.0.0
installer                     0.7.0
Jinja2                        3.1.2
libdnf                        0.72.0
markdown-it-py                3.0.0
MarkupSafe                    2.1.3
mdit-py-plugins               0.4.0
mdurl                         0.1.2
myst-parser                   2.0.0
packaging                     23.2
pluggy                        1.3.0
Pygments                      2.17.2
pyproject_hooks               1.0.0
pytest                        7.4.3
pytest-datadir                1.5.0
pytest-regressions            2.5.0
python-dateutil               2.8.2
pytz                          2023.3
PyYAML                        6.0.1
requests                      2.31.0
six                           1.16.0
snowballstemmer               2.2.0
Sphinx                        7.1.2
sphinxcontrib-applehelp       1.0.4
sphinxcontrib-devhelp         1.0.5
sphinxcontrib-htmlhelp        2.0.4
sphinxcontrib-jsmath          1.0.1
sphinxcontrib-qthelp          1.0.3
sphinxcontrib-serializinghtml 1.1.9
tomli                         2.0.1
typing_extensions             4.8.0
urllib3                       1.26.18
wheel                         0.42.0
zipp                          3.17.0

Just retested wit latest pytest 8.1.1 and sphinx 7.2.1 and now pytest fails like below

Here is pytest output:
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-sphinx-autodoc2-0.5.0-2.fc36.x86_64/usr/lib64/python3.9/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-sphinx-autodoc2-0.5.0-2.fc36.x86_64/usr/lib/python3.9/site-packages
+ /usr/bin/pytest -ra -m 'not network'
==================================================================================== test session starts ====================================================================================
platform linux -- Python 3.9.18, pytest-8.1.1, pluggy-1.4.0
rootdir: /home/tkloczko/rpmbuild/BUILD/sphinx-autodoc2-0.5.0
configfile: pyproject.toml
testpaths: tests
plugins: mock-3.12.0, hypothesis-6.99.5, datadir-1.5.0, regressions-2.5.0
collected 38 items / 1 error

========================================================================================== ERRORS ===========================================================================================
___________________________________________________________________________ ERROR collecting tests/test_render.py ___________________________________________________________________________
ImportError while importing test module '/home/tkloczko/rpmbuild/BUILD/sphinx-autodoc2-0.5.0/tests/test_render.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.9/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/test_render.py:15: in <module>
    from sphinx.testing.util import path as sphinx_path
E   ImportError: cannot import name 'path' from 'sphinx.testing.util' (/usr/lib/python3.9/site-packages/sphinx/testing/util.py)
================================================================================== short test summary info ==================================================================================
ERROR tests/test_render.py
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
===================================================================================== 1 error in 0.99s ======================================================================================

After add tests/test_render.py to --ignore list rest of the test suite seems is OK.

sphinx = ["sphinx>=4.0.0"]
testing = [
    "pytest",
    "pytest-regressions",
    "pytest-cov",
    "sphinx>=4.0.0,<7",
]

autodoc proper depends on Sphinx >= 4.0.0, but the test dependency has a tighter bound, also being < 7. sphinx.testing.util doesn't export path as of that version, and the module where it itself imported it from no longer supports the way it's being used here.
Ignoring doesn't seem to work in my case, as other tests begin to fail when doing so.

At the moment use anything than >=7 does not make any sense because any older version of the sphinx is no longer maintained.

I agree. This is a dependency for another rpm I need to package, so I'd like to see a real resolution of some sort rather than using an old version. Hoping to have some time toon to work on a patch, but it sure doesn't look fun after reading the test src


Fix MySQL deprecation warnings with Rails 5

When the truncation strategy is used with Rails 5, we see
the deprecation message:
DEPRECATION WARNING: #tables currently returns both tables and
views. This behavior is deprecated and will be changed with Rails 5.1 to
only return tables. Use #data_sources instead.

@etagwerker Would you mind reviewing this? This deprecation warning is polluting our MySQL CI logs like crazy. :)


Did not received XLM because no memo was indicated

Need your help. I did not received my XLM from exodus. Please see details below:
Transaction ID: 5fd8ebfc2d40ad9adc416217f76cd599a890565356de2c6abe02f5b7fe727ec9
Address: GBLJ5ZBZKZXQMXUEABO4FWLR7YWXYOJFLDISAE3TSHT4XVOWLJYBBXCS
Memo: 19732606
Amount sent: 1284.4969 XLM

I have the same issue... Cant figure out a solution..

I have the same issue... Cant figure out a solution..

I have the same issue for two transactions. I XLM twice from my ledger to my coinbase account and forgot the memo. Didn't receive my xlm onto my coinbase. Can you help?

I have the same issue for two transactions. I XLM twice from my ledger to my coinbase account and forgot the memo. Didn't receive my xlm onto my coinbase. Can you help?

I have the same issue for two transactions. I XLM twice from my ledger to my coinbase account and forgot the memo. Didn't receive my xlm onto my coinbase. Can you help?

Same here!I have opened two cases with coinbase,haven’t heard anything back from them.If a memo id is required,why does it let you proceed without it???That makes it optional to me...

I have the same issue for two transactions. I XLM twice from my ledger to my coinbase account and forgot the memo. Didn't receive my xlm onto my coinbase. Can you help?

Same here!I have opened two cases with coinbase,haven’t heard anything back from them.If a memo id is required,why does it let you proceed without it???That makes it optional to me...

I don’t think this is actual support for XLM crypto from this site.Try here for some help https://medium.com/stellar-community/help-i-forgot-my-stellar-memo-d62b3cc9c2f7

I don’t think this is actual support for XLM crypto from this site.Try here for some help https://medium.com/stellar-community/help-i-forgot-my-stellar-memo-d62b3cc9c2f7

I have same problem has anyone sorted out there problem I forgot memo

I have same problem has anyone sorted out there problem I forgot memo

2500 xlm 🤦🏻♂

2500 xlm 🤦🏻♂


Add Osmosis IBC-Hooks Initial port

Description
This PR adds the Osmosis IBC-Hooks module to support routing generic messages from Axelar (GMP) to wasm smart contracts.
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

I am going to merge this to meet our internal timeline, but keep the branch open and resolve a few more issues we have with the code quality (missing tests) and general formatting.  When it fully meets our standards I will issue a second PR to fully close this out.


Add client feature flag to support connect_with_connector in wasm32 targets

This is an updated version of @boxdot's PR #693. The main purpose is to allow compiling tonic for wasm32-unknown-unknown with the connect_with_connector function, so you could use custom connectors in wasm.
Motivation
The main motivation is to allow using something like https://github.com/boxdot/tonic-ws-transport to use tonic in browsers over websockets. grpc-web has a limit on concurrent conections that are open and doesn't allow for client streaming. There is also a related issue for this, #491.
Solution
The connect_with_connector function, as well as the Endpoint and Channel structs, are gated behind the transport feature. Enabling this feature also enables things that are impossible to compile for wasm. This PR introduces a client feature that that enables everything necessary to make connect_with_connector work in wasm and disables anything that fails to compile for wasm.
An alternative to adding a new client feature could also be to gate everything that doesn't compile for wasm behind a #[cfg()] attribute that is disabled for wasm.
I could also add a test that checks whether compilation to wasm works with the client feature, so this won't break in the future.

@lucasmerlin I'm also interested in this. Any chance you can address the conflicts?

Hi, I gave it a shot and got the native version of tonic-ws-transport working natively, but I'm struggling to get tonic to compile for wasm again.
hyper-utils e.g. depends on tower/make which in turn depends on tokio features which aren't available on wasm. So I think there will need to be some patches to other crates to get this working again, which I unfortunately don't have the time for right now.
If someone else wants to give it a try, these are the branches with my rebased changes:
https://github.com/lucasmerlin/tonic/tree/wasm-client-feature-hyper-1.0
https://github.com/lucasmerlin/tonic-ws-transport/tree/hyper-1.0
That said, I'm still using tonic-ws-transport with tonic 0.10.x in my project and it's working really well for me.

IIRC there's some work ongoing in hyper-utils to make some dependencies optional, though tower still seems to be required after https://github.com/hyperium/hyper-util/pull/105. cc @tottoto for visibility.


Fixed minor CSS issue

Hey! I came across this project on a random discord server. As someone who's had to take a long break from open source due to school, I love the idea!
The CSS file had a minor problem, that wouldn't really impact much but was still problematic enough for me, and my css linter to pick up. When using a vendor prefix, you're also supposed to keep the actual property too.

While the intention of this PR was for hacktoberfest, I understand that this contribution may be a tad small, hence why I didn't apply the label. If it is indeed too small, please let me know if there is anything else I can do to help!