Bug: Admonition sometimes appears twice when you edit it later (only in live preview mode, not reading mode)

I have a admonition block, that I returned to a few minutes after creating, and added another sentence. Now the admonition appears twice, once as it originally was, and once with the new addition. This does not show up in reading mode.
And when you click "Edit this block" it's also only a single codeblock.
This does not always happen, so it's difficult to reproduce.

Is it a block quote or code block?

Both. I think the issue occurred when I put a > in the code block.

@ReaderGuy42 Are you still having this issue?

Honestly, I can't even remember this bug. I haven't used admonitions that much since then, but I guess I also haven't found this bug still. Thanks though.


New User-Interface and Design for the showcase page.

The Showcase page is a page that is different from the otherwise nonchalant pages that are present on the website. The page should look a little different as it is a representation of the creativity of the people who have developed amazing stuff using the editor. I can try and make the page look more innovative so that the content and the theme of the page compliment each other.
Would you like to work on the issue?
Yes

This page is updated regularly via GSOC and processing foundation fellowships. If you'd like to submit a proposal to update it, we'd encourage you to do so through one of those two programs, both calls are open right now. Thanks!


Clarification needed in step 1

Hello, I am running through this because this may be interesting content to share GitHub Universe next week in the Actions Hackspace.
My comments below are a direct correlation with this Workspace in mind.,
Is the content complete?
I ask because while evaluating it, I am finding the steps a bit confusing.
I am also presented with multiple branches when I start. I have not seen another lab course start like this.

Confusion
The instructions state I should edit the staging-workflow.yml file, but only the following files are include in the CHANGETHIS folder

ci.yml
approval-workflow.yml
deploy-staging.yml

Changing the deploy-staging.yml works, but multiple files threw me off at the happy path.
Suggestion

I can open a PR to fix the content, but I might suggest also using quicklinks similar to how the hello world action lab works. That experience seemed really nice and I would love to see that same experience here.

I can open a separate PR for that to start the discussion. Curious if there was a reason that method wasn't used.

Thank you @bdougie! You're right - the file is misnamed, and it would definitely be better to have quicklinks to edit the file.
In terms of the extra branches, this is something we battle with Learning Lab. New branches are the only way we can introduce new commits, and we have to choose between opening the PRs all at the beginning, or having the branches show up as you're seeing them.
It would be 💯 to have these things fixed before Universe, since this will also be used in the workshops. If you have the bandwidth to open a PR that would be amazing - but if not, I will see what our team's bandwidth is to work on this. (cc @mattdavis0351 - would this be something you could focus on on Tuesday?)

I have time to dedicate to this later today and tomorrow. Happy to help.

@brianamarie @bdougie I have created a PR #10 that addresses this file change.  It actually needs to be changed in the responses as well as in the config.
@brianamarie @hectorsector if I could get a review on it we can merge and close this issues as well as the associated PR's

Thank you @bdougie! This has been addressed through your work, #10, and #12. 🎉


⚠ Bio Links has degraded performance

