Infinite Loop in the Transaction Profiler

Summary

The transaction profiler profiler.go loops infinite if the transaction duration exceeds the profilerRuntimeLimit, causing the application to terminate due to OOM.
Steps To Reproduce
func main() {
	err := sentry.Init(sentry.ClientOptions{EnableTracing: true, ProfilesSampleRate: 1})
	if err != nil {
		fmt.Printf("sentry.Init: %s", err.Error())
		return
	}

	span := sentry.StartSpan(context.Background(), "main", sentry.WithSpanSampled(sentry.SampledTrue))
	time.Sleep(35 * time.Second)
	span.Finish()
}

Expected Behavior

Either:

The Sentry SDK is able to profile also transactions lasting longer than 30 seconds without crashing the application.
The Sentry SDK discards the profiling of transactions exceeding the profilerRuntimeLimit.

Environment

SDK

sentry-go version: v0.24.1
Go version: 1.21.1
Using Go Modules? yes

Sentry

No Sentry Backend required to reproduce the behavior.

Additional context
The following loop runs infinite:
https://github.com/getsentry/sentry-go/blob/7e37edeb9589c5e8966c5c80822aa4ddaa0fbfd2/profiler.go#L243-L251
The profilerRuntimeLimit defines a limit of 30 seconds. If the transaction lasts longer, the start-30-second-ring-structure is filled completely which causes both break conditions to not apply.

@vaind Can you take a look, please?

#725 fixes this issue for me. Thank you for getting a PR with the fix out so quickly!

The fix was released in 0.25.0. Thanks for confirming the fix @cjcormack 🙏

I can confirm that release 0.25.0 resolves our issue. Thank you for your quick solution!


Added noviicee to maintainers.yml

Added noviicee in maintainers.yml file .

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/india/blob/main/CONTRIBUTING.md.

Which change are you proposing?

[ ] Adding/updating open source project/s
[x] Adding/updating maintainer/s

Adding/updating maintainer/s

[x] Maintainer's location on their GitHub profile indicates as India
[x] Maintainer has approved this PR to be included on the website

What open source project/s does the individual maintain?
CompetitiveProgrammingQuestionBank
Banque-De-Questions

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Can I please get a review on this one..? :)


Review all selectors that would trigger an error message

If a selector is missing a hint, an error will be produced. For framework and boot let's review how many are missing hints and try to cover them in 0.7.

I haven't done them all - but I've added coverage of a few more. Some are straightforward but some are dynamically loading types based on what is in the annotations they have access to - hard to predict what those really need and I don't want to tackle them until we have good test examples.
kafka is now covered, which I know we have an issue about (and that was a straightforward one).


hello world using Smalltalk language

/label hacktoberfest-accepted

Please update the branch once, pull all changes from the main repository, then I'll merge.

means what I do now?

@Mergifyio update


Switch maps from Embed map to Javascript API map

Switch to an interactive map where user can zoom and move about to other neighborhoods. Keep the search function so users can quickly focus map on a specific neighborhood.

updated map unfortunately does not render in Firefox. adding new issue for this.

Change the map to use the Google Maps Javascript API. The Embed API, which I currently have up, does not allow editing maps (adding custom pins).

Updated map


Edit box does not close after a second edit is made

Edit box in the expanded scripture pane does  not close after one edit is made and saved. The edits are not lost but it is confusing to the user as if the app is hung.

@elsylambert This is fixed in latest build checking-extension-0.9.0-d472aac.vsix

Looks good in the latest v0.9.0. Edits can me done multiple time and saved correctly without any delay.


ipv6 obfuscation

ipv6 addresses are currently replaced by ::1. The less restrictive way would be to keep the first three octets, similar to what Chrome does in onicecandidateerror

or chrome in general as the comment from the chrome logs shows:
        // TODO: Gathered candidate: Cand[:3209149097:1:udp:2121804031:[2600:380:76ec:x:x:x:x:x]:51639:
        // apparently ok to use first three octets and obfuscated the rest


test direct mode and LVM

This changes the test setup such that the CI covers LVM and direct mode on Kubernetes 1.14. To make it work well, some tweaks to the deployment and VM setup are needed.

Testing in the CI showed that the reduced size of the test cluster apparently caused test failures (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-327/43/pipeline) while it worked without that change (current test result in https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-327/44/pipeline).
So let's merge it without that change (current state of the PR).

So let's merge it without that change (current state of the PR).

I forgot to force-push the removal of the size commit. Build results were clean only by chance, the first run of testing 1.14 direct had failed and now also fails on devel.
I'm not sure whether this particular commit is really the reason for the flaky test behavior, but let's revert it anyway:
https://github.com/intel/pmem-csi/pull/352


Publish 07/29/2021, 3:30 PM

Docs Build status updates of commit 6ce61c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/international/Get-WinLanguageBarOption.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/iscsi/Update-IscsiTargetPortal.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012-ps/netqos/New-NetQosPolicy.md
:white_check_mark:Succeeded
View (winserver2012-ps)

docset/winserver2012r2-ps/international/Get-WinLanguageBarOption.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/iscsi/Update-IscsiTargetPortal.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2012r2-ps/netqos/New-NetQosPolicy.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/international/Get-WinLanguageBarOption.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/iscsi/Update-IscsiTargetPortal.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2016-ps/netqos/New-NetQosPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/international/Get-WinLanguageBarOption.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/iscsi/Update-IscsiTargetPortal.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/netqos/New-NetQosPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/international/Get-WinLanguageBarOption.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/iscsi/Update-IscsiTargetPortal.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/netqos/New-NetQosPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Is this a bug ?

html code
A) < p >blah-blah-blah< /p> <- OK with NO-space
B) < p>blah-blah-blah< /p> <- WEIRD, < + space + p+>,  "& lt; p& gt;"
call serialize()
the result is weird.
Is this intentional ?

@octalflow
The behavior is correct.


Drop Python 3.8 support

While Python 3.8 is reaching its end-of-life, maybe we should also consider dropping the support (at least in the generated project)? Currently the DevContainer workflow is failed due to Python 3.8 compatibility issue, and it needs extra hack to fix.
More evidence:

Sphinx 7.2.0 already drop Python 3.8 support on Aug 17, 2023.
pre-commit v3.6.0 alreay drop support for python<3.9 on Dec 10, 2023.

@msclock Any comments?

@msclock Any comments?

I consider Python 3.8 is not up to the end of life  to security and has not escaped developer selection. Moreover, the scaffold has not yet released a maintainable version. Is the pdm support to resolve the conflicts?
Importantly, why is it not a breaking change when dropping python version support.Ideally, when a breaking change happends, the major version increment can ensure the following fixes and patches more maintainable release. So I really think it needs to consider carefully.

the scaffold has not yet released a maintainable version.

Actually, this is also one point for me, since the project is still in alpha stage, and there is only half a year remaining for Python 3.8, maybe it is more ease to propose this breaking change.

Is the pdm support to resolve the conflicts?

Hack are needed in the DevContainer Dockerfile and with that hack, we will lose the renovate update, I will propose a back-compatible hack later.

Importantly, why is it not a breaking change when dropping python version support.Ideally, when a breaking change happends, the major version increment can ensure the following fixes and patches having more maintainable release. So I really think it needs to consider carefully.

Gotcha, thanks for your reminder.

the scaffold has not yet released a maintainable version.

Actually, this is also one point for me, since the project is still in alpha stage, and there is only half a year remaining for Python 3.8, maybe it is more ease to propose this breaking change.

Is the pdm support to resolve the conflicts?

Hack are needed in the DevContainer Dockerfile and with that hack, we will lose the renovate update, I will propose a back-compatible hack later.

Importantly, why is it not a breaking change when dropping python version support.Ideally, when a breaking change happends, the major version increment can ensure the following fixes and patches having more maintainable release. So I really think it needs to consider carefully.

Gotcha, thanks for your reminder.

If it is urgent, the pr also is fine. But it might require a backfoward compatibility later. And it should ensure a minor change at least.🤣

It is absolutely not urgent, but a compatibility strategy. Another question could be, why does sphinx drop Python 3.8 support so early, even before Python 3.12 is released.


Add condition to generate release file in local dev build only

PR Summary
Allow a switch to skip generation of dummy files.. During local dev build, the files will be created.
PR Context

PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

depends on #16258

/backport to release/v7.0.11


stat adds an extra 0 to access bits of files with special permissions enabled

If I stat a file with set{u,g}id and the sticky bit disabled, the permissions section of the output will correctly display something like Access: (0755/-rwxr-xr-x) but if I do the same with a file that has one of the 3 special permissions enabled, in the following example setuid, the expected output would be Access: (4755/-rwsr-xr-x) but with toybox stat it is Access: (04755/-rwsr-xr-x).

Fixed in commit e5942a8c90c2.


There is no way to run my code with custom dependencies

Describe the bug
For Spark engine，only driver classpath appending is supportted, there is no way to add any dependency jars into classpath for executors.
this.driverClassPath(SPARK_CONF_DIR.getValue)
  this.driverClassPath(HADOOP_CONF_DIR.getValue)
  this.driverClassPath(SPARK_DRIVER_CLASSPATH.getValue)

Expected behavior
if there is any workaround before bug fixing, pls show me the guide instead of a word.

Hello, this is supported, you can configure the --jars parameter, you can refer to SparkSubmitProcessBuilder class
SparkSubmitProcessBuilder:
properties.getOrDefault("jars", "").split(",").map(RelativePath).foreach(jar)


Fix slow wallet deletion and db issues

Issue Number
ADP-827
Overview

[x] Don't retry on SQLITE_BUSY when trying to close

Comments

The retrying would timeout anyway, leaving the connection open and the file un-deleted.

Alternative attempts / notes