In 3316e3d, Bio Links (https://bio.rheinklang.events/links) experienced degraded performance:

HTTP code: 200
Response time: 3267 ms

Resolved: Bio Links performance has improved in e893695 after 46 minutes.


addReaction errors when following the documented pattern.

Your checklist for this issue

[x] Jenkins version 2.255

[x] Plugin version 2.37

[x] OS Linux 4.19.112+

Description
I feel somewhat like this is user error, but for the life of my I cannot see my mistake. When I run the following code:
slackResponse = slackSend(message: jobInfo);
slackResponse.addReaction("jenkins_triggered");

I receive the following exception:
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: jenkins.plugins.slack.workflow.SlackResponse.addReaction() is applicable for argument types: (java.lang.String)
However without the addReaction call it works just fine.

Should it not be
def slackResponse = slackSend(message: jobInfo);
slackResponse.addReaction("jenkins_triggered");

This is another option
def slackResponse = slackSend(message: jobInfo);
slackResponse.addReaction(emojiName: "jenkins_triggered");

thanks, I tried the second option and got another similar error. Here is the beginning of my build script for clarity:
`
node {
def slackResponse = null;
def err = null;
def jobInfo = "${env.JOB_NAME} ${env.BUILD_DISPLAY_NAME} \n${env.BUILD_URL}"
try
{
slackResponse = slackSend(message: jobInfo);
slackResponse.addReaction(emojiName: "jenkins_triggered");
} catch(caughtError) { echo caughtError.toString(); }

// STARTS THE ACTUAL BUILD
`

@aeos Always good to read release notes as I noticed you were using v2.37 according to your checklist.
https://github.com/jenkinsci/slack-plugin/releases/tag/slack-2.39

Thank you, and sorry for wasting your time!


Proovread terminated with error

I run proovread with following command
`perl proove/proovread/bin/proovread -l Lang_flnc.fasta.CDHIT.fasta -s normalized.fastq -o re`

After running for 5 days, it terminated with the following error.
Reading normalized.fastq
    Killed
    [E::sam_parse1] incomplete aux field
    [W::sam_read1] parse error at line 185663450
    [main_samview] truncated file.
    #------------------------------------------------------------------------------#

	Exited at 'main'
	'proove/proovread/bin/proovread', line 1320
	Last call 'main::run_bwa'
	'proove/proovread/bin/proovread', line 853

Any help will be appreciated. Thanks.

Can you send me your complete log file. Seems like something went wrong earlier in the run which then resulted in a truncated bam file.

I am not sure where to locate log file. Please find the log file created after each iteration. Thanks.
proovread_bwa.log
proovread_bwa.log
proovread_bwa.log
proovread_bwa.log
proovread_bwa.log
proovread_bwa.log

Ah, no, those are just the logs from mapping with bwa. I mean everything that proovread logged to the console. But I'm guessing from the confusion that you did not save that to a file?

Sorry I didn't save it. However partial log is attached. Thanks
log.txt

Perfect, thanks. Yes, just look 5 lines up from what you sent initially. It says:
/home/sanjaysingh765/Desktop/analysis/proove/proovread/bin/SeqChunker: line 17: echo: write error: No space left on device
/home/sanjaysingh765/Desktop/analysis/proove/proovread/bin/SeqChunker: line 23: echo: write error: No space left on device

It means you ran out of diskspace, and that's what killed samtools and resulted in the truncated file. If you want to rerun proovread, I'd suggest to split your input data. You seem to have a lot of reads to correct, which is also not ideal for best results. Have a look at this section of the manual https://github.com/BioInf-Wuerzburg/proovread#getting-chunk-sizes-right-48 for more info. Smaller input sets should need less space and you can also delete intermediate files after the end of the run. (And fyi, proovread died in the last iteration, so you were actually almost done, sorry...)

Thanks for your reply. Is there any way to resume my old job?

No, unfortunately not...

Thanks


The email address is no longer valid.

The email address is no longer valid. Could you please update it ?
[Enter feedback here]

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

ID: 88d8d464-42ee-5a50-6330-8e93fa4abf39
Version Independent ID: f372c69b-84b1-8423-c19e-cbbcae563d10
Content: Voice of the Customer is deprecated
Content Source: ce/voice-of-customer/deprecate.md
Service: dynamics-365-customerservice
GitHub Login: @sbmjais
Microsoft Alias: shjais

Thanks for the feedback. We have updated the document.
Closing this issue.


Subsetting tab: Long original variable name problem

The show more/show less button seems to have disappeared from variables in the Kalifabougou Malaria Cohort.
See screenshots below.

Looks good!


make DynamoDatastore default to consistent reads

We're seeing what looks like a race condition on the testnet, where a newly-written record has its canonicalInsert event emitted by the transactor and received by the indexer, but the datastore service is returning "not found" when trying to fetch the referenced canonical.
It seems like this may be related to dynamo's default eventual consistency setting, so this PR changes the default for DynamoDatastore to strongly consistent reads.  You can override by setting the config property io.mediachain.transactor.dynamo.consistentReads to false.
I haven't measured the performance implications of this, so it may be that we want to keep the default and handle the inconsistencies in the clients instead.  This is especially true for IPFS, where there's no "strong consistency switch".  But I want to try deploying this branch on the testnet so I can at least determine whether this is causing the issue in the indexer.

Let me see if I understand Dynamo consistency correctly: it seems that instead of waiting for n of m acknowledgement like with e.g. mongodb, consistency requirements are applied at read time, where you ask n of m (or possibly just m of m) nodes and linearize results afterwards, every single read. This also appears to increase the cost (in $) of the reads by 2x, which sort of makes sense -- I would imagine the latency is increased too, because you have to wait for max_n(...) every time.

yeah, it looks like it does double the read cost... and I'm sure you're right about latency as well.
Maybe it is best to have the client just retry if the key isn't found

Basically, the real (kinda) issue is that Dynamo is not an immutable/append-only store and therefore the consistency semantics are more concerned with concurrent writes than with reliably roundtripping our content-addressed immutable objects. So it's another conceptual flaw in our substitution of Dynamo for IPFS (in a way, the IPFS wait-forever behavior is the perfect complement to this behavior--both make no assumptions about when a given "write" propagates, but IPFS is infinitely optimistic and Dynamo is infinitely pessimistic, with good reason)
I'd say let's just use a manual retry for now -- incurring the consistency cost (both time and $) across all reads, especially when we know that vector clock value is always the same, doesn't really make sense.

cool; I'll close this PR and work on the client end 👍


Windows installation crashes

Describe the issue
QEMULauncher crashes while starting my Windows 10 ARM ISO. It shows me the error message "Assertion failed: (isv), function hvf_vcpu_exec, file hvf.c, line 1232". Probably linked to this file. (If that can help you, I compiled the ISO myself using this exact package). This happen when I choose to boot on DVD after a few seconds.
Probably linked to this issue also : #3197
Configuration

UTM Version: Version 3.2.4 (58)
OS Version: macOS 12.4
Intel or Apple Silicon? Apple Silicon

Crash log
Here.
Debug log
Here
Upload VM
(Useless since this doesn't happen on the Hard Drive of the VM but while booting the ISO)

Pinging @agraf due to HVF-related issue.
Looks like the UTM QEMU HVF backend raises an assertion in int hvf_vcpu_exec(CPUState *cpu):
https://github.com/utmapp/qemu/blob/utm-edition/target/arm/hvf/hvf.c#L1232
Here is the upstream QEMU code.
https://github.com/qemu/qemu/blob/master/target/arm/hvf/hvf.c#L1207-L1233
Notably the upstream code contains a windows_workaround_enabled that is not in our fork (yet).

Great ! Notif me if you need more data.

I have hit this issue as well.
UTM Version: Version 3.2.4 (58)
OS Version: macOS 12.5.1
Intel or Apple Silicon? Apple Silicon (M1 Pro)
Following the instructions on https://mac.getutm.app/gallery/windows-10

I too, ran into this tonight trying to install Windows 10 under UTM 4.1.14. Also fails in precisely the same way with the released version of 4.0.9.

https://docs.getutm.app/guides/windows/
Make sure you’re using a compatible version of windows 10 or windows 11. The guide contains a list of known working versions. Older versions are broken (thanks Microsoft).

The guide [at https://docs.getutm.app/guides/windows/] contains a list of known working versions

That page currently does not contain any list or other information about working versions of Windows.


Alternate, Simplified Async Pull

This PR implements an alternative, simplified approach for sync and async image pulling of images. It leverages the previous, synchronous code and behavior as much as possible.
Effectively, only the actual pull activity is affected. Before v0.7.0, the pull activity was entirely synchronous and a timeout meant the pull was terminated. Now, the same flow is preserved except that after the existing logic is evaluated and a decision to pull is made, a check is done to see if if the pull is already occurring because it was previously tried and timed out.
Many factors complicate the simple timeout-based cancellation that this asynchronous pull feature addresses. Proper modularity allows for more robust and simple tests of individual logic. The changes to existing code are very minimal. The new behavior is implemented in a modular way in new files (a new package). The behavior is more easily tested because more of the system can be mocked.
For another comparison which does not have to back out as many new changes, see https://github.com/warm-metal/container-image-csi-driver/compare/v0.7.0...imuni4fun:container-image-csi-driver:async-pull-simplified-diff?expand=1
That comparison is missing a few minor tweaks but it illustrates the minimalism of the change to existing code.
Created issue #147 per request in community standup. It shares a little more background on this PR.

Note that I still need to update logging to use the chosen logger rather than fmt.Printf() which I had used in my linked example for the pattern. Logging has also changed since the initial integration that I did pre-v0.7.0. Everything other than a few logging lines are ready for evaluation.

logging is now updated to use klog. verbose logging of internals of the AsyncPuller can be enabled by increasing log verbosity, though i was having trouble trying to pass this through go test to get those higher verbosity outputs.

go test -count=1 -v ./pkg/remoteimageasync/...
=== RUN   TestPullDuration
pullerMock: starting to pull image nginx:6
pullerMock: starting to pull image nginx:2
pullerMock: starting to pull image nginx:7
pullerMock: starting to pull image nginx:1
pullerMock: starting to pull image nginx:4
pullerMock: starting to pull image nginx:3
pullerMock: starting to pull image nginx:8
pullerMock: finshed pulling image nginx:1
pullerMock: finshed pulling image nginx:2
pullerMock: finshed pulling image nginx:3
pullerMock: finshed pulling image nginx:4
pullerMock: context cancelled
pullerMock: context cancelled
pullerMock: context cancelled
--- PASS: TestPullDuration (5.00s)
=== RUN   TestParallelPull
pullerMock: starting to pull image nginx:2
pullerMock: finshed pulling image nginx:2
--- PASS: TestParallelPull (3.00s)
=== RUN   TestSerialResumedSessions
pullerMock: starting to pull image nginx:A
pullerMock: finshed pulling image nginx:A
--- PASS: TestSerialResumedSessions (6.00s)
=== RUN   TestParallelResumedSessions
pullerMock: starting to pull image nginx:A
pullerMock: finshed pulling image nginx:A
--- PASS: TestParallelResumedSessions (6.00s)
PASS
ok      github.com/warm-metal/container-image-csi-driver/pkg/remoteimageasync   20.607s

Node plugin pod seems to be crashing due to -
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin I0208 11:19:14.556750       1 provider.go:82] Docker config file not found: couldn't find valid .dockercfg after checking in [  /root /]
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin panic: runtime error: invalid memory address or nil pointer dereference
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x19f7b2c]
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin goroutine 44 [running]:
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin github.com/warm-metal/container-image-csi-driver/pkg/remoteimage.puller.Pull({{0x0, 0x0}, {0x22a1800, 0x400017c8c0}, {0x2299df8, 0x40007317a0}}, {0x22b3d90, 0x4000a25770})
container-image-csi-driver-warm-metal-csi-driver-nodeplugizd67g csi-plugin 	/go/src/container-image-csi-driver/pkg/remoteimage/pull.go:47 +0x13c

Working on fixing this issue.

I don't think this approach is anymore simple than the previous approach. I would argue it is more difficult to understand overall because it has too many indirections. Maybe this is what we need but I wouldn't call it simplified. It has the advantage of not moving/abstracting/changing the existing NodePublishVolume code which is nice.

I don't think this approach is anymore simple than the previous approach. I would argue it is more difficult to understand overall because it has too many indirections. Maybe this is what we need but I wouldn't call it simplified. It has the advantage of not moving/abstracting/changing the existing NodePublishVolume code which is nice.

i do believe that this approach is simpler for the following reasons:

very little changed in node_server.go from pre-async

i reverted the order of calls back to pre-v0.7.0 so it looks like more is changed. refer to comparison link in earlier comment.
this makes no change to the actual pull behavior. it is still performed by remoteasync.Pull() in both async and sync code paths
no new logic is introduced regarding determining whether to pull. this decision is made before looking at whether or not we will pull async or sync
mounting is still synchronous. less states to manage than in v0.7.0

interfaces are cleaner and more testable

a new pullerMock object was used for unit testing and verifying continuation of pulls
mocking allowed clean unit test of new logic without integration with containerd
unit test now exercises relevant async continuation logic

generally cleaner multi-threading implementation

prefer less mutexes, no polling
you almost always want to lock the smallest segment of code possible which doesn't allow for race conditions
channels are preferred over mutexes
sleeping is preferred over polling
this structure best represents the actual problem: pull session is really the fundamentally most pure representation of what is happening that i can think of. then want to reduce edge cases and states as much as possible. drive simplicity of states and data structures. coming from deep history with multi-threading across many domains, the problems that i am familiar with are best solved via this "session" approach.

@mugdha-adhav could you re-trigger the integration tests?

@mugdha-adhav it looks like I cannot request reviews from specific people. I will at them here instead.
@kitt1987 @MaxFedotov @mbtamuli could you take a peek at this PR? thanks!

decided to re-introduce the size extraction and logging since it was present in the reverted files which were removed. added more error handling because there was none and i experienced a panic in my local dev env. added metric export as a bonus since it was very little work and followed same pattern as image pull time (individual).

@mugdha-adhav could you kick integration tests again when you get the chance? thanks!

@imuni4fun currently we are not testing the async mode in our CI tests. Could you please add a test which enables the async feature and then runs integration tests for it?

@mugdha-adhav could you kick integration tests again? thanks

Overall LGTM provided we

address https://github.com/warm-metal/container-image-csi-driver/pull/137#discussion_r1500686922
address https://github.com/warm-metal/container-image-csi-driver/pull/137#discussion_r1500694509
add tests for NodePublishVolume (in node_server_test.go)

summary of discussion with @vadasambar:
I agree that it would be good to build out additional regression tests at higher layers of the onion... in this case at the call to PublishNodeVolume() with mocked containerd being called over GRPC.
I believe this additional testing does not exercise additional code paths beyond one case where there is interplay between caller timeout (kubelet) and actual pull time when pull policy is always. In this case, an image pull that takes too long to pull and exceeds the 2m caller timeout but ALSO completes the pull BEFORE the next call to continue (completes during backoff waiting period) will start a new pull on next call. The image in this scenario will never succeed. Because it would never succeed previously, and just timeout and cancel, I consider this the same behavior.
The above scenario tests the pre-existing pull-always logic in a new context where now many more scenarios CAN succeed. Anything that cannot succeed after the change would also have not succeeded prior.
I am happy to grow the regression tests but don't think adding these new layers should block this feature.

@vadasambar @mugdha-adhav could you review? thx

@mugdha-adhav created meeting to wrap up tomorrow
could you kick off integration tests again? it looks like it might need another run but it’s not clear from my end
last commit was just comments. previous commit had passing integration tests

Also why did we remove the metrics test?

I didn’t remove the test. I removed the “rendered” version which is rendered from https://github.com/imuni4fun/container-image-csi-driver/blob/4c6d7160fa72408225477aad4b061765753095e8/test/integration/metrics-manifests/test.yaml#L1
rendered test changes each time and should be ignored. i added it to .gitignore file in different PR/issue.
:point_up: https://github.com/warm-metal/container-image-csi-driver/pull/148/files#diff-bc37d034bad564583790a46f19d807abfe519c5671395fd494d8cce506c42947

@mugdha-adhav pushed changes called out in review plus from @woehrl01 above. also one small replacement of docker.Named.String() with Puller.ImageWithTag()
ephemeral-volumet-set test passed in local kind cluster


Feature/ted/eng 899/optimization bound type upgrades

This PR has a web_main friend here: https://github.com/FeroLabs/web_main/pull/1453

This PR has a web_main friend here: https://github.com/FeroLabs/web_main/pull/1453

Thanks! Will chat with Todd tomorrow to coordinate a release


Add Youtube workload

Updated workload with AndroidUxPerfWorkload superclass and some adjustments for minor issues found while re-testing.


#522 Correctly pass exceptions when handling servlets

Fixes #522
Motivation

When an exception is thrown inside a servlet handler, the exception is ignored. This causes the application to immediately fall back to default behavior, which typically is returning SC405 (method not supported).

Changes
Will now correctly pass exceptions when handling servlets. If an exception is thrown it is rethrown so Jetty can handle it appropriately (this will pass it into the configured ErrorServlet so you keep control of everything). If no response was given, and no exception was thrown the status code 204 (No content) is returned instead of falling back to 405 (Method not supported)
Type of change

[x] Bug fix

How Has This Been Tested?

[x] Integration testing

Rethrowing exceptions works appropriately for clients, however it would be nice to intercept them before they are sent to the HttpChannel. Preferably at a high level, in org.eclipse.jetty.server.Server#handle - L516.
Also see org.eclipse.jetty.server.HttpChannel#L450 to see how exceptions are currently handled by the channel.


checkup, namespace: Use default K8s client-set

Change the client type to default client-set (kubernetes.Interface) in functions belonging to the checkup.namespace package.
Because we are using K8s fake client as a stub, there is no need to use a client other than the default.
Depends on PR #54.

LGTM, thanks.

Change: Rebase.


Error while loading shared libraries

Hello there,
I am a Ubuntu 18.04 user and was trying out your application but couldn't run the application due to following error
command:::  fmo-desktop --camera 0 --utiademo
Result:-
fmo-desktop: error while loading shared libraries: libopencv_highgui.so.3.1: cannot open shared

Hello, it seems to be related to OpenCV library. Are you sure you have installed it correctly? What version of OpenCV do you have? It's looking for version 3.1.

@rozumden  Thanks for the quick reply...Works like a charm, you guys have done a great job.


fixes #255

note: for some unknown reason ldoc still complains about the function not being found, while generating the correct output

Using the form -- @see Class\method works fine.
Could this get merged ASAP? It’s pretty much critical if anyone is to use LDoc to document Moonscript…

that, combined with @stevedonovan's speed when merging nonconflicting important PRs is why i now made and switched to https://github.com/cuddlyrobot/lunadoc/, which does moonscript right (by using the moonscript parser instead of misinterpreting regexes).

It looks like an interesting project.
I might very well switch to it in the near future if LDoc remains stagnant or if lunadoc becomes more complete and documented. :)
I’m not doing it right away because I spent half of the day tweaking an LDoc template. I don’t want to do that work again unless there are significant benefits. :p

very understandable. lunadoc is pretty young yet, but will be growing with my documentation needs, for example I'm currently working to support more in-depth commenting of tables (which i currently completely ignore, it currently just matches functions and classes and their properties and members), including moonscript files that are just implicitly returning tables (e.g. for a config.moon file documentation etc).

To give an idea of the level of complexity I need in my documentation and for further reference, here’s the current output of a project I’m working on through LDoc:

http://lukc.upyum.com/pkgxx/index.xhtml
http://lukc.upyum.com/pkgxx/classes/Recipe.xhtml

The sources of everything are stored here:

https://github.com/Lukc/pkgxx

Things got messy at some point. O:)

most of the stuff I see there at first glance (except distinction between modules and scripts, and lack of file-based documentation; currently you'd have to move that to the class doc block) would already work, but yeah, if I was you I'd wait, because I'm pretty sure I'll make some api breaking changes in lunadoc at some point soon and you don't want to rewrite everything twice :P

Thanks for taking the time to contribute @nonchip. I'm not exactly sure what I'm testing here. I'm happy to merge a fix to accommodate Moonscript, but I'm having trouble knowing what to check to make sure I'm not breaking plain Lua in the process. What is a use case that I can test this with?

@alerque it's been a while, but iirc this just allows using the form class\method in documentation links when using MoonScript. It might also be that without this moonscript just errors out completely because it generates some such links itself internally, but I don't know anymore.

Thanks. With those comments in mind I've had another look ath this, and I think I've made sense of it. Actually what is confusing me more than anything is not the addition of a backslash \ (escaped because of the string it's in) but why the colon character in that set is escaped as if it was a Lua Pattern magic character! Additionally the second pattern match doesn't make sense because the first one should already cover it.
However whatever those are about, it is that way already so merging this shouldn't hurt.


Bugfix/nested objects b34f0a25ce0c775a29a14241b14e9bc0e47976c8

Nested form wouldn't work anymore.
This was due to the field retrieval methods (getMutableFields, getInsetableFields) using systematically this.state.schema as the current schema. But when you want the fields of a nested schema, you need to pass it explicitely. Same for createField.
value prop of the FormNested was not defined either, instead the whole currentValues object is passed.
However this fix needs a review, I am not sure what was the intent of the previous modifications on the Form component.
I also added a few tests (that does almost nothing), so that we start taking good habits :)
Unit testing is a bit complex and heavy because we need to run Meteor even for pure frontend testing, and Mocha have less features than Jest. But a few regression tests are never a bad thing.
It would also be a good idea to write a few acceptance tests on the Vulcan Starter app with Chimp to detect such issues more easily.

Thanks! btw the reason for the previous modifications was to enable adding "static" (non-mutable) fields to a form. For example the "stripe subscription" field here:

Or you can use the same feature to force a field to always display even when it's not editable. For example maybe you have a "status" field that is only editable by admins but you'd still like to show it (although disabled) to other user groups. So you can do that now.


PT-BR: Fixing wrongly used words at PHP While guide

Changing the use of wrongly translated words to the correct words

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: while is not a function.
Thank you and happy coding.


Accummulating temp files

With a long running daemon scraping pages temporary files are accummulating on /tmp. Other HTTP clients are being used and don't cause issues
braulio@ip-10-98-40-43 tmp]$ ls
httpx20210705-3432-1bqwstk  httpx20210705-3432-1qw4nc6  httpx20210705-3432-2v0bg7  httpx20210705-3432-7sh561  lua_FpCpcb  tmux-0  tmux-500  tmux-512

moved to https://gitlab.com/honeyryderchuck/httpx/-/issues/139


Restore world graph planning capability

I went ahead and did this because I am showing the tool tomorrow and wanted it to work.

Python:
planner_config = {
    "world": world,
    "max_connection_dist": 10.0,
    "compress_path": False,
}
planner = PathPlanner("world_graph", **planner_config)

Yaml:
robots:
  - name: robot
    path_planner:
      type: world_graph
      max_connection_dist: 10.0
      compress_path: false

Closes #104

Thanks !
I will work on a cleaner solution for the graph based planners sometime next week.


[WFCORE-6821] Use a builder to construct the different attributes for the domain mode reload test suite operation

https://issues.redhat.com/browse/WFCORE-6821

Core -> WildFly Preview Integration Build 13633 outcome was FAILURE using a merge of b1c47c62070a7c48181a7aaa078cf46f1703a6ae
Summary: Tests passed: 4982, ignored: 62; exit code 1 (Step: Build & test full (Maven)) (new) Build time: 03:01:22

Thanks @lvydra


fix Typo in #28

#28

@MikeDev101

...Please make sure your have proofread and tested your code before making a PR.


Add Floflis

Please don't change the file permissions of unrelated files, otherwise it's good

You can fix it by reverting commit 5a212e3

I've reverted it for you. The ascii looks good!


Resume playback when headset plugged back in

This is currently the only feature I miss to make this app my Music app.
Shuffle music player does it, Power AMP also, Phonograph does not, nor Jockey.
I really wish it had that feature.
Technical: this should help http://stackoverflow.com/a/13610712 related to https://developer.android.com/reference/android/content/Intent.html#ACTION_HEADSET_PLUG in https://github.com/marverenic/Jockey/blob/master/app/src/main/java/com/marverenic/music/player/PlayerService.java maybe?

To clarify, should playback start every time headphones are plugged in, when AudioFocus is being held by Jockey, or only after headphones are unplugged and reconnected?

I just would like Jockey to resume playback as long as the notification is there, averytime I replug the headset. If the service is dead or the notification got cancelled, I totally understand (and somehow expect) Jockey NOT to resume playback.

I think there should be an option for users to avail this. Otherwise it would be annoying if music starts playing everytime you plug in the headset.

The new Awareness API could surely help:
https://developers.google.com/awareness/android-api/snapshot-get-data#get_headphone_state
Your app can be notified when headphones are plugged/un-plugged:
https://developers.google.com/awareness/android-api/fence-api-overview

Thanks for the link, but I don't think that the Awareness API is a good solution here. I say that because it involves adding Google Play Services as a dependency, and doesn't substantially clean up the implementation details. Because MusicPlayer already has a BroadcastReceiver listening for headphone connection changes, it makes much more sense to just add another branch to its if-else statement to see if headphones were connected, and handle it as described before.


Loading Icon

Implement the LoadingIcon component so that a spinning wheel appears in its place while content is loaded.

done.


Popochiu settings are moved to Project Settings

At the moment, the plugin settings are exposed in the inspector as a set of resource properties, because it was quicker than creating a dedicated interface.

Having those exposed in the Project Settings would be sexier though (and sexier is better than quickier).

It would be nice to have sections: things related to the GI, things related to localization, things that will affect rooms, characters, and so on.


CPLEX/Gurobi performance improvements from comments in #617

Some improvements from comments https://github.com/cvxgrp/cvxpy/issues/617#issuecomment-462909013 and https://github.com/cvxgrp/cvxpy/issues/617#issuecomment-463220105.
It still does't solve completely #617.

Coverage decreased (-0.02%) to 82.792% when pulling 620e77debd6da964183cd3724772182950308487 on bstellato:master into cd0302266e50010cd598ad718e0477f114bbb971 on cvxgrp:master.

Is this good to merge? (I fixed the flake8 issues causing travis to fail.)

Looks good to me. Thanks!


Add crc setup in the error string if crc start fails during preflight

We should tell user to run crc setup as part of error message or separate one in case crc start fails during preflight check.

Resolved by #1877


 I think I did it three times which is why there are so many "commits", i.e. repetitive changes and undo's...
However, I summarized the relevant changes in the commit message


Don't show banner notification in Android push

I send notification with this schema:
$msg = array( 		'title'		=> "This is a title. title", 'sound'		=> "default", 		'body'		=> 'This is a body. body', 		'color' 	        => "#C60800", 		"show_in_foreground" => true, );
$fields = array ( 		"to" 		=> "/topics/topicName", 		'priority' 	=> 'high', 		"notification" => $msg, );
When I send the push, I receive that in my Android, but without banner. Why?

There are any solution?


⚠ Cioos Pacific ERDDAP has degraded performance