.deleted lock and removing waitForFree lead to err500 on wallet creation.
(On master) it seemed to consistently (100% of the time) get stuck in destroySqliteBackend trying to close, when a db query was cancelled.

Effects on tests
With -j 8

240s
0 >10s DELETE or POST /wallet requests

New approach — just remove the retries to close' on SQLITE_BUSY:
I compared it with master, and they seem similar in the amount of wallets not being cleaned up:
ADP-827.zip

Closing for now


Create C tests for command parser

This task has two parts:

Setup a unit testing runner system
Write unit tests for the command parser

Two options to setup the unit testing runner system:

Try to get the Unity framework to work. Tests run on computer hardware, so compiling might be tough.
Just write our own thing that logs all the tests over UART/comms/to a file. I personally am a fan of this option, as it'll allow us to run our tests in space if we're having issues. It'll also allow us to use the same ideas for both Unit Tests and System Integration Tests.

The unit test framework is setup in #26. More can always be done on unit testing, but I'm happy with the current state.


⚠ ClamAV has degraded performance

In cd995e9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 50 ms

Resolved: ClamAV performance has improved in e73fafe.


Link window modal

Hello!
How can i avoid link window from showing again. When i remove whitespace after link, link window modal shows again.
Thanks in advance

https://github.com/bootstrap-wysiwyg/bootstrap3-wysiwyg/issues/104

Follow this thread

That's what i was looking for!
Thanks


Added Powerline like > < separators

solution for #21
It works, doesn't look bad .
Need to do some cleanup on the code.

I think it's quite stable now

I think it's quite stable now

Does anyone know of any unicode symbles that can be used for this without patched fonts?

Does anyone know of any unicode symbles that can be used for this without patched fonts?

I think we should keep separators from https://github.com/hoob3rt/lualine.nvim/pull/55/commits/ef3dff46b492b2d5198f2c81159416433e7fe8e7 as default. They work with nerd fonts well while the current defaults crash on nerd fonts and display funny emojis with emoji theme installed

I think we should keep separators from https://github.com/hoob3rt/lualine.nvim/pull/55/commits/ef3dff46b492b2d5198f2c81159416433e7fe8e7 as default. They work with nerd fonts well while the current defaults crash on nerd fonts and display funny emojis with emoji theme installed

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

I think we should keep separators from ef3dff4 as default. They work with nerd fonts well while the current defaults crash on nerd fonts and display funny emojis with emoji theme installed

Funny naver thought they would look like this . Though it will be a small fix.

I think we should keep separators from ef3dff4 as default. They work with nerd fonts well while the current defaults crash on nerd fonts and display funny emojis with emoji theme installed

Funny naver thought they would look like this . Though it will be a small fix.

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

Why not ?

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

Why not ?

changed to nerd font separators

changed to nerd font separators

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

I've realized they aren't found in powerline . I've removed them

Also there is a new visible bug, there should be no separator after filaneme or before utf-8 here.

I've realized they aren't found in powerline . I've removed them

Closed in favor of #94.


Use <= and < instead of > or >= in comparison

Hi.
I have tried to search in the docs and on the web for a Rubocop rule to use <= and < instead of > or >= in comparison, but can't seem to find anything about it.
Example:
# bad
a > 2
3 >= b

#good
2 < a
b <= 3
4 < c && c <= 7

It can conflict with YodaCondition however I find it easier/faster to figure out when only using the same operators.

I'm interested in why you believe comparison in one direction is better than the other, or is the issue simply that which ever way the comparison goes it should be consistent across the code base?
Consider giving value objects a look for this sort of work, since that can encapsulate simple type comparison pretty well ')

This seems like a reasonable thing for Rubocop to support. I think ascending comparisons are more natural coming from a mathematical background.
(@casper91 I think the first two "bad" "descending" examples are already descending.)

Yeah, "ascending" is also my preferred choice.
Updated Example, thanks!

I find that a > 2 is more clear than 2 < a, because the variable is the first thing I read, so cognitively it takes up fewer resources. <variable> <operator> <value> should perhaps be the default.


latest Aurelia version

are these the correct scripts to use for the latest Aurelia in aurelia-bundle?
    <script src="https://cdn.rawgit.com/jdanyow/aurelia-bundle/master/jspm_packages/system.js"></script>
    <script src="https://cdn.rawgit.com/jdanyow/aurelia-bundle/master/config.js"></script>

the latest aurelia bundle is here: https://gist.run/?id=7542e061bc940cde506b
<script src="https://cdn.rawgit.com/jdanyow/aurelia-bundle/v1.0.3/jspm_packages/system.js"></script>
 <script src="https://cdn.rawgit.com/jdanyow/aurelia-bundle/v1.0.3/config.js"></script>

It's pretty recent- some of the updates from the last week are not yet in there.  Will be updating it soon.

Would be great to get an update. Perhaps an automated build system would solve the problem of manual updates?

latest is here https://gist.run/?id=7542e061bc940cde506b

while open the this latest Aurelia https://gist.run/?id=7542e061bc940cde506b getting the below console error.
/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.
about:blank:1 Refused to display 'https://gist.host/' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.
https://gist.host/ Failed to load resource: the server responded with a status of 403 ()

That's an issue in gist.run- it's running an old build of Aurelia. Will be fixed next time I push a new build out.
The Aurelia gist IS up to date.  Safe to ignore that message for now.


FloatingActionButton in FloatingActionMenu with Progress

When I insert a Floating Action button in the Floating Action Menu and give it a progress, the button jumps inside the view to the left edge and moves up. This looks with one button ugly, with more than one the menu is messy.

Did you find a solutio. To this?

https://github.com/Clans/FloatingActionButton/pull/261


Update packages.json

Thanks for the great site Dave!
Added a couple of my packages. Some are command line tools, but they also include libraries that people use.

Thanks!


Docs: Add StackBlitz edit button for examples

Related issues
Closes #36857
Description
This PR proposes to add a StackBlitz edit button for each Bootstrap example.
TODO: add more details to explain the technical solution
Motivation & Context
TODO
Type of changes

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly

Live previews

Docs > Examples

Manual tests
For each example, try the StackBlitz edit button and then check if the rendering is the same as within our docs: CSS, JS, etc.

Album // Album RTL
Blog // Blog RTL
Carousel // Carousel RTL
Cheatsheet // Cheatsheet RTL
Checkout // Checkout RTL
Cover

⚠ Missing .h-100 for html.

Dashboard // Dashboard RTL

⚠ Doesn't seem to work because index.js in StackBlitz is executed before the scripts in <script> (index.html)

Dropdowns
Features
Footers
Grid
Headers
Heroes
Jumbotron
List groups
Modals
Navbar bottom
Navbar fixed
Navbar static
Navbars
Navbars offcanvas
Offcanvas navbar
Pricing
Product
Sidebars
Sign-in
Starter template
Sticky footer

⚠ Can't work because it needs class="h-100" on the html tag which is not possible in StackBlitz since this class is overriden. Do we remove the StackBlitz edit button?

Sticky footer navbar

Remaining things to do