In 467a6f0, Cioos Pacific ERDDAP (https://data.cioospacific.ca/erddap/index.html) experienced degraded performance:

HTTP code: 503
Response time: 29539 ms

Resolved: Cioos Pacific ERDDAP performance has improved in 8ea1f86 after 10 minutes.


Review and update ICeWall documentation

@Colin-Holehouse could you help reviewing the Synopsis and Description lists for ICeWall and its Tcl commands so they match and are updated? Some of these questions where raised by @abk-openroad.
On this file for the options:

-core_area and -die_area, please explain semantics of how the list of 4 numbers specifies a region. Also, these options are not given in the Synopsis above the table.
If possible, could you add detail and example for the -offsets argument?

Edit more notes:
On set_bump_options mentions lower left bump. Are origins (lower left vs. upper left) consistent throughout ICeWall commands and mentioned somewhere?  Also, now that the database will allow 45 degree lines, this command will be deprecated once ICeWall has been modified to write RDL into the database directly.
On set_padring_options once a power net is defined, it can be used as the -signal argument for the add_pad command, is this an overload of "signal"?

@vvbandeira
ICeWall got updated. Is this still relevant?


Feature: 这是一个关于图片发太多QQ被腾讯风控的故事

Scope
NovelAI
Describe the problem related to the feature request
因为图片发太多QQ被腾讯风控
Describe the solution you'd like
null
Describe alternatives you've considered
No response
Additional context
No response

This would not gonna happen until you write down a valid solution.
直到你写下一个合法的解决方案之前这不会发生。

This would not gonna happen until you write down a valid solution.
直到你写下一个合法的解决方案之前这不会发生。

6

By the way, "Wind-control" is a complex problem on QQ platform, we could not just change some code and then call it a day. 'Cause the Tencent refused to provide a valid approach to bots on QQ at first.
顺便一提，“风控”在QQ平台上是一个复数的问题，我们不能改一些代码然后称它为一天。因为腾讯公司从一开始拒绝提供一个合法的途径到机器人在QQ上。

这不是一个可以解决的问题。因此将它挪到 discussion 以供讨论。


Backtrick quote highlight error in vscode

Vue - Official extension or vue-tsc version
2.1.6
VSCode version
1.93.1
Vue version
3.5.3
TypeScript version
5.4.4
System Info
No response
package.json dependencies
No response
Steps to reproduce
Error highlight in vscode extension

<template lang="pug">
.row
  template(v-for="(params, field) in data.fields")
    div(
      class="mb-3px"
      :class=`{
        ['col-'+(params.config?.grid?.cols ?? 12)]: true,
        ['row-'+(params.config?.grid?.rows ?? 1)]: params.config?.grid?.rows != 1,
        'field-pinned': openCollapsedPinned[field],
        'h[calc(100%-15px)]': !(openCollapsed[field] === false),
      }`
      style="align-self: baseline;"
    )

<template lang="html">

What is expected?
Correct highlight
What is actually happening?
Not correct highlight
Link to minimal reproduction
No response
Any additional comments?
No response

Using backquote to wrap attribute values is not supported in HTML.

Using backquote to wrap attribute values is not supported in HTML.
In phpstorm supporting

And it works on production good

Because its lang is pug but not html.

Create issue in vscode
https://github.com/microsoft/vscode/issues/229464
I don't know whose bug it is

You can create a minimal reproduction for this and open a new issue.

It might be the problem about textmate.


docs(api): Make API docs less repetitive

We have three main documentation landing pages (or will soon):

https://pypi.org/project/opentrons/
https://github.com/Opentrons/opentrons/blob/edge/api/README.rst and
https://github.com/Opentrons/opentrons/blob/edge/README.md
docs.opentrons.com

Right now, these are all muddled together and often repeat the same content from
different sources. This can lead to issues keeping content in sync, and also
disregards that by convention these locations should have different content
anyway. This PR fixes that. Now,

docs.opentrons.com is the intended landing page for customers who want to
learn how to use the API to run protocols. As subtasks, it also has
instructions on how to simulate protocols locally.
The github readme pages are for people who want to look at the source code.
Because github is no longer how you install the API, it is no longer a place
for users that are new to programming or python. It is instead intended at
people who understand code and want to look at or contribute to it. In case
someone gets there by accident, it has a link to where you should be
looking (docs.opentrons.com) instead. It also has the normal trappings of
development in 2019: badges, inline links to dependencies, etc.
The pypi.org page is for python users who want to confirm that they’re about
to download the right thing, or for people who google some combination of
"opentrons" and "python" and "simulate". Its job is to confirm that people
have found the right thing and pass them on to the actual landing page. It is
bare and does not contain large amounts of documentation, by design; it tells
you only what it’s for on a surface level (simulate stuff) and what it will do
to your computer (make a directory in your home dir) but not how to use the
API, because this is just about the module as a python package.

exactly what the new api readme will look like
more or less what the content of the pypi landing page will look like, ignoring the sidebars
new content for the design with python page but the style will match


Publish to GitHub causes "Repo already exists" error

VS Code Version:

Version: 1.57.0-insider (user setup)
Commit: 37a12c9b0846167b2f68e9e1f276149d2d8b9b27
Date: 2021-05-12T14:14:26.024Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043

OS Version:
Jon$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

Steps to Reproduce:
VS Code / WSL2

Open folder

Click source control

Click "Publish to GitHub" button

I get the prompt

I click publish, remove obj/bin folders

I see this:

It is unclear that I need to do a commit here.

I do a commit

I see this:

I don't know what to do now.
I know the "View" repos option exists, so I click that

I see the repo:

I click publish to GitHub

I choose publish

I get "already exists error

I try to do a push, but get 'no remotes' error

I manually add the remote and can now push.
I believe this can be resolved if we add a remote when we initially click the "publish to github" button.

Does this issue occur when all extensions are disabled?: Yes/No

Okay, thanks.  Will let you know.


{storage-preview} Remove duplicated command az storage blob list

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/Juliehzl/azure-cli-extensions.git@list#subdirectory=src/$EXT&egg=$EXT"


[enhancement] Maps should have an InstanceTable as well

Instance tables provide a great way to check the existing configuration concepts. However, for maps, this has been lacking due to their inherit complexity. @dickscheid and I had discussed this before and had considered an upgrade to the instance tables by making them a data frame that stores extra information such as species. The branch attrDFforMaps introduces such a data frame to maps while instance tables are still used for the core concepts. This branch is made to facilitate the discussion:

Should all the InstanceTables be replaced by such a data frame? (In such a case, the naming InstanceTable will be preserved.)
What else can we improve for the maps InstanceDF?
Should we change the naming of the statistical map files in the configuration? (continuous<->statistical)
Thoughts about a similar table for features?

Code example:
import siibra
print(siibra.maps.head())
print(siibra.maps.columns)
print(siibra.maps.index)
siibra.maps.query("space == 'MNI Colin 27'")

PS: The original code is authored by @dickscheid.

Just occurred to me one thing:

Should all the InstanceTables be replaced by such a data frame? (In such a case, the naming InstanceTable will be preserved.)

I would hate to lose static typing offered by instance table.

Dataframes are very nice in notebooks to plot the instances with some attributes, but in line with Xiao's comment I think we need to clarify a few important functionalities:

can we do static typing with this?
can we do autocompletion on the instance keys a suitable interpreter?

Maybe the solution is to provide a data frame listing optionally, using a dedicated function. Then it could be part of the the atlas concept parent class, and we could keep the instance table.

-If we enable static typing, the default __iter__ has to be replaced. Which then in turn breaks the default representation of dataframes. I am thinking about this currently.

Autocompletion is currently supported

Maybe the solution is to provide a data frame listing optionally, using a dedicated function. Then it could be part of the the atlas concept parent class, and we could keep the instance table.

I think this might work. I will give it a try and update here

why not just add dataframe as a property to all instancetables? this way, we preserve the current behavior, and if the user is more comfortable using a dataframe, they could get one

If we make it a property, registers siibra.maps.dataframe for static typing.
But function works just fine, see https://github.com/FZJ-INM1-BDA/siibra-python/pull/364/commits/6cd227ad727772c66a49c8c590c3399183a33da2
PS: It can be less ugly I think. I am checking how this looks with features and then will work on cleaning up.

If we make it a property, registers siibra.maps.dataframe for static typing.

not too sure what is the issue with using a @property decorator?

I tried but siibra.maps.dataframe raised AttributeError. I'll check again if it was a typo on my side or alike

It was an error on how I initially created dataframe property. A new commit  is pushed now


[Survey] User feedback

VSCode Version: 1.58.0,
Extension Version: 0.8.3,
OS: Windows
1. Overall, how would you rate your experience with the Stream Analytics Visual Studio Code Extension? Please rate us from 1 (poor) to 10 (excellent).
8
2. What do you like or dislike about the Stream Analytics Visual Studio Code Extension?
the project structore for code is not the same as in vs2019. So it is not possible to share projects.
3. What improvements do you suggest for Stream Analytics Visual Studio Code Extension?
I Would like to test iot edge stream analytics projekts.

Hi @bqstony
For #2: even the project structure is slightly different, you can open VS project in VS Code directly and continue to author, test and debug your job in VS Code extension. Please have a try and let us know if you have any problem.
For #3: right now we don't have IoT scenario support in VS code yet, we have recorded your feedback.


Error when trying to use in SPFX 1.17.2

Category
[x] Bug
Version
Please specify what version of the library you are using: latest
Expected / Desired Behavior / Question
Error when trying to implement a control inside a webpart:
sp-pages-assembly_en-us_c3101e7c5d8dbbcc3ca06e3e193641cf.js:70 Could not load quick-access-web-part in require. Error: Script error for: @microsoft/sp-lodash-subset
I just installed the dependency, imported it into my TSX file as shown in the documentation and at the same time the webpart stops working and I get the reported error.

@lhdeveloper
Are you working in the workbench or have you bundled the webpart to display it on a different page? If not on the workbench, try re-bundling and adding the spfx to the appcatalog.

@lhdeveloper
Are you working in the workbench or have you bundled the webpart to display it on a different page? If not on the workbench, try re-bundling and adding the spfx to the appcatalog.

Hello, friend. Yes, I tested it in every way, both on the workbench and on a clean page and also on the home of a communication site. None of the forms occur as expected. I get a script error with something related to the patch.

Hello everybody.
I'm still having this problem.
I'm trying to use the FilePicker component in a webpart, in my TSX file (I don't know if it's possible but I believe so because I'm not using the framework that handles the webpart's controls) and I still keep getting this error:
VM6383:34 GET<EMAIL_ADDRESS>net::ERR_NAME_NOT_RESOLVED
VM6383:34 GET https://relative-path.invalid/ControlStrings.js net::ERR_NAME_NOT_RESOLVED
GET<EMAIL_ADDRESS>net::ERR_NAME_NOT_RESOLVED
Could not load page-collab-profile in require. Error: Script error for: @microsoft/sp-lodash-subset
Does anyone know if it's possible to use the spfx-react-controls components within TSX or just in the TS file that handles the settings panel?
Even after calling the component, I built the application and uploaded it again to the appcatalog, but without success.

Testing my application, I was able to run the webpart on the workbench page.
In a page created within the site (sitepages), the webpart does not load due to the errors reported in the previous comment.

@lhdeveloper Hi there, the controls can definitely work on TSX pages, that's what they are for. We have a separate repository for web part property pane controls.
Could you please confirm that this is the control you are trying to use? https://pnp.github.io/sp-dev-fx-controls-react/controls/FilePicker/
Could you please share the code you are using with your control? (Remove any sensitive information please)
Also, to build the package can you double-check that you are using gulp bundle --ship and gulp package-solution --ship? My main point to validate is the --ship parameter to ensure that the component doesn't try to link back to your localhost.

@joelfmrodrigues
Thanks for your feedback, I managed to get it working even running locally.
A doubt that arose is that when I open FilePicker it has taken a while to load the Recent Documents.
Is this normal or is there something I can do to make it faster?
Here's an image of what the screen looks like.

@lhdeveloper I'm not sure about the time to load recent documents. Can you check on the browser console if you get any API request errors related to that? Is it slow every time, or just sometimes?
Hopefully, someone else can share the experience they found and we can then check if it was an occasional issue or if this is something we need to fix

@joelfmrodrigues
From what I could see, it's always when it opens. I also noticed that when opening the developer tools of chorme he uploaded the recent documents but very slow. The other tabs work normally, the only one has this problem.

Another problem I encountered,
When you click on a tab in FilePicker, a hash is added to the URL.
On a page that I already have parameters added to the URL, it is replacing the hash with the selected tab, which makes no sense to me.
Is there any way to disable adding this parameter to the URL?

@lhdeveloper - this thread is getting difficult - there are multiple different issues.
Could you please create new issues for the problems you're still experiencing.


Could not read whole reply when it's long.

This is a great project that make gpt has ability to have voice.
But I met a question: when the reply of gpt is long (like 200 words), it would not read the final part of reply.
Any guy met similar question?
How to reproduce similar issue:
Ask it question like "how to build a repo on Github", you will get a step-by-step guide, and the voice would keep going to step4 or 5, but could not read to the last word.

Currently listening to the full guide on "how to build a repo on Github" and we're already past step 6 😅


Move inodes from irmin-pack to irmin

This PR extract a part of irmin-pack/inode.ml to irmin/inode.ml:

Bin, Val_impl and Val move to irmin/inode - this is the inode logic and hash computation;
Compress and Elt are kept in irmin-pack/inode.ml - this is the part that compress the inodes for writing it on disk

To create an inode store in irmin, we need an unsafe_content_addressable store that exposes unsafe_find, unsafe_add and unsafe_mem. (I also had to introduce unsafe_append_only  stores to enable irmin-mem to use the inodes. )
Instead of one Make_ext functor we have:

Make_ext_with_nodes - which need a Node.NODE_CONTENT_ADDRESSABLE_STORE instead of Node.S;
Make_ext - which instantiates the default node store and passes it to Make_ext_with_nodes
Make_ext_with_inodes - which instantiates an inode store and passes it to Make_ext_with_nodes

The tests passes for irmin-pack and an irmin-mem store using the inodes.

This is blocked on my refactoring #1340 which is moving a lot of code around.
The possible plan for going forward is to drop "stable hash" completely for inodes (proper plan TBD).

This was discussed at the irmin weekly: we are not sure about the direction as there are a few more design decisions to take (like the removal of stable hashes) @icristescu will open a new PR with irmin-pack.mem instead and we'll see how that'll look.

Superseded by #1436


Fix techinsights docs: replaced DefaultTechInsightsBuilder with buildTechInsightsContext

Hey, I just made a Pull Request!
Just changing README docs for tech-insights as the documented func does not exist.
@Xantier this one might be for you to review?
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Do we want to bump versions with these changes to get the new docs up to npmjs as well?

Will do that now, I see no harm in bumping it.

while using the jsonfc module also noticed that factRefs was renamed to factIds, so I updated that as well on this PR.

@goenning Let's add changesets for these with these PRs. Since a lot of the implementations depend on these docs before tech insights moves further, it's probably good to keep npmjs.com up to date with these.

added patch changeset


124.0.6367.245 the browser doesn't remember that its the default browser

Win 7 64 bit
I updated from version 122 R4. After installation, everything works fine except for the function that sets the browser as the default one for Windows. After restarting your computer, I need to confirm again that Supermium is to be the default browser. The computer remembers this until the next restart.
The error did not occur in the earlier version.

This was fixed in the main release of Supermium 124 in most configurations at least. Is HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet containing a key named "Supermium" or "Supemium"?

Supemium :D ok, I changed it to Supermium.


In try_batch, we should use the latest apply's bucket_meta.

Description
Now in struct Apply, we have bucket_meta field. So we should adjust the try_bacth's code to use the latest bucket_meta (the original code have not handled with it which means we use the first apply's bucket_meta).

Please clarify the issue in the description.

Please clarify the issue in the description.

@SpadeA-Tang

Please clarify the issue in the description.

@SpadeA-Tang

Em.. The words in the description now are appended after the comments. I will list the original code.

/run-cherry-picker


Makefile build options does not generate static binaries

Same here as with atc0005/check-mail#94.

From https://github.com/atc0005/check-mail/issues/94#issuecomment-703084918:

Specifying CGO_ENABLED=0 produced failures:
WARN[0000] github.com/atc0005/mysql2sqlite/internal/dbqs.VerifyDBConn: attempt 1 of 6 to verify database connection failed: Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ git diff Makefile
diff --git a/Makefile b/Makefile
index bcc36ff..8723fae 100644
--- a/Makefile
+++ b/Makefile
@@ -37,7 +37,7 @@ VERSION                               = $(shell git describe --always --long --dirty)

 # The default `go build` process embeds debugging information. Building
 # without that debugging information reduces the binary size by around 28%.
-BUILDCMD                               =       go build -mod=vendor -a -ldflags="-s -w -X $(VERSION_VAR_PKG).Version=$(VERSION)"
+BUILDCMD                               =       go build -mod=vendor -tags 'osusergo,netgo' -a -ldflags "-extldflags '-static' -s -w -X $(VERSION_VAR_PKG).version=$(VERSION)"
 GOCLEANCMD                             =       go clean -mod=vendor ./...
 GITCLEANCMD                            =       git clean -xfd
 CHECKSUMCMD                            =       sha256sum -b

ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ make linux
Building release assets for linux ...
Building mysql2sqlite 386 binaries
Building mysql2sqlite amd64 binaries
# github.com/atc0005/mysql2sqlite/cmd/mysql2sqlite
/tmp/go-link-753298436/000010.o: In function `unixDlOpen':
/home/ubuntu/go-mysql2sqlite/vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:39981: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Generating mysql2sqlite checksum files
Building check_mysql2sqlite 386 binaries
Building check_mysql2sqlite amd64 binaries
# github.com/atc0005/mysql2sqlite/cmd/check_mysql2sqlite
/tmp/go-link-293828066/000010.o: In function `unixDlOpen':
/home/ubuntu/go-mysql2sqlite/vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:39981: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Generating check_mysql2sqlite checksum files
Completed build tasks for linux

ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ file release_assets/mysql2sqlite/mysql2sqlite-7a77dab-dirty-linux-amd64
release_assets/mysql2sqlite/mysql2sqlite-7a77dab-dirty-linux-amd64: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.32, BuildID[sha1]=d00f44845d74d0677794ae875b7920d3f626bb78, stripped

Running the application produces the desired results, at least on the same distro/arch that generated the binary.