[x] Handle 404 errors when using fetch
[x] Handle extra JS files
[x] Handle RTL (CSS)
[x] Handle RTL (JS)
[x] Check how to handle relative URL like /docs/5.2/assets/brand/bootstrap-logo.svg in the body
[ ] Remove the bootstrap-bundle.min.js in `

@julien-deramond it would help a lot if you are able to separate the renaming changes, and continue with the functionality additions,

@julien-deramond it would help a lot if you are able to separate the renaming changes, and continue with the functionality additions,

Yes, if you're OK with the renaming for the consistency, I can create a separate PR right now and then work on the addition of the StackBlitz edit buttons.


[help] How to add SystemMessage to ConversationalRetrievalQAChain?

Hey guys,
I've setup a CRQAChain with a vectorStore. I'm struggling to pass a system message that would tell the LLM what it's name is.
Failed attempt (snippet, not whole app):
 // Create a system message
 const systemMessage = "Your name is Enigma"

  // Create a chain that uses the OpenAI LLM and Pinecone vector store.
  const chain =  ConversationalRetrievalQAChain.fromLLM(
    chat,
    vectorStore.asRetriever(),
    {
      memory: new BufferMemory({
        memoryKey: "chat_history",
        inputKey: "question",
        returnMessages: true
      }),
      returnSourceDocuments: false,
      verbose: false,
      // #1: systmeMessage attempt
      questionGeneratorChainOptions: {
        template: systemMessage // pass systemMessage as context for CRQAChain
      }
    },);

  // call chain with latest user input from messages array, catch errors
  chain
    .call({ question: json.messages[json.messages.length - 1].content })
    .catch(console.error)

Suffice it to say the llm has no idea it's name is Enigma. I've wracked my brain on this for a few days, so any help would be greatly appreciated.
Example: I can get it to work with FlowiseAI just fine, but I'm trying to learn how to do it myself.

SOLUTION: use templates with qaChainOptions
Dove into Flowise Docs for a useful example.) and Langchain Docs for help.
  // Create templates for qaChainOptions to use as instructions for the chain and chat model
  const qa_template = `Use the following pieces of context to answer the question at the end.

  {context}

  Question: {question}
  Helpful Answer:`

  const sys_template = `I want you to act as a document that I am having a conversation with. Your name is Enigma. You will provide me with answers from the given info. If the answer is not included, search for an answer and return it, and make a note that you searched outside of the given info. Never break character.`

  // Create a chain that uses the OpenAI LLM and Pinecone vector store.
  const chain =  ConversationalRetrievalQAChain.fromLLM(
    chat,
    vectorStore.asRetriever(),
    {
      memory: new BufferMemory({
        memoryKey: "chat_history",
        inputKey: "question",
        outputKey: "text",
        returnMessages: true
      }),
      returnSourceDocuments: false,
      verbose: false,
      // SOLUTION
      qaChainOptions: {type: "stuff", prompt : PromptTemplate.fromTemplate(`${sys_template}\n${qa_template}`) }
    },
    );

  // call chain with latest user input from messages array, catch errors
  chain
    .call({ question: json.messages[json.messages.length - 1].content })
    .catch(console.error)

Hopefully this will help anyone down the road attempting to use langchainjs docs.


Nitpicks on CDC article

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/blog/change-data-capture
What part(s) of the page would you like to see updated?
Explicitly call out antipatterns:
On my first read through, I only skimmed this article, so originally didn't see that most of the Scenario block is describing the antipattern implementation. Especially since it is so meticulously documented!
If we're going to include the what not to do version, it should be very very clearly called out at the top of the segment. (See also my kvetching about this in a different context)
Potentially move the comparison chart up higher
I'm less attached to this opinion, but I also think it'd be useful to pull up the comparison chart at the bottom to before the two better alternatives, so that the reader is going in with a bit more context:

Clarify dbt's relationship to versioning
Finally, "Because of this, the concepts of “version history” and “backups” aren’t intrinsic to dbt" is a bit unfair – version control isn't intrinsic to any programming language, it sits on top of the text files. I'm worried that it'll get pulled out into a Google extract one day like

I don't really know what to write instead though sorry!
Additional information
No response

@graciegoheen and @krevitt I guess this is you? Not sure exactly who to @

@johnblust Tagging you here as well


[SUPPORT] Hudi failed to sync new partition table to glue data catalog

Describe the problem you faced
I am trying to bulk_insert a small table (~150MB) into s3 using Apache hudi.
I want to partition the data based on created field with format yyyy/MM/dd  using hive_style_partitioning.
The table (with partition subfolder) is created successfully on S3,
However, Hudi failed with the following :
Caused by: org.apache.hudi.hive.HoodieHiveSyncException: Failed to sync partitions for table brand_tree
...
Caused by: java.lang.IllegalArgumentException: Partition key parts [created] does not match with partition values [2019, 01, 17]. Check partition strategy.

here my bulk_insert configuration:
{
'hoodie.bulkinsert.shuffle.parallelism': 3,
'hoodie.datasource.write.operation': 'bulk_insert',
'hoodie.datasource.write.keygenerator.class': 'org.apache.hudi.keygen.CustomKeyGenerator',
 'hoodie.datasource.hive_sync.partition_extractor_class': 'org.apache.hudi.hive.MultiPartKeysValueExtractor',
'hoodie.deltastreamer.keygen.timebased.timestamp.type': 'DATE_STRING',
'hoodie.deltastreamer.keygen.timebased.output.dateformat': 'yyyy/MM/dd',
'hoodie.deltastreamer.keygen.timebased.input.dateformat': 'yyyy-MM-dd HH:mm:ss',
'hoodie.datasource.write.partitionpath.field': f'{partition_key}:TIMESTAMP',
 'hoodie.datasource.hive_sync.partition_fields': f'{partition_key}',
'hoodie.datasource.write.hive_style_partitioning': 'true',
'hoodie.deltastreamer.keygen.timebased.input.dateformat.list.delimiter.regex': '',
'hoodie.deltastreamer.keygen.timebased.input.timezone': 'GMT',
'className': 'org.apache.hudi', 'hoodie.datasource.hive_sync.use_jdbc': 'false',
'hoodie.datasource.write.precombine.field': pre_combine_key,
'hoodie.datasource.write.recordkey.field': ','.join(record_keys),
'hoodie.table.name': table_name,
'hoodie.consistency.check.enabled': 'true', 'hoodie.datasource.hive_sync.database': db_name,
'hoodie.datasource.write.table.name': table_name,
'hoodie.datasource.hive_sync.table': table_name, 'hoodie.datasource.hive_sync.enable': 'true',
'hoodie.datasource.write.table.type': "COPY_ON_WRITE",
'hoodie.index.type': "GLOBAL_SIMPLE"
}

And here the Python:Traceback:
2021-11-16 11:26:57,813 ERROR [main] glue.ProcessLauncher (Logging.scala:logError(70)): Error from Python:Traceback (most recent call last):
  File "/tmp/dev-poc", line 357, in <module>
    main()
  File "/tmp/dev-poc", line 353, in main
    rds_job_driver.run()
  File "/tmp/dev-poc", line 228, in run
    self.transform()
  File "/tmp/dev-poc", line 330, in transform
    partition_key=partition_key)
  File "/tmp/dev-poc", line 176, in overwrite
    self.write_df(data_frame, write_mode, target_path, self.data_format, **combined_conf)
  File "/tmp/dev-poc", line 91, in write_df
    save(target)
  File "/opt/amazon/spark/python/lib/pyspark.zip/pyspark/sql/readwriter.py", line 734, in save
    self._jwrite.save(path)
  File "/opt/amazon/spark/python/lib/py4j-0.10.7-src.zip/py4j/java_gateway.py", line 1257, in __call__
    answer, self.gateway_client, self.target_id, self.name)
  File "/opt/amazon/spark/python/lib/pyspark.zip/pyspark/sql/utils.py", line 63, in deco
    return f(*a, **kw)
  File "/opt/amazon/spark/python/lib/py4j-0.10.7-src.zip/py4j/protocol.py", line 328, in get_return_value
    format(target_id, ".", name), value)
py4j.protocol.Py4JJavaError: An error occurred while calling o164.save.
: org.apache.hudi.exception.HoodieException: Got runtime exception when hive syncing brand_tree
	at org.apache.hudi.hive.HiveSyncTool.syncHoodieTable(HiveSyncTool.java:132)
	at org.apache.hudi.HoodieSparkSqlWriter$.org$apache$hudi$HoodieSparkSqlWriter$$syncHive(HoodieSparkSqlWriter.scala:425)
	at org.apache.hudi.HoodieSparkSqlWriter$$anonfun$metaSync$2.apply(HoodieSparkSqlWriter.scala:479)
	at org.apache.hudi.HoodieSparkSqlWriter$$anonfun$metaSync$2.apply(HoodieSparkSqlWriter.scala:475)
	at scala.collection.mutable.HashSet.foreach(HashSet.scala:78)
	at org.apache.hudi.HoodieSparkSqlWriter$.metaSync(HoodieSparkSqlWriter.scala:475)
	at org.apache.hudi.HoodieSparkSqlWriter$.commitAndPerformPostOperations(HoodieSparkSqlWriter.scala:548)
	at org.apache.hudi.HoodieSparkSqlWriter$.write(HoodieSparkSqlWriter.scala:238)
	at org.apache.hudi.DefaultSource.createRelation(DefaultSource.scala:170)
	at org.apache.spark.sql.execution.datasources.SaveIntoDataSourceCommand.run(SaveIntoDataSourceCommand.scala:45)
	at org.apache.spark.sql.execution.command.ExecutedCommandExec.sideEffectResult$lzycompute(commands.scala:70)
	at org.apache.spark.sql.execution.command.ExecutedCommandExec.sideEffectResult(commands.scala:68)
	at org.apache.spark.sql.execution.command.ExecutedCommandExec.doExecute(commands.scala:86)
	at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:131)
	at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:127)
	at org.apache.spark.sql.execution.SparkPlan$$anonfun$executeQuery$1.apply(SparkPlan.scala:155)
	at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
	at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:152)
	at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:127)
	at org.apache.spark.sql.execution.QueryExecution.toRdd$lzycompute(QueryExecution.scala:80)
	at org.apache.spark.sql.execution.QueryExecution.toRdd(QueryExecution.scala:80)
	at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:676)
	at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:676)
	at org.apache.spark.sql.execution.SQLExecution$$anonfun$withNewExecutionId$1.apply(SQLExecution.scala:78)
	at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:125)
	at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:73)
	at org.apache.spark.sql.DataFrameWriter.runCommand(DataFrameWriter.scala:676)
	at org.apache.spark.sql.DataFrameWriter.saveToV1Source(DataFrameWriter.scala:285)
	at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:271)
	at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:229)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
	at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357)
	at py4j.Gateway.invoke(Gateway.java:282)
	at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
	at py4j.commands.CallCommand.execute(CallCommand.java:79)
	at py4j.GatewayConnection.run(GatewayConnection.java:238)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hudi.hive.HoodieHiveSyncException: Failed to sync partitions for table brand_tree
	at org.apache.hudi.hive.HiveSyncTool.syncPartitions(HiveSyncTool.java:332)
	at org.apache.hudi.hive.HiveSyncTool.syncHoodieTable(HiveSyncTool.java:188)
	at org.apache.hudi.hive.HiveSyncTool.syncHoodieTable(HiveSyncTool.java:118)
	... 40 more
Caused by: java.lang.IllegalArgumentException: Partition key parts [created] does not match with partition values [2019, 01, 17]. Check partition strategy.
	at org.apache.hudi.common.util.ValidationUtils.checkArgument(ValidationUtils.java:40)
	at org.apache.hudi.hive.HoodieHiveClient.getPartitionClause(HoodieHiveClient.java:223)
	at org.apache.hudi.hive.HoodieHiveClient.constructAddPartitions(HoodieHiveClient.java:199)
	at org.apache.hudi.hive.HoodieHiveClient.addPartitionsToTable(HoodieHiveClient.java:143)
	at org.apache.hudi.hive.HiveSyncTool.syncPartitions(HiveSyncTool.java:327)
	... 42 more

1. sample partition path: s3://schema_name/table_name/created=2021/11/10/ -> this will have parquet files as output
2. pertaining using hive style
3. I am converting partition field (created) to string before ingesting/save to hudi table on S3
Environment Description

Hudi version : 0.9.0

Spark version :  2.4/ PySpark

Hadoop version : 2.7.3

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

Look at you table definition

Caused by: java.lang.IllegalArgumentException: Partition key parts [created] does not match with partition values [2019, 01, 17]. Check partition strategy.

It has single partition column created while you partition table by 3 columns  with values: 2019, 01, 17

@mtami

sample partition path: s3://schema_name/table_name/created=2021/11/10/ -> this will have parquet files as output

This is not a valid hive-style partition. You should change it to these for example
s3://schema_name/table_name/created=2021-11-10/ -> this will have parquet files as output

OR

s3://schema_name/table_name/year=2021/month=11/day=10/ -> this will have parquet files as output

@xushiyan thank u. I will try your suggestions and write down here what i got.

Hey @xushiyan
After using created=yyyy-MM-dd, Hudi succeed sync table to hive.
However, I still can't get hudi creating table on Glue data catalog (Hive metastore), Even the Hudi logs is showing the table was successfully created at the hive metastore.
INFO [Thread-6] hive.HiveSyncTool (HiveSyncTool.java:syncSchema(213)): Hive table brand_tree is not found. Creating it
INFO [Thread-6] hive.HoodieHiveClient (HoodieHiveClient.java:updateHiveSQLs(460)): Time taken to execute [CREATE EXTERNAL TABLE IF NOT EXISTS my_schema.brand_tree( _hoodie_commit_time string, _hoodie_commit_seqno string, ... .
Schema sync complete. Syncing partitions for brand_tree
I am not sure if this is related to Hudi or Glue (AWS), if you could direct me where i should look?

@mtami From the logs it showed that hive sync was successful. I suggest you double check the glue table in aws in the desired region for the database you set. It could be permission issue too. Please engage with AWS support to investigate. From Hudi's side, don't see there is an issue so will close this. Feel free to follow up here if you have further info to share. Thanks.

for other who might encounter similar issue, you need specify --enable-glue-datacatalog in the glue job parameter in order to to use the AWS Glue Data Catalog as an Apache Spark Hive metastore. This was not clear from AWS glue job documentation at the first glance.


Fix IE11 text overlapping bug on done pages

Users were reporting a bug on IE11 where the first done page
feedback question was overlapping the related links on the left.
This change fixes it with some new CSS for the legend HTML, and
applies it everywhere. It makes it no worse in Chrome etc., but a
lot better in IE11.

Before:

After:

Trello: https://trello.com/c/sQQiAeyy/309-done-page-ie11-rendering-issue-5

Thanks to @dsingleton for narrowing this down with me and recommending adding width instead of float.

:100:


Modify the HTML template to handle more data

Description

Expand HTML template to account for more profile data
Modify HTML template to account for multiple projects

This lesson took the life out of me... lol


Different binary states for different subspecs of the same pod leads to many problems

target 't' do
    pod 'A/sub1' , :binary => true
    pod 'A/sub2'
end

The preuilt A.framework will contain no sub2 content.
target 't' do
    pod 'A/sub1' , :binary => true
    pod 'A/sub2'
end
target 'p' do
    pod 'A/sub3' , :binary => true
end

It will crash on prebuilt stage of a second pod install.

@leavez any news?


Update 'Add Medication' Form Validation

Fix #277
'Add Medication' does not allow new medicine creation with the same name.

Fix name validation for add and edit; modal header fixed.


Support OT headers

This is a retake on #95. I have:

Rebased it over master
Added interaction tests between ot and jaeger headers (they were not present when the original pr was submitted)
Addressed some of @Tieske 's comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Mast: Watch bustel.net

Mast requests the watch of the watch_keyword bustel\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bustel\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


support for 2021.2

Hi, IDEA has released new version 2021.2 recently. Now It shows FlutterJsonBeanFactory is incompatible. Hope update soon. Thanks a lot!

Very soon. I'm probably expecting to finish by 5pm

https://plugins.jetbrains.com/plugin/11415-flutterjsonbeanfactory/versions
version 4.1.7 has been released

WOW! So quick! Thanks


Add a requirements file (jsonschema is needed for building)

Build script fails on macOS with system python because the jsonschema utility (from the jsonschema package) is not installed by default. Other Unixes may experience similar issues. The package has other dependencies that were removed from the requirements file using pip-chill.

@rbanffy, We have https://github.com/mesosphere/universe/blob/version-3.x/scripts/requirements/requirements.txt. Does that work for you? Let me know and I can close this issue.

Closing this PR since we already have https://github.com/mesosphere/universe/blob/version-3.x/scripts/requirements/requirements.txt
@rbanffy please feel free to ping again if you feel this should be reopened.


v3 regression: Wild card domain resolution appears to fail unlike in v2

What is Happening
I am trying on the v3 betas in https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330
This drops right in the place of my usage of v2 without any additional changes https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/330/diffs#d632a42138acb9bcc35a4d2e3eee040758ab84cc_6_6
And one of my end to end tests is failing https://gitlab.wikimedia.org/repos/releng/cli/-/jobs/69627
Specifically....
A dps service is created in a docker-compose setup with a fixed IP on a dps network and with access to the docker socket
This DNS service is then used by all the contianer in the setup, such as mediawiki-fresh which specifies the dns service by its IP
As part of the test this service tries to resolve default.mediawiki.mwdd, but it fails
[0-0] Error in "Page."before all" hook for "should be previewable @daily""
Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
[0-0] RETRYING in chrome - /tests/selenium/specs/page.js
[0-0] RUNNING in chrome - /tests/selenium/specs/page.js
[0-0] Error in "Page."before all" hook for "should be previewable @daily""
Error: getaddrinfo ENOTFOUND default.mediawiki.mwdd
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:26)
[0-0] FAILED in chrome - /tests/selenium/specs/page.js (1 retries)

The host is correctly resolved outside of a container, but when inside it appears to struggle or fail?
(Though this is perhaps due to the fact I use *.localhost)?
The service that should be resolved to is mediawiki-web, where a VIRTUAL_HOST env var is used.
What is expected
A container that uses DPS as the DNS server should be able to resolve this wild card hostname.

Wildcards were supposed to be working, I will do some tests

Found the cause

Docker container wasn't solving from env when the names weren't separated by , (spaces before and after the comma were needed)

Minimal reproducible example: https://github.com/mageddo/dns-proxy-server/tree/c1dcfe5/examples/wildcards

Github automatically closed the issue, please reopen if the issue persists

It looks like I can confirm that wildcards are now working in my e2e tests using the latest beta.
There is another issue, I'll investigate and try to write a ticket if I figure out what is up.


input variable security_groups is not being utilized

Kafka brokers are only using the default security groups.  Passing in variable security_groups is not being used.
main.tf
`resource "aws_msk_cluster" "default" {
count                  = module.this.enabled ? 1 : 0
cluster_name           = module.this.id
kafka_version          = var.kafka_version
number_of_broker_nodes = var.number_of_broker_nodes
enhanced_monitoring    = var.enhanced_monitoring
broker_node_group_info {
instance_type   = var.broker_instance_type
ebs_volume_size = var.broker_volume_size
client_subnets  = var.subnet_ids
security_groups = aws_security_group.default.*.id
}`
Line "security_groups = aws_security_group.default..id" does not add variable "security_groups".  Maybe replace with "security_groups = concat(aws_security_group.default..id, var.security_groups)"

The security_groups var is used to pass security groups you want to allow ingress into the kafka cluster. It gets utilized in the in the aws_security_group_rule ingress_security_groups.
resource "aws_security_group_rule" "ingress_security_groups" {   count                    = module.this.enabled ? length(var.security_groups) : 0   description              = "Allow inbound traffic from Security Groups"   type                     = "ingress"   from_port                = 0   to_port                  = 65535   protocol                 = "tcp"   source_security_group_id = var.security_groups[count.index]   security_group_id        = join("", aws_security_group.default.*.id) }
I think there is a case to be made for applying additional SGs to the kafka cluster.


perf(lexer): use SIMD char search when parsing numbers

What This PR Does
Use memchr_iter to find and remove underscores when parsing number literals.
I'm seeing some performance improvements when running benchmarks on my machine, but I want confirmation from the CI benchmark job.

Looks like it doesn't help, so I'm closing this PR

The benchmark probably doesn't have any relevant data, assigning @overlookmotel for a quick look.

I can see 3 reasons why this appears to be slightly hurting performance rather than improving it:

Probably a majority of numbers in typical JS source code are short integers e.g. in for (let i = 0; i < 5; i++). Using SIMD will be more costly than just iterating through characters in these common cases.
memchr may be overkill here, because (apart from BigInts), JS numbers can only be a few chars long. memchr is optimized for searching for uncommon needles in large haystacks, but here most commonly you'd have a _ every 3 chars e.g. oneMillion = 1_000_000.
There's likely a cost to initializing a Memchr. It could possibly be speeded up by creating a single finder and reusing it each time, the way the memchr finder for end of multiline comments is here:

https://github.com/oxc-project/oxc/blob/eefb66f75050a54d380d1ff0e18021a778160e55/crates/oxc_parser/src/lexer/mod.rs#L98-L99
But... if we want to optimize this, can I suggest a different approach?
The lexer already iterates through the characters of the source code comprising the number, and deals with _s. At present we do the same check again later, which is unnecessary. We could avoid checking again for _ when converting the number to f64 with something like this:

Add more Kinds e.g. Kind::DecimalWithUnderscores, Kind::BinaryWithUnderscores.
If lexer finds an underscore while lexing the number, it returns Kind::DecimalWithUnderscores instead of Kind::Decimal (in these functions).
Then during conversion to f64, in the majority of cases it'll be a plain Kind::Decimal, and the check for _s can be bypassed entirely.

@DonIsaac What do you think of that approach?
Also, can I ask out of interest: What was your motivation for getting into this? Were you using Oxc on some input with lots of _s in integers, and found it was slow? Or pursuing optimization for optimization's sake? (either way, thank you!)

@overlookmotel Your suggestions look sound. I like the idea of underscore checking during lexing (as per suggestion 2). Since we already need to iterate over numbers there, we could skip the use of memchr entirely.
As for suggestion 1, I like the idea of storing underscore data within the number's Kind, but adding an WithUnderscores variant for each number kind feels verbose to me. What do you think about doing something like using bitflags! for numeric kinds, or some other similar approach?
My motivation for getting into this is that I've spent time optimizing other parts of Oxc before, but never the most important part: the lexer and parser. It's so heavily optimized it's hard to find anything that needs improving. I'm not experiencing any problems with underscores, it's just optimization for optimization's sake 😄

@DonIsaac Thanks for coming back.

just optimization for optimization's sake

A man after my own heart!

adding an WithUnderscores variant for each number kind feels verbose to me

Yes, you're right, it is verbose and unwieldy. But there is a perf advantage to keeping Kind simple (simple to the compiler, not us!). At present it's just a single byte, and that's as tight as you can get performance-wise.
If we added explicit discriminants to Kind enum, we can also make sure there are patterns in the discriminant values so it's actually behaving like a bit flags set under the hood. e.g. make it so that converting any Kind::*WithUnderscores to the corresponding Kind::* is just "subtract 8 from the discriminant".
Personally, my view is that as the lexer is the most primitive level of the stack, and everything else depends on it, it's acceptable to be quite nasty code, as long as it's as fast as possible. But that's just my opinion, feel free to disagree.

It's so heavily optimized it's hard to find anything that needs improving.

I actually see quite a lot of opportunity for further optimization in the lexer. For a start, everywhere we use the Chars iterator, we should iterate over bytes instead. Chars iterator is really slow. #2352 got some heavy perf improvements from doing this (along with other tricks). Secondly, many of the simpler matchers (e.g. when you find a =, is it =, == or ===?) could be made branchless to avoid the penalty of incorrect branch prediction. I had intended to finish off that work on the lexer, and I expect there's another 5% to 10% gain on parser benchmarks there for the taking, but I've got sidetracked to other things.
If by any chance you'd be interested in taking up that baton, I'd be very happy to talk it through with you.

numbers are pretty short, and underscores are rare, so this routine may need to be done differently. Feel free to close the PR again 😅


Add help command

Close #140

Codecov Report

Merging #143 (e09f06c) into master (5cebe08) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #143      +/-   ##
============================================
- Coverage     37.56%   37.52%   -0.05%
  Complexity      407      407
============================================
  Files           120      121       +1
  Lines          2425     2428       +3
  Branches        255      255
============================================
  Hits            911      911
- Misses         1481     1484       +3
  Partials         33       33

Impacted Files
Coverage Δ
Complexity Δ

...a/seedu/budgetbaby/logic/commands/HelpCommand.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...eedu/budgetbaby/logic/parser/BudgetBabyParser.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


fix(client): use iframe document element for transform

Checklist:

[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 main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #45006
It is bizarre that this still works, just because Mozilla have the contentDocument as READ_ONLY.
Nonetheless, nice one working through getting this to work @gikf . I was not able to find a better way to make it work.

Good old magic. I get the preview back.


Syntax highlighting with prismjs doesn't work on deployed site

When I add syntax highlighting via prismjs following the instructions, it works on my local machine with npm run develop but not on my deployed site.

@jmn we have a gatsby module called gatsby-purge-css, this plugin removes css rules which are not used, i think this is not fully compatible with the primsjs module.
We use this particularly because the starter is based on bulma, but we are only using 5% of the css rules bulma has, so we remove them during the build process to save bandwith.
So there's a couple of things you can do to fix this:

on gatsby-config.js file put gatsby-remark-prismjs after gatsby-plugin-purgecss, this way whatever purgecss is doing it's not gonna effect the prismjs styling
on the file mentioned above, substitute 'gatsby-plugin-purgecss' with

{
     resolve: 'gatsby-plugin-purgecss',
      options: {
        develop: true,
        printRejected: true
      },
    }

This will basically let you reproduce the issue in develop mode and will list all the rules which are getting deleted. Once you see which css rules are getting removed you can whitelist them, more details here: https://github.com/anantoghosh/gatsby-plugin-purgecss#whitelist---from-purgecss
The code listed above was something i've learned today, i'm going to add  develop: true to ensure that there's not going to be any difference between npm run develop and npm run build.
If you happen to figure this out please let us know!

Unfortunately gatsby-remark-prismjs is already placed after gatsby-plugin-purgecss in my gatsby-config.js. Not sure how to solve this except disabling gatsby-plugin-purgecss for the moment.

@anantogosh Thank you, printRejected will help figuring out the missing css rules. I've updated today the purgecss plugin to v3 so develop:true should work for future forks, you can run gatsby update gatsby-plugin-purgecss in any other scenario

You are amazing @anantoghosh ! Will add this to the starter soon! Thank you again!


Standardize integration testing

The integration testing for this module should be standardized based on the module template. This should include obviating the need for manual steps beyond running kitchen.

I'd like to do this task after finishing upgrading terraform version to 0.12.0. Thoughts?

@namusyaka I almost done, it PR for TF 11 version will be ready today, so you can change kitchen docker version in Makefile and verify again TF 12
By the way I have issue running kitchen converge against safer-mysql-simple test, have you stuck with following?
`       Error: Error applying plan:
   3 error(s) occurred:

   * module.safer-mysql-db.module.safer_mysql.google_sql_database.default: Resource 'google_sql_database_instance.default' not found for variable 'google_sql_database_instance.default.name'
   * module.safer-mysql-db.module.safer_mysql.random_id.user-password: Resource 'google_sql_database_instance.default' not found for variable 'google_sql_database_instance.default.name'
   * module.safer-mysql-db.module.safer_mysql.google_sql_database_instance.default: settings.0.ip_configuration.0: invalid or unknown key: private_network

`

@kopachevsky I couldn't reproduce the errors. If you can't resolve those errors, please open an issue with more details.


Strange behaviour with INTEGERKEY and DUPSORT

Hello,
I'm experiencing an unexpected behaviuor when using INTEGERKEY along with DUPSORT.
use std::sync::Arc;
use std::fs::{read_dir, create_dir_all};

use lmdb_zero::{Environment, Database, EnvBuilder, DatabaseOptions, open, db, put::Flags, ReadTransaction, WriteTransaction, traits::LmdbResultExt};

pub struct LmdbContext {
    pub env: Arc<Environment>,
    pub db: Arc<Database<'static>>,
}

fn lmdb_db_build_context(path_db: &str) -> LmdbContext {
    let env = Arc::new(unsafe {
        let mut env_builder = EnvBuilder::new().expect("1");
        env_builder.set_mapsize(4_000_000).expect("2");
        // check if dir exists
        if read_dir(path_db).is_err() {
            // create dir
            create_dir_all(path_db).expect("3");
        }
        env_builder.open(path_db, open::Flags::empty(), 0o600).expect("4")
    });

    let db = Arc::new(Database::open(
        Arc::clone(&env),
        None,
        &DatabaseOptions::new(db::DUPSORT | db::INTEGERKEY | db::CREATE)).expect("5"));

    LmdbContext {
        env,
        db,
    }
}

fn main() {
    let context = lmdb_db_build_context("test");

    let txn = WriteTransaction::new(context.env.clone()).expect("1");
    {
        let mut access = txn.access();
        access.put(&context.db, &[1u8], &[1u8], Flags::empty()).expect("2");
        access.put(&context.db, &[2u8], &[2u8], Flags::empty()).expect("3");
        access.put(&context.db, &[2u8], &[3u8], Flags::empty()).expect("4");
    }
    txn.commit().expect("5");

    let txn = ReadTransaction::new(context.env.clone()).expect("6");
    {
        let access = txn.access();
        let mut cursor = txn.cursor(context.db.clone()).expect("7");
        let res1: Option<(&[u8], &[u8])> = cursor.first(&access).to_opt().expect("8");
        println!("First: {:?}", res1);
        let res2: Option<&[u8]> = cursor.last_dup(&access).to_opt().expect("9");
        println!("First::last_dup: {:?}", res2);
        let res3: Option<(&[u8], &[u8])> = cursor.next(&access).to_opt().expect("10");
        println!("Next: {:?}", res3);
        let res4: Option<&[u8]> = cursor.last_dup(&access).to_opt().expect("11");
        println!("Next::last_dup: {:?}", res4);
    }
}

What I expect from this code is
First: Some(([1], [1]))
First::last_dup: Some([1])
Next: Some(([2], [2]))
Next::last_dup: Some([3])

instead I get
First: Some(([1], [1]))
First::last_dup: Some([1])
Next: Some(([2], [2]))
Next::last_dup: Some([2])

Taking out INTEGERKEY it works as expected.

I made some other tests, seems like some Flags combinations are ignored, and obviosly some are invalid.
Some examples:

DUPSORT | INTEGERKEY => works, but DUPSORT is ignored
DUPSORT | INTEGERDUP => works as expected
INTEGERKEY | INTEGERDUP => invalid

Maybe the docs about Flags could be expanded a little

https://docs.rs/lmdb-zero/0.4.4/lmdb_zero/db/constant.INTEGERKEY.html

Keys are binary integers in native byte order, either libc::c_uint or libc::size_t, and will be sorted as such. The keys must all be of the same size.

Using byte arrays with INTEGERKEY isn't generally going to produce reasonable results. I actually didn't think LMDB would have allowed your 1-byte keys since they are not the same size as either of those types and I'm not sure what exactly it is doing with them, though my guess is that they're getting zero-padded to the right. Or maybe it's corrupting the database and the example doesn't do enough for it to notice.

docs

I don't actually know the valid combinations myself — in general, the docs that exist are just copied from the LMDB docs and edited to use rust syntax and lmdb-zero names, plus a simple example illustrating how to use the feature with lmdb-zero.

Yes, I checked also the LMDB docs and there are no valid or invalid combinations listed, as far as I can see.
Anyway I'm closing this issue since it has solved as upstream missing docs.


add in free-courses-hi frameworks like spring boot,spring core,spring…

… mvc,Hibernate,servlet jsp , hosting on aws java
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Provided few more framework courses on java

include all inside java index

add java hindi courses

Resolved Conflict

when you've made changes, please add (changes made) to the title of your PR

all change made

change done

It looks to me like you inadvertently removed good resources while trying to resolve conflicts. when resolving conflicts, please do not undo the work that others have done.

course added in fe15c9c738c82b1d7c032585304ef63c7b6fa15e


Only have a single AsyncLocal for the transaction manager

We use a single AsyncLocal rather than replacing the global value for each
transaction manager. This makes it possible to run multiple transaction
managers in parallel without clearing each others values.

Fixes ScopedTransaction is null

ref https://github.com/Readify/Neo4jClient/issues/300

It also seems to have fixed, or at least drastically reduced, the following:

Neo4j.Driver "The Read method cannot be called when another read operation is pending"

ref https://github.com/neo4j/neo4j-dotnet-driver/issues/329

Neo4j.Driver "A blocking operation was interrupted by a call to WSACancelBlockingCall"

ref https://github.com/neo4j/neo4j-dotnet-driver/issues/329

I'm unsure about the correct behavior in Dispose -- should we really just set the
ScopedTransactions to null? Or should we do some other cleanup?

Btw, after we get Neo4j.Driver to merge https://github.com/neo4j/neo4j-dotnet-driver/pull/328 and with this PR, I'm pretty happy with how this works. We would have to switch to Bolt as the Rest interface still doesn't work well in parallel, but migrating to bolt is a win-win either way.
Thanks for your help so far -- hopefully these changes works for other people too and not just us.

I should note that not everything is fixed. The issue with "A blocking operation was interrupted by a call to WSACancelBlockingCall" still exists, but happens very rarely. I'm able to run 943 tests in parallel tens of times before it happens. When it first happens, every test that follows gets the same exception, even across assemblies, which indicates some corrupted shared state. I have no idea where to start debugging this, and given that I've found two bugs in .NET during this work, I wouldn't exclude more .NET bugs. It might be a bug related to AppDomain again as my testrunner uses the same AppDomain across assemblies, which could explain that the error is replicated through all tests after it first happens.
Anyway, it's way better than the current situation.


feat: allow passing TS config loader options

Summary
Follow up #15190
this will allow us to pass config loader options in a docblock comment.
Currently, valid options are swc and transpileOnly, these options are useful if someone is using ts-node for loading ts config files.

Test plan
Added e2e test

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.6


Page title not assigned the value of doctitle when using Jekyll 3

I've noticed an issue when trying to migrate my blog from Jekyll 2 to Jekyll 3.
To reproduce it I've created sample Jekyll site with jekyll new command and created a sample AsciiDoc page as described in plugin's README.
Assuming my page located at _posts/2015-11-11-page11, I expect to see its title ( extracted from AsciiDoc page title marked with = ) in post list.
But instead I see Page11 as a page title. The same happens when I navigate to the page.
It seems Jekyll or this plugin doesn't  properly set neither post,title nor page.title after update to  Jekyll 3. Using Jekyll 2.5.3 with the latest version of the plugin provides expected result, i.e. Liquid veriables page.title and post.title are populated from AsciiDoc 1st level header.
To overcome the issue it's possible to add :title attribute to the Front Matter of each page, but I'd like to see previous behaviour, i.e. when that attribute was populated based on AsciiDoc document title.
Attached content of the sample project below.
jekyll3.zip

At some point, Jekyll started assigning a default title to posts (using Utils.titleize_slug).
https://github.com/jekyll/jekyll/blob/v3.1.3/lib/jekyll/document.rb#L294-L295
This breaks our logic, which only assigns the title if not already specified.
https://github.com/asciidoctor/jekyll-asciidoc/blob/v1.0.1/lib/jekyll-asciidoc.rb#L120
There are a couple of things we can do.

Assign the title anyway if the AsciiDoc document has a doctitle (we'd need to check first)
Check if the title is equal to title that Jekyll generates (using Utils.titleize_slug). If that's the case, we can assume the title was automatically assigned and we should override it (again, if doctitle is set)
We could monkeypatch Utils.titleize_slug to return null, which would revert the behavior in Jekyll

What do you think we should do?

Thanks for catching this, @eshepelyuk!

Well, I vote for option #1. Thus, AsciiDoctor doctitile, if presents,  takes precedence over one generated by Jekyll. Seems as quite reasonable and expected behaviour.

You are missing one condition of (1). The doctitle will also clobber any title set in the front matter. There's no way we can tell whether the title was auto-generated or specified in the front matter*.
* Unless we use the logic in (2) or we read the source file and parse the front matter ourselves.

As for me it's fine, i.e. ignoring front matter title if one is present in AsciiDoc document itself.
Maybe we should just add a special note about this behaviour into plugin's docs.

Hello
Excuse me for being bothering, but may I ask what are the resolution intentions for this issue ?

Sorry for not replying @eshepelyuk. I had a really busy week and this got pushed back.
I'm kind of torn between (1) and (2). In most cases, (1) is reasonable because it's probably what people use most of the time. However, there are cases where people will want a different page title than document title, and may use the front matter to achieve that (2).
There are other ways to override the title when running under Jekyll. For instance, the author could use a preprocessor conditional to use a different doctitle in the case env-jekyll is set. We could also support the page-title AsciiDoc attribute as a way to override the title.
Given I see at least two ways to achieve an alternate title, I conclude that we should select (1), but only if a document title (level-0 section title) is specified. We'll also support the page-title AsciiDoc attribute as a way to override the title.
Sound reasonable?

Absolutely, thanks for the explanation.

Let me know how that works for you, @eshepelyuk.

Issue is fixed, but there's some strange thing happened after using latest plugin version.
Before, I didn't explicitly declared default layout for my posts, i.e. there were no layout attribute neither in my FrontMatter nor in _config.yml. Somehow, automagically, _layouts/post.html was used for my AsciiDoctor posts.
Now, after upgrade to Jekyll3 and latest plugin version - I have to declare default layout in _config.yml.
It's not a big deal, reporting it jFYI.
Thanks for bug fix, hope net version will be released soon :)

Oops, I made a typo when I refactored. I restored the default layout for posts to "post".

Checked, works as expected :)

Awesome! Thanks for testing!


[snippet] Ability to add snippets from .vscode directory

Ability to add snippets from .vscode directory, instead of %APPDATA%/Roaming/Code/User/snippets.
This would be nice for working with snippets in a specific project, then there is no need to create a snippet extension for private snippets, and install it separately because it's included in the project

+1

Any chance this will be implemented anytime?

Sorry, there are currently no plans. PR are welcome.

+1

+1

close as dupe of #8102 which is younger but more busy.

/duplicate of #8102


Bug in USBTMC transport: else missing

See: https://github.com/glscopeclient/scopehal/blob/e3fb92510a07f40565ba507046d728cdad0deb22/scopehal/SCPITMCTransport.cpp#L198-L207
the else seems to be missing, thus the read() is executed twice which lets the whole thing fail.

I don't have one of the buggy Siglent firmwares handy to know if this is a bug or if it's a workaround for #652.
@mandl can you have a look?

Hello Andrew, he ist right. The else is Missing. Please merge the pull
requests. Thanks for reporting.
Andrew Zonenberg @.***> schrieb am So., 12. März 2023,
12:05:

I don't have one of the buggy Siglent firmwares handy to know if this is a
bug or if it's a workaround for #652
https://github.com/glscopeclient/scopehal/issues/652.
@mandl https://github.com/mandl can you have a look?
—
Reply to this email directly, view it on GitHub
https://github.com/glscopeclient/scopehal/issues/754#issuecomment-1465275534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAER3437C6FYBTVSWHAZAL3W3YUCLANCNFSM6AAAAAAVYI4OPU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add cheatsheets from devhints.io

Website Link: https://devhints.io/
Repository Link: https://github.com/rstacruz/cheatsheets
This repository contains cheatsheet for various libraries which are missing at cheat.sh, for example lodash, backbone.js etc.

Accepted


Hello! @nguyenzung
In my opinion, since the deployment address of SignatureChecker is included during the deployment of FiatTokenV2_2.sol(it can be checked in foundry.toml), it seems we should deploy SignatureChecker as well.
Additionally, when I was modifying the predeploy deployment code, Justin from the smart contract team mentioned that even though it's a library, if it contains public or external functions, it should be deployed!
Thank you😊

@nguyenzung
Oh, I missed something else,,,,(Is it failed to make devnet-up as well to you?,,,)
I will check it after lunch,,, 🥹🙇🏼♂

Hello! @nguyenzung
In my opinion, since the deployment address of SignatureChecker is included during the deployment of FiatTokenV2_2.sol(it can be checked in foundry.toml), it seems we should deploy SignatureChecker as well. Additionally, when I was modifying the predeploy deployment code, Justin from the smart contract team mentioned that even though it's a library, if it contains public or external functions, it should be deployed!
Thank you😊

Thank you!
Let me roll it back. Anw, I am curious about why we should deploy a lib if it contains public or external functions

@nguyenzung Oh, I missed something else,,,,(Is it failed to make devnet-up as well to you?,,,) I will check it after lunch,,, 🥹🙇🏼♂

Thank you very much, Steven
I can start devnet, but when I looked at the PR about USDC, I found that there are things need to be checked more. I am doing it in this PR

https://eip2535diamonds.substack.com/p/the-difference-between-solidity-libraries
I will send you a link for reference !! I don’t know if there will be an answer..!🥹 @nguyenzung

Oh, I'm sorry. I have a question! 🙇🏼♂
@xxeonge @nguyenzung
If I run the make bindings-build, There is some update of usdcBridge's binding files.

Do you know why? And should we update the files? 🙇🏼♂

Oh, I'm sorry. I have a question! 🙇🏼♂ @xxeonge @nguyenzung If I run the make bindings-build, There is some update of usdcBridge's binding files.  Do you know why? And should we update the files? 🙇🏼♂

I think we need to view in assembly to verify it. Let me check

Thank you very much,,,🙇🏻♂🥰🫡

Thank you so much😊
When I tried it, the file didn't change, so I think I need to check with @nguyenzung

Thank you so much😊 When I tried it, the file didn't change, so I think I need to check with @nguyenzung

If you delete forge-artifacts and build again, I think you can see the changes.
After that, if you still can't see the changes, please contact to me.

Thank you so much😊 When I tried it, the file didn't change, so I think I need to check with @nguyenzung

If you delete forge-artifacts and build again, I think you can see the changes. After that, if you still can't see the changes, please contact to me.

I cloned a new main and ran make bindings-build, but the file does not change..! OR-1535-thanos-cannon-update-for-predeploy-contracts as well @rlgns98kr

@xxeonge
Oh, Thank you for your checking. I will check again about the changes,,,🙇🏼♂

Oh, I'm sorry. I have a question! 🙇🏼♂ @xxeonge @nguyenzung If I run the make bindings-build, There is some update of usdcBridge's binding files.  Do you know why? And should we update the files? 🙇🏼♂

I think we need to view in assembly to verify it. Let me check

It seems like the change does not have any meaning.

Line 0x11EC and 0x11ED are located between 2 STOP instructions, and those line does not change storage slot. Maybe the change related to compile config


List Animals in animal-list page

Task depends on #22
Simply list all the animals and link each item to its own page.
Listing can be simple, showing only: id, name, mod_time (unless the UI is already made with more concrete design).
DataTable, Pagination and other presentation features are the object of another task.

Issue is closed as things were done via #22 #32

Issue is closed as things were done via #22 #32


package: Add pre-commit hooks to enforce commit message style

We should do our best to enforce our desired conventional
commit style, especially since PRs may come from the
public.
Semver: minor
Ref: LOG-7183

I think we can add this to everything written on js, right? So, what's stopping us from applying the same thing onto (e.g.) the agent or you have already started doing that?

We will definitely add this across public repositories. I'm just using this as a way for us to feel it out.


[Feature Request] Add free Deploy methid

Heroku is removing free tier option. Use https://render.com/ as an alternative deploy method.

Fly.io also another option


Force to recaptcha verification flow for phone auth in Simulators

In the latest Xcode and macOS versions, APNs is now supported in simulators. Before that, phone auth will always fallback to the recaptcha verification flow.
Since FCM doesn't support iOS 16 simulators yet, https://github.com/firebase/firebase-ios-sdk/issues/9968, this change force the phone auth flow fallback to recaptcha in simulators.

It looks like the integration test Firebase project is in a bad state for the signin tests. Would you fix?

Yeah, it's fixed now.


Add formatting script

This PR adds a bin/format_optivac_output.R script that formats the OptiVac output into a TSV file format like:
| peptide_seq | label |
| ----------- | ----- |
| ALGENSEVV   | e1    |
| MW          | s1,s2 |
| YLAHAIHQV   | e2    |
| MWYWNY      | s2,s3 |
| KIPEQSVLL   | e3    |
| MNW         | s3,s4 |
| RIIGMRTQL   | e4    |

This is mainly to help facilitate downstream analysis.

Withdrawing due to lack of activity


maintainer needs to register for bioc support site

BiocCheck generates this error for clustifyr and clustifyrdatahub:
* Checking for bioc-devel mailing list subscription...
    * NOTE: Cannot determine whether maintainer is subscribed to the
      Bioc-Devel mailing list (requires admin credentials). Subscribe
      here: https://stat.ethz.ch/mailman/listinfo/bioc-devel
* Checking for support site registration...
    * ERROR: Maintainer must register at the support site; visit
      https://support.bioconductor.org/accounts/signup/

@kriemo can you register on the support site?

done, I was registered on another email acct.

Error fixed now:
https://github.com/rnabioco/clustifyr/actions/runs/3412046853/jobs/5699032075


I can setup and use more than one endpoint when deploying

As a Camunda Modeler user
Given:
I model a process and
I use more than one engine, for example at least two.
Then:
I want to setup two different endpoints with separate credentials for the both of the engines.
http://localhost:8080/engine-rest/deployment/create
http://<IP_ADDRESS>:7001/camunda/engine-rest/deployment/create
So that:
I don't need to edit the endpoint on each deploy when switching the engine.
(Maybe I can only select already saved engines from dropdown menu or something like this?)

Makes a lot of sense and fits very well in the general deploy improvements bucket.

Hi @nikku,
I want to bring this topic again to your attention.
Having such feature will help us during testing.
Is there any chance to reconsider it for some of the next Modeler releases?
Best,
Yana

We will reconsider this feature request in our next planning session.

Idea: have a separate place where you can configure and save the endpoints with/without credentials; allow to choose which servers deploy to and remember this config.

Unfortunately, we weren't able to tackle this topic in the current quarter and will also not focus on it in the next quarter due to other priorities.


Refactor binary builder

Remove binary builder code from compilation

@TisVictress whats the reason for this PR being a draft still?

@sophiewigmore I didn't get a chance to add some comments but I split the main file out into internal to make it easier to read. The code still needs to be refactored a bit more to make it more simpler (ie running commands). It now uses the paketo full builders.
The tarballs are not identical to the current output but they are similar but I didn't get a chance to test the latest changes in the buildpack.
The InstallerFactory has methods that match the names of the PHP extensions so the utils can use golang's relect pkg to create installers for each extension. I split the extensions out into separates files as well, one for native modules and the other for Pecl extensions.
Compilation works for jammy and bionic.

The code still needs to be refactored a bit more to make it more simpler (ie running commands).

Are you specifically looking for feedback on that? Or is it in progress?

The tarballs are not identical to the current output but they are similar but I didn't get a chance to test the latest changes in the buildpack.

This is pretty important so we can verify that we haven't changed any behaviour with the new dependencies.

The InstallerFactory has methods that match the names of the PHP extensions so the utils can use golang's relect pkg to create installers for each extension. I split the extensions out into separates files as well, one for native modules and the other for Pecl extensions.

In general the new split has made things clearer, well done.
You have the most context on how the code comes together so I'll defer to you for an answer, but it still feels like there's a lot of duplication. For example, in internal/extension_installer.go, the Pecl extensions all look similar for their functions except Install.
type Redis struct {
	peclExt PeclExtension
}

func (r Redis) DepName() string {
	return r.peclExt.DepName()
}

func (r Redis) DepVersion() string {
	return r.peclExt.DepVersion()
}

func (r Redis) DepSha() string {
	return r.peclExt.DepSha()
}

func (r Redis) URL() string {
	return r.peclExt.URL()
}

func (r Redis) WorkingDir() string {
	return r.peclExt.WorkingDir()
}

Would it be possible to achieve some kind of method override pattern, were PeclExtension type is anonymous inside of each extension type like:
type Redis struct {
	PeclExtension
}

and then, we can use the common PeclExtension methods like URL() and WorkingDir(), but override Install() and any others that are different? I think we could use that same idea for the various "types" of extensions you have here. What do you think?

small nit - I noticed that the dep.tgz.checksum file that gets output doesn't include the algorithm in the file content

Just compiled 8.0.27 (bionic) and 8.1.15 (bionic and jammy) with the code here and put them into the buildpack. The integration tests here fail with:
        [builder] failed to evaluate symlink /layers/paketo-buildpacks_php-dist/php/lib/libgpg-error.so: lstat /layers/paketo-buildpacks_php-dis
t/php/lib/lib: no such file or directory
            [builder] ERROR: failed to build: exit status 1
            ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 51

during the step during the build phase where we try to install (and untar) the dependency.

What do you think?

@sophiewigmore  Each extension type is an Installer and needs to implement the Installer interface. I don't think this can be done with anonymous types because the InstallerFactory expects each type to have a specific set of methods.

Are you specifically looking for feedback on that? Or is it in progress?

Both

@TisVictress have you had a chance to test out these changes in the buildpack? That's how I discovered the failures last time

@TisVictress have you had a chance to test out these changes in the buildpack? That's how I discovered the failures last time

Yes...I used the integration tests and they were green.

@TisVictress btw I was able to compile 8.1.21 on bionic, but 8.2.8 takes a really long time and errors out on my machine. Are you able to do it on your machine?

@TisVictress btw I was able to compile 8.1.21 on bionic, but 8.2.8 takes a really long time and errors out on my machine. Are you able to do it on your machine?

@sophiewigmore No I haven't had any issues. Would you mind trying again?


build: Add workaround for failing yarn check

The yarn check is recently failing on

old webpack (v1, at least v2 is "needed")
bootstrap-switch has peerDependency on bootstrap "^3.1.1" (but<EMAIL_ADDRESS>used)
redux-devtools-extension has peerDep on<EMAIL_ADDRESS>(but<EMAIL_ADDRESS>used)
"patternfly-react#table-resolver#redux@>= 3.0.0 < 4.0.0" doesn't satisfy found match of<EMAIL_ADDRESS>error "patternfly-react#eonasdan-bootstrap-datetimepicker#jquery" not installed
error "patternfly#eonasdan-bootstrap-datetimepicker#jquery" not installed

It's manually verified, that these errors have no effect on recent ovirt-web-ui code base.
But they need to be watched carefully, since they might in the future.

This change is

Related to #636, the new yarn v1.7.0 is more strict in case of yarn check

Is there any particular reason bootstrap >3.3.7 is being used?
patternfly-react and react-bootstrap are both built on bootstrap 3.

No, introduced by #614 .
Looking for comments - I'm fine with downgrading if it makes sense.

@vojtechszocs see above

Why do we need yarn check in builds?

bootstrap should be locked at 3.3.7 for everyone using patternfly

So some of the errors are valuable.  For example, this shows web-ui really needs to upgrade webpack to use those new loaders "properly":
error "babel-loader#webpack@2 || 3 || 4" doesn't satisfy found match of<EMAIL_ADDRESS>error<EMAIL_ADDRESS><5.0.0" doesn't satisfy found match of<EMAIL_ADDRESS>
But some are not valuable.  For example:
warning<EMAIL_ADDRESS>|| ^2.0 || ^3.0" could be deduped from "3.3.1" to<EMAIL_ADDRESS>error "patternfly-react#eonasdan-bootstrap-datetimepicker#jquery" not installed

I suggest using yarn check --integrity in the build.  At least in yarn 1.7, that will check package.json against yarn.lock.  That would keep the check shallow and only error out if someone changed package.json without also committing a new yarn.lock.  It won't look deep in node_modules/, but it won't error on problems deep in patternfly dependencies...

Just noticed - the bootstrap dependency really should be in the dependencies block, not devDependencies.

Why do we need yarn check in builds?

I suggest using yarn check --integrity in the build.

Still makes sense to verify that since failure would point to potential issue with merged PRs. So to double-check.
Recently, the yarn check is called from ovirt-engine-nodejs-modules/setup-env.sh. I think it makes sense to fix it there. @vojtechszocs ?

this shows web-ui really needs to upgrade webpack to use those new loaders "properly":

There's no doubt about that. I had already more-or-less working version of this upgrade, there's bunch of changes needed, it's not straightforward as one would think. I used recent ejected react-create-appas a frame to subsequently re-introduce changes specific for ovirt-web-ui - this approach helped a lot.
Unfortunately, still not everything was finished and I have not enough time to continue on this.
The v1 is not a long-term way for us ...
Anyway, recent webpack v1 is not perfect but I don't observe any real issue with it.

Added commit downgrades bootstrap to 3.3.7 and moves some packages from devDependencies to dependencies

Why do we need yarn check in builds?

Until now, using yarn check was a recommended practice - its purpose was to validate package.json (version ranges of all dependencies) against yarn.lock (version resolutions of all dependencies). In other words, yarn check was supposed to ensure a fully deterministic dependency resolution via the lock file.
It seems that Yarn 1.7.x made yarn check command cover a wider area of potential problems. I'll check this and get back to you.

Recently, the yarn check is called from ovirt-engine-nodejs-modules/setup-env.sh. I think it makes sense to fix it there. @vojtechszocs ?

Normally, for the purpose of RPM build (e.g. when using oVirt Standard CI), ovirt-engine-nodejs-modules should be declared as build-time dependency and the setup-env.sh script should be called during the %prep phase, check this example spec file.
We added yarn check to setup-env.sh script to ensure that dependency resolution check is always performed.

I suggest using yarn check --integrity in the build.

CLI docs on using --integrity flag:

Verifies that versions and hashed value of the package contents in the project’s package.json matches that of yarn’s lock file. This helps to verify that the package dependencies have not been altered.

Notice the "versions and hashed value" part. The --integrity flag should do what yarn check does, plus it should verify checksums (content hashes) of all packages. Therefore, I don't see how using the --integrity flag would solve the problem at hand.

@gregsheremeta @sjd78 I think we have the same issue in current ovirt-engine-dashboard master.
When using Yarn 1.5.1 (reasonably recent):
$ rm -rf ./node_modules && yarn install && yarn check ; echo $?
..
error "patternfly#eonasdan-bootstrap-datetimepicker#jquery" not installed
..
error An unexpected error occurred: "Found 1 errors.".
..
1

When using Yarn 1.7.0 (latest stable):
$ rm -rf ./node_modules && yarn install && yarn check ; echo $?
..
error "patternfly#eonasdan-bootstrap-datetimepicker#jquery" not installed
..
error Found 1 errors.
..
1

Note that in ovirt-engine-yarn package (used by oVirt CI), we upgraded Yarn version from 0.24.4 straight into 1.7.0.

My take:
until patternfly is adjusted, just add this to package.json
"resolutions": {
"bootstrap": "3.3.7",
"jquery": "3.2.1"
}
We didn't have this in our old yarn.
Now the check will succeed and you don't need the "yarn check || /bin/true"

@sjd78 see this comment

—integrity does a light check that verifies that no one touched node_modules after yarn installed it.

Regular check runs Yarn’s resolution mechanism that checks that  the installation tree matches yarn.lock.

The warnings indicate that something is not optimal but installation is
still correct

This diff will fix all the yarn check errors except the webpack one:
diff --git a/package.json b/package.json
index 4b5eb59..c67f4a3 100644
--- a/package.json
+++ b/package.json
@@ -92,9 +92,12 @@
     "react-router-navigation-prompt": "1.6.3",
     "react-test-renderer": "16.4.0",
     "redux": "4.0.0",
-    "redux-devtools-extension": "2.13.2",
     "redux-saga": "0.16.0"
   },
+  "resolutions": {
+    "patternfly/**/jquery": "~3.3.1",
+    "redux": "4.0.0"
+  },
   "scripts": {
     "start": "node scripts/start.js",
     "build": "node scripts/build.js",

@mareklibra - I feel your pain on the webpack upgrade.  With applying optimizations etc on dashboard, took me a few weeks to get webpack v3 all sorted.

@sjd78 , I would keep the redux-devtools-extension in the dependencies. I just briefly verified, it's still working even with the redux 4.0.0 .

Big thank all of you for your help on this.

I would keep the redux-devtools-extension in the dependencies. I just briefly verified, it's still working even with the redux 4.0.0.

I took a look at the extension and I couldn't find where it was used in the code base, but I don't have any particular issue with leaving it there.

Any objection merging this?
@sjd78 , @gregsheremeta , @vojtechszocs , @bond95 ?

@gregsheremeta  @mareklibra -
Keep the jquery version at 3.3.1 and the resolution block is required.
Dropping the version to 3.2.1 allows dropping the jquery entry from the resolution block.
Either way LGTM

@sjd78 , both ways makes sense to me as well.
Anyway, since this hack is potential subject to change in the future, I'm aligning it with the dashboard project.


Implement dq.stack for QArrays and fix mesolve vector_field consequently

Replaces https://github.com/dynamiqs/dynamiqs/pull/630.
The following snippet now passes:
import dynamiqs as dq
import jax.numpy as jnp

H = dq.number(8)
jump_ops = [dq.destroy(8)]
tlist = jnp.linspace(0.0, 1.0, 10)
psi0 = dq.basis(8, 0)
result = dq.mesolve(H, jump_ops, psi0, tlist)


Introduce backend flag to indicate that a deployed project is in an actual production state

We should implement a has SLA / high priority flag that can be set for projects via rill sudo to indicate that a deployed project is actually in production / business critical. This will help us determine which projects require active monitoring from our side so we can build more robust alerting / self-healing without introducing too much noise / signal either. Additionally, this should be emitted as part of log attributes (so we can alert / filter on it).

FYI @begelundmuller @kaspersjo


Cálculo do R_t

Improved inference of time-varying reproduction numbers during infectious disease outbreaks

Wang et. al (2020) - R_t(I,A) mean across points in time period

 Calcular R_0 real


MCO home mh-c421 can't put up or down

Describe the bug
Hello everyone,
I published a post a month ago about configuring mco home modules (https://github.com/zwave-js/node-zwave-js/issues/1401). I added my mh-c421 module and everything seems to be good (just the description which is not perfectly correct it is not a Micro Shutter but a shutter panel ... this is not very important). However, I noticed that it was still not possible to raise or lower the shutter as I wanted (it is always considered as an on / off switch and when I activate it, the shutter goes down but I do not have no option to bring it up ...).
If I use the parameters of the multilevel Switch I have this message:

Since I mentioned them in my old post, there are already some log files and some answers to possible questions.
If the problem is just my home, can you tell me how to fix it?
I remain available for any questions or to give you any file.
thanks a lot for your help
Have good day
Simon

I can't find Node 26 in your other logs. Please just make a new one and post your current cache file (<homeid>.json) here, so the information is not spread through multiple issues.

I can't find Node 26 in your other logs. Please just make a new one and post your current cache file (<homeid>.json) here, so the information is not spread through multiple issues.

Node 23 should be taken from the old post, node 26 is the same, I just excluded my device several times. But if you really want the logs, I can send them to you tomorrow.
Thank you

I have that :
zwave_1 log.txt
It's ok ?
Thank you

No, sorry. See my other comment:

[...] and post your current cache file (<homeid>.json) here

It wouldn't hurt if you also post a log where you re-interview the node. Since it was already queried before, I cannot see much in the logs.

No, sorry. See my other comment:

[...] and post your current cache file (<homeid>.json) here

It wouldn't hurt if you also post a log where you re-interview the node. Since it was already queried before, I cannot see much in the logs.

@AlCalzone,
I have that :
Log.zip
For the "<homeid.json>.json", if it's not in my .zip file please give me the exactely file location.
Thank you for give me your time !

ok and on your side this can still be settled definitively on your side or temporarily?

The PR enables a workaround for the device. That's a bug in the device, not zwave-js.

The PR enables a workaround for the device. That's a bug in the device, not zwave-js.