This page (https://stackoverflow.com/questions/7526255/unknown-reference-to-dlopen-in-dlopen/7532277) has this to say:

In my system, gcc test.c  -ldl -static is enough to make the application run, but
gcc  -static -ldl -lc
should fix the problem in your system.

So, add -lc then?

That didn't seem to make a difference.
ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ git diff Makefile
diff --git a/Makefile b/Makefile
index bcc36ff..18b4bd2 100644
--- a/Makefile
+++ b/Makefile
@@ -37,7 +37,7 @@ VERSION                               = $(shell git describe --always --long --dirty)

 # The default `go build` process embeds debugging information. Building
 # without that debugging information reduces the binary size by around 28%.
-BUILDCMD                               =       go build -mod=vendor -a -ldflags="-s -w -X $(VERSION_VAR_PKG).Version=$(VERSION)"
+BUILDCMD                               =       go build -mod=vendor -tags 'osusergo,netgo' -a -ldflags "-extldflags '-static -ldl -lc' -s -w -X $(VERSION_VAR_PKG).version=$(VERSION)"
 GOCLEANCMD                             =       go clean -mod=vendor ./...
 GITCLEANCMD                            =       git clean -xfd
 CHECKSUMCMD                            =       sha256sum -b

ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ make clean && make linux
Removing object files and cached files ...
Removing any existing release assets
Building release assets for linux ...
Building mysql2sqlite 386 binaries
Building mysql2sqlite amd64 binaries
# github.com/atc0005/mysql2sqlite/cmd/mysql2sqlite
/tmp/go-link-263648963/000010.o: In function `unixDlOpen':
/home/ubuntu/go-mysql2sqlite/vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:39981: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Generating mysql2sqlite checksum files
Building check_mysql2sqlite 386 binaries
Building check_mysql2sqlite amd64 binaries
# github.com/atc0005/mysql2sqlite/cmd/check_mysql2sqlite
/tmp/go-link-969147616/000010.o: In function `unixDlOpen':
/home/ubuntu/go-mysql2sqlite/vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:39981: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Generating check_mysql2sqlite checksum files
Completed build tasks for linux

Mixed findings when searching further. It is unclear to me whether static binaries are reliable where CGO is concerned.

https://github.com/mattn/go-sqlite3/issues/457
https://sourceware.org/bugzilla/show_bug.cgi?id=10652
https://github.com/golang/go/issues/17935

The more I think about it, the more I think I should hold off with attempts to truly generate static binaries for this project. This may change once I put some effort into #18.
For now, I may try what appears to be a "safe" set of Go  build tags:
-tags 'osusergo netgo'

The Gitea project produces static binaries. Probably a good idea to see how they're pulling off stable builds.
https://github.com/go-gitea/gitea/blob/v1.12.5/Makefile

.PHONY: release-linux
release-linux: | $(DIST_DIRS)
	@hash xgo > /dev/null 2>&1; if [ $$? -ne 0 ]; then \
		GO111MODULE=off $(GO) get -u src.techknowlogick.com/xgo; \
	fi
	CGO_CFLAGS="$(CGO_CFLAGS)" GO111MODULE=off xgo -go $(XGO_VERSION) -dest $(DIST)/binaries -tags 'netgo osusergo $(TAGS)' -ldflags '-linkmode external -extldflags "-static" $(LDFLAGS)' -targets 'linux/amd64,linux/386,linux/arm-5,linux/arm-6,linux/arm64,linux/mips64le,linux/mips,linux/mipsle' -out gitea-$(VERSION) .
ifeq ($(CI),drone)
	cp /build/* $(DIST)/binaries
endif

Looks like they're using a similar collection of flags/settings that I was. Need to try building their codebase to review the output.

Need to try building their codebase to review the output.

https://github.com/techknowlogick/xgo

My solution to the challenge of cross compiling Go code with embedded C/C++ snippets (i.e. CGO_ENABLED=1) is based on the concept of lightweight Linux containers. All the necessary Go tool-chains, C cross compilers and platform headers/libraries have been assembled into a single Docker container, which can then be called as if a single command to compile a Go package to various platforms and architectures.

Ah. Talk about a rabbit hole.

If you take this literally:
/tmp/go-link-383478856/000010.o: In function `unixDlOpen':
/home/ubuntu/go-mysql2sqlite/vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:39981: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

this seems to suggest that if I build on Ubuntu 18.04 and glibc is at 2.23.0, then that version of glibc is needed?
ubuntu@mysql2sqlite-testing:~/go-mysql2sqlite$ dpkg -l | grep -E '^ii\s+libc[0-9]'
ii  libc6:amd64                      2.23-0ubuntu11.2                           amd64        GNU C Library: Shared libraries
ii  libc6-dev:amd64                  2.23-0ubuntu11.2                           amd64        GNU C Library: Development Libraries and Header Files

That exact version, or that version and newer?

Light reading seems to suggest a hard requirement with "strange" behavior if the versions don't line up.
Then, there is the licensing aspect. It sounds like if I distribute compiled binaries with dynamic linkage there is no trouble, but if static builds are provided which pull in glibc code then the LGPL comes into play. This still isn't very clear to me.

https://bugzilla.redhat.com/show_bug.cgi?id=111298#c2

Statically linked programs which are not self-contained and depend
on the installed glibc (be it because of using NSS or iconv (which
both dlopen glibc internally), using dlopen directly or even using
locale support) are really the least portable thing you can build.

and

So, the only supported way of using NSS/iconv/dlopen in statically
linked programs is if they are compiled/linked against the same glibc
as they are run with.

A decent bit of reading later and it appears that I'm left with a few options:

Spend time on #18 to find a SQLite package that does not depend on CGO

this package would need to be promising, well maintained, etc.

Setup multiple LXD containers to provide architecture-specific build environments for musl libc

e.g., 32-bit, 64-bit, and so on

Use xgo + multiple Docker containers (one per build) to perform builds

upside: clean environment per build, easily reproducible
upside: Gitea project uses this approach, so there would be good starter material to work from
downside: complicated vs "go build" or "make all" from a WSLv1 environment

Skip binary builds for this project

skip them going forward
update docs to note caveats (might be needed anyway)
remove binary builds provided with v0.1.0 release (might also be needed anyway)

Giving xgo a try by way of building Gitea from source. Once you crawl down the rabbit hole, you end up at this xgo Dockerfile:

https://github.com/techknowlogick/xgo/blob/master/docker/base/Dockerfile
https://github.com/techknowlogick/xgo/blob/12cf2e8194ca4b45a8375df67992c9535d996453/docker/base/Dockerfile

that is used to generate this Docker image:
ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ docker image ls | grep -E 'SIZE|xgo'
REPOSITORY           TAG                 IMAGE ID            CREATED             SIZE
techknowlogick/xgo   go-1.14.x           be60bf7e5281        3 weeks ago         6.41GB

When running make release-linux, this is the output:
ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ make release-linux
mkdir -p dist/binaries dist/release
CGO_CFLAGS="-g -O2 -DSQLITE_MAX_VARIABLE_NUMBER=32766" GO111MODULE=off xgo -go go-1.14.x -dest dist/binaries -tags 'netgo osusergo ' -ldflags '-linkmode external -extldflags "-static"  -X "main.MakeVersion=GNU Make 4.1" -X "main.Version=1.12.5" -X "main.Tags="' -targets 'linux/amd64,linux/386,linux/arm-5,linux/arm-6,linux/arm64,linux/mips64le,linux/mips,linux/mipsle' -out gitea-master .
Checking docker installation...
Client: Docker Engine - Community
 Version:           19.03.13
 API version:       1.40
 Go version:        go1.13.15
 Git commit:        4484c46d9d
 Built:             Wed Sep 16 17:02:36 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.13
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       4484c46d9d
  Built:            Wed Sep 16 17:01:06 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Checking for required docker image techknowlogick/xgo:go-1.14.x... not found!

Compiling for linux/amd64...
# code.gitea.io/gitea
loadinternal: cannot find runtime/cgo
Compiling for linux/386...
# code.gitea.io/gitea
loadinternal: cannot find runtime/cgo
Bootstrapping linux/arm-5...
Compiling for linux/arm-5...

it continues from there, that's as far as it has gotten as of this writing.

Results of the build:
ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ tree dist/
dist/
├── binaries
│   ├── gitea-master-linux-386
│   ├── gitea-master-linux-amd64
│   ├── gitea-master-linux-arm-5
│   ├── gitea-master-linux-arm-6
│   ├── gitea-master-linux-arm64
│   ├── gitea-master-linux-mips
│   ├── gitea-master-linux-mips64le
│   └── gitea-master-linux-mipsle
└── release

2 directories, 8 files
ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ file dist/binaries/*
dist/binaries/gitea-master-linux-386:      ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=2107c37e63227068000209cfa7a6fed8de39c357, not stripped
dist/binaries/gitea-master-linux-amd64:    ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=2e7789d9ed84e5c961dfdddd37c8a880cd89ffff, not stripped
dist/binaries/gitea-master-linux-arm-5:    ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=08514b5051fa57f9e617c5a3af87734c638780fb, not stripped
dist/binaries/gitea-master-linux-arm-6:    ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=b220cd11cbfcbe2338de3d175d0badb86dfce1ee, not stripped
dist/binaries/gitea-master-linux-arm64:    ELF 64-bit LSB executable, ARM aarch64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.7.0, BuildID[sha1]=4b5a87688c2e4bf802fd83f489acf2be72dbe8cb, not stripped
dist/binaries/gitea-master-linux-mips:     ELF 32-bit MSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=386cdbd0c818ec22a9f25a2afc59cb49923678d1, not stripped
dist/binaries/gitea-master-linux-mips64le: ELF 64-bit LSB executable, MIPS, MIPS64 rel2 version 1 (SYSV), statically linked, BuildID[sha1]=6a16d7cd4610f4add7c31ce768097c238255909a, for GNU/Linux 3.2.0, not stripped
dist/binaries/gitea-master-linux-mipsle:   ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=d1b5ec4af35163b9c7e8596971902eeb10c4af9c, not stripped

So, xgo doesn't use a container per architecture, (afaict), it uses one large container with lots of cross-compiling tools within to handle the various architectures.
The end result is static binaries based off of glibc. That still leaves the licensing question in the air: what is the final license for static binaries generated from Go code + glibc?

https://blog.filippo.io/easy-windows-and-linux-cross-compilers-for-macos/

Maybe most importantly, it's based on the musl C standard library. This means that the binaries will only run on a musl-based system, like Alpine. However, if you build them as static binaries by passing -static as a LDFLAG they will run anywhere, including in scratch Docker containers. musl is specifically engineered to support fully static binaries, which is not recommended with glibc.

https://github.com/zeromq/libzmq/issues/2849#issuecomment-347144252

You cannot statically link to glibc - it uses runtime plugins for things like DNS resolution.
Also it's licensed under the LGPL, which means you can do dynamic linking, but static linking means your program's source code also has to be released under the LGPL.
Besides that, it looks like a problem with Golang, by searching for that error on google this is the second result:
golang/go#21421

Results of the build:

Results from trying to run the x64 build:
ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ ./dist/binaries/gitea-master-linux-amd64 --help
Trace/breakpoint trap (core dumped)

ubuntu@ubuntu-1804-virtual-machine:~/Desktop/gitea$ strace ./dist/binaries/gitea-master-linux-amd64
execve("./dist/binaries/gitea-master-linux-amd64", ["./dist/binaries/gitea-master-lin"...], 0x7ffcbf337170 /* 59 vars */) = 0
brk(NULL)                               = 0x4e77000
brk(0x4e781c0)                          = 0x4e781c0
arch_prctl(ARCH_SET_FS, 0x4e77880)      = 0
uname({sysname="Linux", nodename="ubuntu-1804-virtual-machine", ...}) = 0
readlink("/proc/self/exe", "/home/ubuntu/Desktop/gitea/dist/"..., 4096) = 65
brk(0x4e991c0)                          = 0x4e991c0
brk(0x4e9a000)                          = 0x4e9a000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
arch_prctl(ARCH_SET_FS, 0x3d89d10)      = 0
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
Trace/breakpoint trap (core dumped)

I think I ran into that yesterday when testing. Something about the -linkmode external setting, though in this case the build environment is within a container and appears to work well for the Gitea team, so perhaps I'm still doing something wrong. Maybe make release-linux is not sufficient to fully prep the build environment.

I opened an issue in the Gitea GH repo asking for their feedback. Maybe something about their build process (ignoring the error that I received) generates binaries that don't link against the GNU C Library.

https://github.com/zgoat/goatcounter#building-from-source

Or to build a statically linked binary:
$ go build -ldflags="-X main.version=$(git log -n1 --format='%h_%cI')" \
    -tags osusergo,netgo,sqlite_omit_load_extension \
    -ldflags='-extldflags=-static' \
    ./cmd/goatcounter

https://www.reddit.com/r/golang/comments/8m4xrh/do_linux_golang_binaries_depend_on_libc/

https://github.com/mattermost/mattermost-load-test-ng/blob/master/Makefile

I tried enabling cgo explicitly by providing CGO_ENABLED=1 for each build command, but this produced odd results for Windows:
Building release assets for windows ...
Building mysql2sqlite 386 binaries
# runtime/cgo
gcc: error: unrecognized command line option ‘-mthreads’; did you mean ‘-pthread’?
Building check_mysql2sqlite 386 binaries
# runtime/cgo
gcc: error: unrecognized command line option ‘-mthreads’; did you mean ‘-pthread’?
Makefile:166: recipe for target 'windows' failed
make: *** [windows] Error 2

Per this GH issue (specifically GH user tiaguinho's feedback):
https://github.com/mattn/go-sqlite3/issues/303#issuecomment-218135677
the fix is to either use a Docker container with everything needed already included, or install some additional packages and specify specific options for the Windows builds:

First install this two packages
apt-get install gcc-multilib
apt-get install gcc-mingw-w64
After that I use this command to compile
GOOS=windows GOARCH=386 CGO_ENABLED=1 CXX_FOR_TARGET=i686-w64-mingw32-g++ CC_FOR_TARGET=i686-w64-mingw32-gcc go build
This works for me.

If this is the route used, then the docs will need to be updated to reflect this build requirement.


Run only one instance

Check to ensure there is only one running instance when launching.
That small feature request aside, THANK YOU for making this amazing app! Works perfectly on latest Windows 10 (20H2 as of this ticket).
I have a triple monitor setup, my main is connected via DisplayPort. So previously, each time I turned off/on my monitors my windows would go all over the place. Now with your app, everything stays put and I can't imagine using my computer without it.

fixed


[command recognition] Try to filter out the noise of background and unintended speech in far distance

Since the noise has a large impact on the TTS's performance, it is worth to do denoising of the microphone we chose currently.

since use KWS as a part of the pipeline, need to test if this part is still necessary.

use reference value to enhance the signal detection of high-frequency note, it works pretty well.


Enable publishing new samples under existing projects/collections

Is your enhancement request related to a problem? Please describe.
We would like to be able to add more samples to the existing published projects
Describe the solution you'd like
Add new samples and spectra, update the DOI meta data when published

We need to further discuss this issue along with issues such as updating the files in an already published project.
Changing the data (i.e the files themselves) requires a new doi while updating the doi metadata is allowed when only the metadata of the files is changed (i.e description, keywords...)


feat(besu): update platform helm charts with README.md

Description
As a developer I want to add proper documentation for the helm charts, before they are packaged and published on bevel helm repo
Acceptance Criteria

README.md file added.
vaules.yaml file filled with default values.
chart.yaml versions updated.

I'll take this issue


Script  Doesn't executes completely

Thanks for reporting! I had a similar issue recently and I think it's related to trying to pull an older version of the repo via tags.
Once I get this replicated and fixed on my own miner I'll upload something here.

This happened to me earlier in the day but fixed itself on restart. Ty kindly for the updates @whoabuddy; miner has been up all day!

Fixed in #45


Support accessing type arguments from smoke

 Issue by DanTup
Originally opened as dart-lang/sdk#20584

I'm trying to use smoke for some simple JSON parsing. It all works fine; except that when a type I'm deserialising into has a List<x>, it seems that smoke does not provide any ability to get at the generic type.
Currently I'm working around this (it's just a prototype) by hard-coding a list of the types I know I'm deserialising lists of:
var s = smoke.nameToSymbol(k);
var d = smoke.getDeclaration(t, s);
if (d.type.toString() == "List<ClientGridColumn>")
  smoke.write(obj, s, v.map((sv) => Serializable.fromJson(ClientGridColumn, sv)).toList());
This obviously isn't a scalable solution. It seems like this is the sort of thing that should be possible with smoke; so I hope it might be considered!

 Comment by sethladd

See also http://stackoverflow.com/questions/25371826/how-to-get-the-parameterized-type-of-an-instance-with-dart-and-smoke

 Comment by sethladd

cc @blois.
cc @sigmundch.
Added Area-Pkg, Pkg-Smoke, Triaged labels.


Make Semaphore.core container Operational

semaphore-core

Base image: python 3.10
Ports: None
Files: src directory (except for API directory and runner.py
.h5 files, dspec files at runtime?
.env
Library: from requirements.txt
Volume:

Status

ALL tests pass!
Need entry point


Not available for embedded

It should be clarified somewhere that paginated reports based on Power BI shared data sets cannot be embedded (yet?) in the "App Owns Data" scenario.

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

ID: cf55ca48-9d24-4a87-0f90-b660d3d0ca50
Version Independent ID: 09e9b1e9-82b6-3efd-7b77-040c284b917b
Content: Create a paginated report with a Power BI shared dataset - Power BI Report Builder - Power BI
Content Source: powerbi-docs/report-builder-shared-datasets.md
Service: powerbi
Sub-service: report-builder
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks, @jlhjr ! Confirming with the product team and will update.

Thanks, @jlhjr ! Updating the article today.


Cannot open Appdata or most of it's subfolders (Roaming/Local) from external applications

Description
So, I've replaced File Explorer with File V2 using the registry method. Everything gets redirected to it except when I open the Appdata Folder from any external sources, Like Everything Search, Windows Run dialog, etc.
Steps To Reproduce

Open Run window (Win+R)
type %appdata% and Enter
I get this error message

or

Search for Roaming in Everything Search
Double click to open it and you get same error

Expected behavior
File V2 should open those folders since I've set it to show hidden files/folders.
Notice that I can open the temp folder from both Everything and Run, even though it's in Appdata subfolder.
Files Version
v2
Windows Version
Windows 11 22000.194
Relevant Assets
No response

Is this still an issue in v2.4?


Fix issues for batch size >1

Move offset=0 outside the modality loop otherwise all offsets are zero
Offset should only be +length for text modality as no som/eom token is used
Fixed no_modality_mask to not misalign tensor for some inputs batch size >1

@RefractAI hello! thank you for pointing out the offset error 🤦
i decided to just remove the final masking out, as a length of 0 will not affect the is_any_modality mask later


How to work with vscode lauch.json?

Find no way to set "program" in lauch.json.
Thanks

I don't know what you want to do. please use xmake-vscode plugin. https://github.com/xmake-io/xmake-vscode

I have tried, how does it support all keyboard shortcut manipulation?

I have tried, how does it support all keyboard shortcut manipulation?

Not yet supported. If you are interested, you can try to add support for it.


support external configuration directory for sand and sand grains

Allow sand and sand-grain config to be loaded from a location external to the sand application's config directory.
This change allows configuration to come from three places:

the application's config directory
an external directory specified by the SAND_CONFIG_PATH environment variable -OR- the configPath member of a passed in configuration object (as before)
a passed in configuration object

In the new model, 3 overrides 2 which overrides 1.
This behavior is now consistent across sand's config and each sand-grain's config.

I'd like to fix the tests before this gets merged (even though they are unrelated to my changes)
They work on my local development machine, so I think we have some race conditions here

After some experimentation, it seems that node-pm requires some functions that aren't available in the travis container environment (I suspect setgid() and setuid()).
Setting sudo: required in travis.yml breaks us out of the container environment and back into the legacy travis environment.  This allowed the node-pm tests to run successfully.
Since sand is not really dependent on node-pm, I felt it was better (and ok) to just not run the node-pm tests on travis.
I'm keeping the enhancements I made to the tests where they actually wait for sand to start in the child processes before setting a timeout to kill them (removing race conditions).

@smitt04 this is ready to merged now if you approve


  That's not how mesos-storm is intended to work -- the mesos-slave runs the supervisor.

@erikdw, yes "the mesos slave runs the supervisor" but which command is being used to run the supervisor?
with storm, the command is bin/storm supervisor. When you're running storm on top of mesos, what is the command ? I guess it was bin/storm-mesos supervisor . If not, why do we need the supervisor function in bin/storm-mesos?
how is storm-mesos is intended to work?
Thanks

@salimane : I am not 100% sure of the answer to "how is storm-mesos intended to work".  At my company we build it ourselves in a bit of a hacked-up manner.  I'm trying to understand the stuff that @pdread100 has been doing well enough to support it.
Can you please be a bit more explicit about how you are testing & what build of this project you are using?  I mean, it seems like you aren't just using the vagrant setup that @pdread100 put in, because just following the docs/vagrant.md instructions (mostly) works for me without having to make a change like the one you proposed.

@erikdw Launching task with Mesos Executor data is interesting.
I'm not using the included vagrant. I'm doing the setup using a puppet storm module mirroring a real production setup. For a normal storm setup without mesos, you need to run the nimbus bin/storm nimbus and a supervisor bin/storm supervisor prior to deploying any topology.
It seems running storm on mesos, the nimbus command become bin/storm-mesos nimbus and is run before deploying any topology. But then according to the code, there is no need to run any supervisor as a new one would be started while deploying a new topology.
am i right ?
Thanks

@salimane : " But then according to the code, there is no need to run any supervisor as a new one would be started while deploying a new topology."  --> exactly!  With storm-on-mesos there is one Supervisor per topology per host.  The Supervisor is the Mesos Executor, and it's launched by the MesosNimbus.  And the storm Worker processes are the Mesos Tasks that run within the container created for the MesosSupervisor.  i.e., on a given host there will be N topologies running in N containers.  1 container per topology per host.  Potentially multiple workers of a given topology within each container.  Containers only ever have a single topologies worker processes, they don't get intermixed.  Hopefully I've stated that exhaustively enough to prevent any confusion.
You can take a gander at some slides I created for a talk I gave at a conference earlier this year for some pictorial views of the differences between regular storm and storm-on-mesos:

http://gotocon.com/dl/goto-chicago-2015/slides/BrianMcCalister_and_ErikWeathers_EventStreamsAtGrouponWithStormMesosAndGriddle.pdf

You can also watch me talk through the slides here (just found that this was uploaded!):

https://www.youtube.com/watch?v=TZeHD-z2W6E&t=8m45s

@erikdw  thanks for the explanation. But then in the bin/storm-mesos python script, is the function supervisor() dead code ?
Thanks

@salimane : the supervisor() function in bin/storm-mesos appears to have never been used; here's the initial commit of that script (@brndmatthews ported the code from another repo, so it appears he wrote everything, but much of it was written by Nathan Marz, the original Storm author):

https://github.com/mesos/storm/blob/b007d54b1a7fad5044932798c1000149d14afd14/bin/storm-mesos#L13-L14

Notably, the invocation of the supervisor wasn't using the bin/storm-mesos script then, and isn't doing so now:
https://github.com/mesos/storm/blob/b007d54b1a7fad5044932798c1000149d14afd14/src/storm/mesos/MesosNimbus.java#L400
So I think it's been dead this whole time...

@erikdw I've updated the pr to remove the misleading supervisor dead code.
Thanks

Thanks!

thanks for the change @salimane & thanks for merging @brndnmtthws !


Add an RSS feed!

What problem does this solve or what need does it fill?
I sadly don't have much time to use Bevy but I do like to live vicariously through the Bevy news. I check manually multiple times a week to see if there is any new news. I'd love a way to get notified if there is anything new!
What solution would you like?
I think adding an RSS feed file to the news would be a pretty good, easy solution, vs some kind of email subscription list or something.
What alternative(s) have you considered?
N/A
Additional context
Nope!

https://bevyengine.org/atom.xml should be an RSS feed from the website

Oh neato there you have it! Maybe a button on the news page would be handy.


Updated Facebook API version

Updated Facebook API to latest version and made it configurable.
https://github.com/nraboy/ng-cordova-oauth/issues/341

I'll run a couple more tests on my end and then confirm.

In our environment this is working. Is there a suite of tests that are usually run for this plugin?


Unable to install

Describe the bug
Following the "Getting Started" guide, when I get to the third step I get an error.
To reproduce
did this:
composer require filament/filament
php artisan migrate

Then this, but get an error: Route [filament.auth.login] not defined
php artisan make:filament-user

I enter name, password and "yes" to create an administrator user.
Screenshots

Context
Fresh Laravel 8 Jetstream with Teams and Livewire.
php 8

Same here. Laravel 8, PHP 7.4.

I did a fresh installation of w Laravel 8 Jetstream + teams.
it worked. Will try to figure out what Filament doesn't like with my boilerplate.

After running a php artisan route:clear before installation, problem solved. 👍

I found the culprit in my boilerplate.
Collided with my custom config/nova->path and filament default url. Both were set to "admin".
A humble suggestion would be to add a check to the Filament RouteServiceProvider.
Like
// if route exists
// throw an error to console
// else
// register the routes to the app...

Guess others might have an existing admin route when installing the package.

how did you solve that, I already got installed nova now I want also to add filament...? thanks in advance

how did you solve that, I already got installed nova now I want also to add filament...? thanks in advance

i'm just digging into filament and i ran into the same issue, filament path conflicts with what i have in nova config, so i will suggest you change nova.path in config to something different from what filament uses

check my forum
https://laracasts.com/discuss/channels/code-review/install-nova-and-filament

if you using linux php, you can install :
im using Fedora :
sudo dnf install php-intl
Linux apt :
sudo apt-get install php-intl
and try install filament laravel again :
composer require filament/actions:"^3.2" -W
its worked for me
php 8.2.18
laravel 11
OS Linux Fedora 39


Source goes empty when Book/chapter/verse/ID is removed at the target side

Source goes empty when Book/chapter/verse is removed at the target side

In a tN project>open a file> select the columns selection for Books/chapter/verse /Id to be displayed.
Remove the text from either of the Books/chapter/verse /Id fields and tab out.
Note that the source side goes empty on all the fields.
Type-in back the data that was cleared in step 2. the Source is populated back again.

In a tN project>open a file> select the columns selection for Books/chapter/verse /Id to be displayed.
Remove the text from either of the Books/chapter/verse /Id fields and tab out.
Note that the source side goes empty on all the fields.
Type-in back the data that was cleared in step 2. the Source is populated back again.


Could we provide a development docker image that is able to build out of box ?

it takes me a day to setup the build environment and it's  still not working.  Clickhouse provided a clickhouse/binary-builder docker images for ci/cd which would also help developer to setup an environment . Wondering if we could do that for chdb.

thanks @lmangani
I tried with clickhouse/binary-builder, installed python3-pip, cmake, ninja-build. and run pip install -U pip setuptools -e .
then I got this:
      CMake Error at contrib/cyrus-sasl-cmake/CMakeLists.txt:79 (target_link_libraries):
        Target "_sasl2" links to:

          ch_contrib::krb5

@qingant alright, I'll try to sketch a dedicated chdb docker builder mimicking the action builder and post updates

@qingant the test builder seems to work fine. Could you check and confirm? https://github.com/lmangani/chdb-builder

Repository moved to chdb-io/chdb-builder feel free to open any issue there to continue improving the builder


Laters commits on Jitpack are not building

Hi,
Snaphost and other latest commits on Jitpack build is failing.
Snaphsot build log
Thanks in advance

You shouldn't use JitPack for this library.


[embedded] Update UserManual.md and EmbeddedSwiftStatus.md with some additional information

See the diff for details.

@swift-ci please smoke test


Document Custom Routes

As per https://github.com/danschultzer/pow/issues/341 and https://github.com/danschultzer/pow/issues/248 I thought it would be helpful to add this to the Readme, as it was literally the only thing I needed to do that I couldn't figure out from the docs.

Thanks! I've moved them over to the router docs rather than the readme. I'll eventually make a "Getting started" guide and remove pretty much everything in the readme and just rely on module docs and the guides in the future.


feat(installer): use cloudsmith instead of gh to fetch preview version

gh requires a valid token - in this PR I exchange it for cloudsmith which does not and now people who don't have a valid token can try out the preview version
Did you sign your commit? Instructions yes
Have you read Contributing guidelines? yes

The end story is why do we have previews in this script?
My original idea when I added this was: being able for external users to use a trusted build to check upcoming features, validate fixes... For this having VERSION=preview be something we think works (e2e pass) would be useful.
@michaelbeaumont definition of what this script should return seems different as: something for the dev team to debug which I think is different and orthogonal to this.
For @michaelbeaumont 's usecase you can always open a PR with e2e tests skipped to get something equivalent (or just build locally). I think using cloudsmith solves a bunch of access issues which I think is meaningful (external users able to use VERSION=preview is a use case).
If we want to do this real difference I think what should happen is build, push to a prerelease area (this includes docker images) then once validated move to the actual release area. In that case you could use cloudsmith (and docker) for both and even have latest docker tags.

@michaelbeaumont definition of what this script should return seems different as: something for the dev team to debug which I think is different and orthogonal to this.

No. it's for allowing users to run KM independent of whether e2e tests complete. we had multiple cases where customers were trying to test out master builds but e2e flakes stopped this from happening.


organization of folders

I think the project based should be well structured. The based of project now contain too many files. For newly to laravel framework or touch the website development(like me ;p). it's not a good beginning.
I suggest put the bower_components and node_modules should be place a folder (for example setup) for people who newly to the laravel framework to easily setup and manage. Also, it can easily remove setup files once configured or reconfigured project before running the setup commands (like project name) if possible!

Hi @KerrickChan
Thanks for your feedback!
Unfortunately these folders (bower_components & node_modules) are required along the way..
One solution would be to place bower_components inside the vendor folder.. but personally I'm not a fan of changing this kind of convention.
Regarding the other files, if you look at the composer.json on Line 45 to 48
Whenever you create a new project using composer create-project we are automatically deleting files that are only used by the repository (most of them are for hosting).
The only folder that remains is the .ebextensions
This can be removed, but I thought it would be a great starting point for people that plan on hosting on Amazon Web Services' Elastic Beanstalk.. but it might be also cleaner if we remove it when creating a new project
Let me know what you think
and I hope to get your feedback so we can make this repository better
Thanks!

Closing this for inactivity
Feel free to comment if you have any quesitons


'Unreachable code detected' after transaction

Overview
Running a transaction causes all code following the transaction to become unreachable.
Version info
@angular/cdk: 5.1.1
@angular/cli: 1.6.6
@angular/material: 5.1.1
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.0.52
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.6
@schematics/angular: 0.1.17
typescript: 2.5.3
webpack: 3.10.0

How to reproduce these conditions
  //Create Firestore reference
let pointsRef = 'Users/'+this.user.uid;
var pointsDocRef = this.afs.doc(pointsRef).ref;

return this.afs.firestore.runTransaction((transaction) => {
  return transaction.get(pointsDocRef).then((ptsDoc) => {
    if(!ptsDoc.exists){
      throw "Document does not exist!"
    }

    var newPtsScore = ptsDoc.data().points - 20;
    transaction.update(pointsDocRef, { points: newPtsScore });
  });
}).then(() => {
  console.log('Point count successfully decremented for new item');
  //Close dialog
  this.dialog.closeAll();
}).catch(function(error) {console.log('Transaction failed: ', error);});

console.log('Hey there!') <-- "UNREACHABLE CODE DETECTED"

Screenshot
Expected behavior
Transaction should allow the rest of the code to execute like normal
Actual behavior
Running a transaction (with an exposed return) causes all code following the return to become unreachable

Hi @FiringBlanks! The code is unreachable because you are returning on one line and then writing code after the the runTransaction block.
// all code after the runTransaction callback is unreachable because you are returning
return this.afs.firestore.runTransaction((transaction) => {

@davideast I know why it's happening, but the way transactions are designed cause them to interrupt the flow of code. This would mean that you can't run two transactions in the same .ts file.

@FiringBlanks Don't return the transaction result. Just store the promise as a variable instead. Or use Promise.all() for multiple transactions.


Update Maturin to 1.2.3 and build aarch64 wheels

Bumped version to 0.0.7
Added CI to create wheels for windows, macOS (x86 and aarch) and linux
Bumped version of minimap2-sys to 1.15, which now builds correctly on aarch64.
This should mean we have native wheels on macOS - I think

LGTM
Will say that the tests have only run on Ubuntu x86 and that probably is a separate issue that needs addressing.