Update Configuration-Management-Reload.md

CAS 6 standalone didn't reload for my application unless cas.events.track-configuration-modifications=true is added, hence I think this remarks is needed in the doc, thanks.

Thanks for the review! I still think adding this remarks in this section of the doc (instead of making a blog post) is appropriate,
since without the cas.events.track-configuration-modifications=true setting in bootstrap.properties, the auto reload is not working and this behavior is not documented.
How about I put this config inside a blue info box, and put it in the same section, do you think that is good? Thanks!

How about I put this config inside a blue info box, and put it in the same section, do you think that is good? Thanks!

No unfortunately, because that's a manual task that later on needs to be reviewed and managed, in case that property ever goes away, is renamed or moved. Tools would not be able to track and manage it, and someone has to come in and manually make adjustments, effectively undoing your work.
At some point, there will be a much more automated strategy of including settings in different pages of the docs in the way that would not result in duplication or manual work. It will likely happen with the next release after 6.3. For now, a blog post is your best bet, or you can explain the need for configuration adjustment in the plain text and document the behavior for the setting where setting is defined, and do that for the master branch as well.

Ah I get it now, thanks a lot. In that case I will put it in a blog post then. Thanks for your time! I will close the commit now

Sounds good, sure.
To elaborate: what I'd like to do at some point to is turn properties into individual markdown fragments that can be referenced on any page. Jekyll and Github Pages that operate the CAS docs have the ability to allow for include clauses: you define a file as fragment, which allows you to include that fragment on any page. You can pass parameters or input into the fragment and render it based on different events. So you can imagine that we can group different properties together in individual fragments. One fragment could be all properties related to configuration management, or ldap, or MongoDb, etc. Then, one could reference the fragment by its id on any page necessary, without duplicating the individual properties listed on that fragment. They are defined once, and reused everywhere. Doing this should also simplify and remove the need for ${configurationKey}.
As you can imagine, this is a lot of work. Or rather, re-work and reorganize. It it something to focus on in 2021 perhaps, and will gradually happen/improve as the underlying elements with includes and such takes form.

Hi there, I agree with @NgSekLong that this should be documented. Some more remarks if it helps:

For me, it looks like putting cas.events.track-configuration-modifications=true just into a regular CAS properties file should be OK, no need to put it into bootstrap.properties.
In order to work, the monitored file needs to be set by cas.standalone.configurationFile or within cas.standalone.configurationDirectory. The watcher doesn't try to monitor the default application-standalone.properties file, for example.
Yet, even when CasConfigurationWatchService starts monitoring a given file (DEBUG [org.apereo.cas.configuration.CasConfigurationWatchService:65] - <Starting to watch configuration file...), nothing happens on file change. Not sure what I'm still missing. So I still need to call POST /cas/actuator/refresh anyway.

There are also many other important details missing in related documentation pages, but that is for too long to enumerate now. Hopefully it will improve in 2021 together with the other planned changes... :)

I dig around the code, and found something interesting.
cas.events.track-configuration-modifications as suppose to be set as true, for some reason it wasn't being set to true seems like a bug.

private boolean trackConfigurationModifications = true;

https://github.com/apereo/cas/blob/master/api/cas-server-core-api-configuration-model/src/main/java/org/apereo/cas/configuration/model/core/events/EventsProperties.java#L43
I found that, this file containing the check for seems to be misconfigured to not able to receive the true when not set.

 @ConditionalOnProperty(value = "cas.events.track-configuration-modifications", havingValue = "true")

https://github.com/apereo/cas/blob/master/core/cas-server-core-configuration/src/main/java/org/apereo/cas/configuration/config/CasCoreBootstrapStandaloneWatchConfiguration.java#L36
If we change it to have matchIfMissing, actually it can be properties can be reloaded without manually specifying the cas.events.track-configuration-modifications properties.

 @ConditionalOnProperty(prefix = "cas.events", name = "track-configuration-modifications", havingValue = "true", matchIfMissing = true)

I also change it to prefix and name instead of just value since it seems matching for most of CAS 6 settings:
https://github.com/apereo/cas/search?q=havingValue


ADARNN torch CPU only

How can I set to use CPU only If GPU is not available? The error stems from the line 150 in pytorch_adarnn.py
/usr/local/lib/python3.7/site-packages/pyqlib-<IP_ADDRESS>-py3.7-linux-x86_64.egg/qlib/contrib/model/pytorch_adarnn.py in init(self, d_feat, hidden_size, num_layers, dropout, n_epochs, pre_epoch, dw, loss_type, len_seq, len_win, lr, metric, batch_size, early_stop, loss, optimizer, n_splits, GPU, seed, **kwargs)
148
149         self.fitted = False
--> 150         self.model.cuda()
151
152     @property
RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from
https://github.com/microsoft/qlib/blob/main/qlib/contrib/model/pytorch_adarnn.py
self.device = torch.device("cuda:%d" % (GPU) if torch.cuda.is_available() and GPU >= 0 else "cpu")

Thanks for reporting the bug :)
I think replacing all the  .cuda() with .to(self.device) will solve this issue.
You can follow this example.
https://github.com/microsoft/qlib/blob/main/qlib/contrib/model/pytorch_nn.py#L157
Would you mind sending a PR to fix this issue and become one of the contributors of Qlib!
Thanks

@SunsetWolf  will help to solve this issue


Change the position of the panel

Could I change the position of the panel to the left, make it configurable?
Because I'm using a tool-bar button to toggle this project-viewer panel, and I wish they could all go to the edge left.
Here's the screenshot of my atom:

Hi @chuyik, thanks for the feedback. Will make it happen :) well spotted

will make it available soon. :night_with_stars:

@chuyik did this suite your needs?

@jccguimaraes Yes! Thanks for the quick action!

@chuyik no prob!


Align docker and release profiles with the new f-m-p. Remove obsolete…

… references to docker-maven-plugin.

[merge]


[haystack][Backward compatibility] MODEL_TO_ENCODING instead of _MODEL_TO_ENCODING, similarly for MODEL_PREFIX_TO_ENCODING

#Problem
As of today, the haystack python library makes use of the constants "MODEL_TO_ENCODING" and "MODEL_PREFIX_TO_ENCODING" from the tiktoken library and with the tiktoken 0.5.0 version, it breaks.
#Workaround
With haystack, we need to use tiktoken 0.4.0 instead of 0.5.0
#Fix requested
Can we revert the variable name from the following commit?
https://github.com/openai/tiktoken/commit/a7937793e7460ae8e815f506600b7248fad2a803#diff-0d973848bd229418209db2c46c86167000845592ca6b98fad215c21c317bc494
#Steps to repro the issue
Run the haystack tutorial in Google colab with T4 GPU runtime: https://haystack.deepset.ai/tutorials/01_basic_qa_pipeline

This is an implementation detail of tiktoken that is subject to change; can you link me to why haystack needs access to these?

Thanks for the quick response. Unfortunately, I don't have any links on why haystack needs it in their library.
Another update: The haystack tutorial started to work again. Seems haystack is now applying some workarounds on the version of tiktoken. You can close the issue for now.
Colab logs:
Collecting tiktoken**<0.5.0**,>=0.3.2 (from farm-haystack[colab,inference])
Downloading tiktoken-0.4.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.7 MB)
The place where tiktoken is used haystack: https://github.com/deepset-ai/haystack/blob/94c5d6d216cfad5a06484e17614be72a7c2d5af1/haystack/utils/openai_utils.py#L10

Okay, I see. I should add an encoding_name_for_model, in case they're trying to do the lookup without instantiating encodings. I'll add this API later today and revert the constant names so cross compatibility is easier.

Fixed in 0.5.1

Thank you @hauntsaninja for taking care of the issue so quickly! :raised_hands:


OP-1767: Changing drone docker image from buildenv to clarity-build.

This is the last repo using the old buildenv.  This will allow retiring of it.

bors r+


[do-not-merge]Let PP fail

Allows to test antivirus and policies integration without actually using antivirus and policies.
WHATEVER YOU DO: DO NOT MERGE
To test antivirus:

set  POSTPROCESSING_STEPS=virusscan
start ocis
start antivirus with  ocis antivirus server
Now all uploads will be declared infected with a virus

To test policies:

set POSTPROCESSING_STEPS=policies
start ocis
start policies with ocis policies server
Now all uploads will be marked as violating the policies

Server works normal when POSTPROCESSING_STEPS=

Why not making this normal test-steps and name it like pofail and avfail. Could be interresting for admins to see if a step reacts correctly in their setup end-to-end.

That would be much effort for little reward. Imo it would unnecessarily bloat up the code. It would prefer to go for dedicated builds if that must be tested.

Not needed any more


Deprecate NativeSeparatorItem

Make NativeSpacerItem from #134 it's replacement, you would just need to set an empty text.

Change of plans: Separators will now be able to change text.


Issue with opcache and oauth

Just letting you know that there is an issue and its with the PHP7.0+ opcache that breaks oauth which creates the look that on first request works just fine but returns a 500 error ever request after.
I've confirmed the issue in PHP7.1 & 7.2 as well. A quick work around is to disable opcache in php but this isn't advisable for applications that need to scale.
There is an open ticket with php here: https://bugs.php.net/bug.php?id=74030

Interesting.
Any interest in doing a pull request where you turn it off and on before
and after any calls to the class, respectively?
On Sat, Mar 31, 2018 at 10:25 PM Jack<EMAIL_ADDRESS>wrote:

Just letting you know that there is an issue and its with the PHP7.0+
opcache that breaks oauth which creates the look that on first request
works just fine but returns a 500 error ever request after.
I've confirmed the issue in PHP7.1 & 7.2 as well. A quick work around is
to disable opcache in php but this isn't advisable for applications that
need to scale.
There is an open ticket with php here:
https://bugs.php.net/bug.php?id=74030
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/onassar/PHP-TheNounProject/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAlaSu2qPkGIvfrPaQG_8ba7a-n99GNHks5tj_Q4gaJpZM4TCnjb
.

--
—
Oliver Nassar


Rename KE7 variation in the Bongcloud Attack to "Zelensky Defence"

When KE2 is played and black replies with KE7, it should be known as the Zelensky Defence in light of Ukraine president's efforts to fight against russia
FEN: rnbq1bnr/ppppkppp/8/4p3/4P3/8/PPPPKPPP/RNBQ1BNR w - - 2 3

Greatest idea of all times.

Zelenskyy has two ys FYI.

 Also the focus should be the Ukrainian people, not so much their president. Will raise it with the team regardless.

If this variation doesn't work then maybe we can find a more suitable one and if zelensky defence doesn't work maybe ukrainian defence is more suited. I do agree it's a bad opening but strong players like carlsen and gm's can still play very well which could be interpreted by the strong will of the president and the ukrainian people who are still fighting strong even when the odds are heavily against them.
In a philosophical sense the war is bad and it reflects the opening, both sides are in a bad position and are forced to fight

Our initial response with more concrete actions to come, but not this one.


Popper will not set its placement immediate after click

Please check the below GIF, I have used Popper.js latest v.2.x but Popper will not immediately place to its position in the first click, I need to scroll to get it updated...  Below is the code I am using
Am I missing any parameter?
const options = {
strategy: 'fixed',
        placement: 'bottom-start',
        modifiers: [
            {
                name: 'preventOverflow',
                enabled: true,
                options: {
                    escapeWithReference: true,
                },
           {
                name: 'flip',
                options: {
                    enabled: true,
                    fallbackPlacements: ['top', 'bottom'],
                    allowedAutoPlacements: ['top', 'bottom'],
                },
            },
            },
        ],
}
this.popperInstance = createPopper(
                this.dropDownButton.nativeElement as HTMLElement,
                this.dropDownMenu.nativeElement as HTMLElement,
                options
            );

Thank you for your issue.
Unfortunately I can't answer to all the reported issues without a little help from you.
Please, make sure to follow the issues template when you submit a new issue, in this way I will already have all the informations needed to understand the problem and help you with it.
I'm closing this issue for now, but feel free to open a new one making sure to follow all the instructions!
Thank you for your understanding.


tech-conferences-operator to 0.0.9

Promote tech-conferences-operator to version 0.0.9

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Introduce plugin for medline (.nbib) format

Adds plugin for the PubMed MEDLINE format outlined here.
Fixes #21.

ERIC (https://eric.ed.gov/) allows saving search results to the PubMed format (Create a file for use with citation management software, in a MEDLINE/PubMed-style (.nbib) format.) but I just tried a file from ERIC and it wasn't recognized by Rayyan. One difference I see is the absence of the tag "PMID" which I guess is normal.  Here is the file from ERIC:
ERIC2020-07-22_02.45.22.txt

The PMID tag is what we use to detect whether the format is PubMed or not. I guess we can parse the OWN - ERIC line  to support the ERIC format.

Why not "IF PMID ELIF OWN"?
I think it would be sensible to do it as other databases may adapt this format and won't have PMID but would have OWN.

Another case is when using PubMed Central PMC (https://www.ncbi.nlm.nih.gov/pmc/), searches can be save in the MEDLINE format (which is the same as the PubMed format we're supporting here). The file start with something like  "PMC - PMC7370876"  (PMC ID) and in many cases it will have a  second line such as "PMID- 32690910". According to https://www.nlm.nih.gov/bsd/difference.html "Some PMC content, such as book reviews, is not cited in PubMed."
So if we support this case "IF PMC" then we're also covering PMC.


Add autocompletion for "zsh" shell

A problem/task I want to solve
I cannot use autocompletion for elegant-git tool using zsh shell.
The solution I'd like
I would like elegant-git tool autocompletion to work with zsh shell the same as it currently works with bash shell.

@vyahello thank you for the issue. I'm going to make implementation and will notify you once it will be released.

@vyahello implemented in version 0.17.0.


Added PORT fix and created Node.js workflow

Added PORT fix and GitHub action workflow for Node.js

✅ The workflow passed this time so we should be good!


ceph-mon: fix get rbd size hanging

For newly created cluster the command: ceph --cluster {{ cluster }} osd
pool get rbd size does not respond properly.
We only want to check if the rbd pool exists, so we know use an ls |
grep approach.
Closes: https://github.com/ceph/ceph-ansible/issues/1547
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

jenkins test kraken-ansible2.2-purge_docker_cluster

jenkins test kraken-ansible2.2-centos7_cluster

jenkins test kraken-ansible2.2-update_cluster

jenkins test jewel-ansible2.2-update_cluster

I'm unsure why the update tests didn't fire on this PR. I mainly see the issue this is fixing with the kraken-ansible2.2-update_cluster scenario.
The *-update_docker_cluster tests are expected to fail here as those tests aren't merged to master yet.


Failed to load config "plugin:solid/recommended"

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Expected behavior
Screenshots

Desktop (please complete the following information):

OS: MacOS 11

Output of node --version: v14.15.4

Output of npm list eslint-plugin-solid/yarn why eslint-plugin-solid:

Output of npm list eslint/yarn why eslint:

Additional context
Configuration
{
    "parser": "@typescript-eslint/parser",
    "plugins": [
      "solid",
      "prettier"
    ],
    "extends": [
      "eslint:recommended",
      "plugin:solid/recommended"
    ]
 }

Thanks for the report, appreciate you trying it out! I'll look into this later today.

This should be addressed now in 0.1.2! Thanks again for the report.


Update twitter.js

Added support for embeddable tweet
(new line with the permalink of a tweet turns it into an embedded tweet)

@SyntaxRules Would be awesome if you could take a look into this.

@xdamman Would you mind adding a test so that we don't break this functionality in the future?


Connection Multiplier via CLI arg

This adds a command-line argument connections to allow benchmarks to "artificially" multiply database connections (Threads_connected in MySQL) for cases in which it's necessary to have a number of connections that exceeds the practical limitation on concurrency (which is the other way to multiply connections).
This is implemented by managing connections within a struct that contains an array of connection object pointers along with a persistent index into that array.  All the connections in the array are used in round-robin fashion to execute connection methods (currently Execute, Prepare or Close), thus approximating simultaneous use of those connections.
The connections argument requires the concurrency object to be specified, and connections must be a multiple of concurrency.
Also added an argument workermaxrate which specifies the maximum number of events per worker.  If it is specified, it is used along with eventrate to automatically adjust the default value of concurrency.
Also, rather than having a multiplier arg that implicitly sets event rate and concurrency, these have been made explicit:

eventrate arg, default 1000
concurrency arg, by default derived from eventrate and workermaxrate as described above

eventrate, workermaxrate and concurrency are subject to scaling according to the new WorkloadScale field in WorkloadConfig.
A lot of the diff is from a name change in the second commit, so it may be easier to just look at the first commit.

The default value code is a bit messy. Maybe it's better to write in a comment what that method is supposed to do and then write the code according to the comment would make it more understandable?

I agree that it's messy.  I'll try your idea of writing the logic in a comment first.

Also, maybe instead of setting the total connection, why not just set the connection multiplier directly and not have the setting on RateControl.Connection (which gets translated to DatabaseCoinfig.ConnectionMultiplier)?

That would be simpler and more readable in the implementation, although it's maybe a bit less intuitive for the CLI (vs. just specifying the total connections target).  On second thought, that's okay -- it's an "advanced" (or at least specialized) option anyway.  I'll implement the ConnectionMultiplier directly, keeping all the connection trickery in DatabaseConfig, which they can also override in WorkloadConfig by specifying it in DatabaseConfig.


Race condition upon queue flushing for an update

Description
tl;dr
When upgrading to a different version, either there is no way without race conditions to flush the queues (and such a way needs to be created) or there is such a way (and it needs to be documented).
Expected Behaviour
When performing an upgrade that requires flushed queues (e.g. from 1.16.3 to 1.16.4), I can flush the queues without worrying they might be unflushed.
Actual Behaviour
The only documented way to flush queues I could find screams race condition so loudly that people started commenting “RIP headphone users” on unrelated YouTube-Videos.
Steps to Reproduce
This is, of course, only an example, but it was my scenario:

Run Gitea version 1.16.3
Decide to upgrade to a later version and see that this requires flushing the mirror sync queue
Find only gitea manager flush-queues in the documentation
Find out that it can be executed only when Gitea is running
Execute the queue flushing command and race to stop the Gitea instance (essentially gitea manager flush-queues && systemctl stop gitea)
Perform the upgrade
Sit back and acknowledge that what you just did feels really dumb because race conditions you neither know how to check for nor how to correct for should absolutely never be part of your process

Conclusion
So, if there was (for some reason or another) no race condition going on or I could have somehow prevented race conditions from occurring, I would have loved to know about that. As it stands, my best guess is that there was a race condition, there was nothing I could do about it and I got lucky and it caused me no problems. But as queue flushing is presumably here to stay as an occasional upgrade requirement, I'm definitely not satisfied with this state of affairs.
Gitea Version
e.g. 1.16.3 → 1.16.4
How are you running Gitea?
By reading documentation and release notes. :P
Less tongue-in-cheek, from binary via systemd, but this feels relevant to all variants of running Gitea.

Sarcasm is not helpful.
If flushing queues could be done without Gitea running it would be done that way. It cannot and you should be able to work out why.
I wrote a PR that would allow one to interrogate the level db queues #18732 but it has not gained traction.
The logs report if the queues are empty on shutdown.
You only need to have empty queues if you're doing a major upgrade - but even then it's not absolutely necessary most of the time.

Sarcasm is not helpful.

I'm sorry, I did not mean to cause offense. The occasional bit of humour helps me when writing technical texts and I, personally, appreciate it also when reading other's texts but I obviously overstepped what is considered sensible here and will accordingly stop doing this.

If flushing queues could be done without Gitea running it would be done that way. It cannot and you should be able to work out why.

I actually can not work out why. Though since you tell me it is impossible, I'll gladly take your word for it.

I wrote a PR that would allow one to interrogate the level db queues https://github.com/go-gitea/gitea/pull/18732 but it has not gained traction.

That definitely seems like a good doctor command to have and I see it has seen more activity again since you mentioned it.

The logs report if the queues are empty on shutdown.

That is good to hear, but I do have two follow-up questions:

If I do understand you correctly, the following procedure would work to downgrade the impact of the race condition to making “How long does it take to flush queues and shut down?” random as opposed to making “Will the queues be flushed after shutdown?” random.

Execute gitea manager flush-queues && stop gitea
Check logs
If (relevant) queues are empty, exit
Otherwise, start gitea
Go to step (i.)

The question is: Have I understood you correctly?

What is it for which I need to look in the logs? And is it tied to some log-level I would need to configure high enough? I do find these notes distributed among various shutdowns (in my testing so far, at least one of them per shutdown):
...eue/queue_channel.go:98:func1() [W] ChannelQueue: mail-channel Terminated before completed flushing
...eue/queue_channel.go:98:func1() [W] ChannelQueue: notification-service-channel Terminated before completed flushing
...eue/queue_channel.go:98:func1() [W] ChannelQueue: push_update-channel Terminated before completed flushing
...eue/queue_channel.go:98:func1() [W] ChannelQueue: task-channel Terminated before completed flushing

Are these the log items telling me that some queue has not been empty at shut down? Or are there other indicators I have missed?

You only need to have empty queues if you're doing a major upgrade - but even then it's not absolutely necessary most of the time.

As long as the release notes only state “This PR will make old queue entrys unredable for the new version, make sure to flush the mirror sync queue before updating.” without comforting words that I'll easily notice and recover-from not having flushed the queues, I'll definitely sleep easier if I knew instead of hoped the queues to be empty.

The queue code has been completely rewritten. Usually you do not need to do "flush-queues", it's not a well-designed behavior.


CI Test Fixed Round6a

Complete rewrite for test_dashboard_navigation:

Cleaner, simpler test logic
Added state checks/retries for failure prone sections

Thanks @ericsnekbytes!


[Automation] Generate Fluent Lite from Swagger automation#package-2022-02-22

[Automation] Generate Fluent Lite from Swagger automation#package-2022-02-22

API change check
API changes are not detected in this pull request.


[Feature][UI] Create a dynamic task component canvas.

Purpose of the pull request
ref https://github.com/apache/dolphinscheduler/issues/12526

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #12577 (e1979ab) into dev (53340fc) will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #12577      +/-   ##
============================================
+ Coverage     39.05%   39.10%   +0.04%
- Complexity     4175     4191      +16
============================================
  Files          1044     1044
  Lines         39289    39447     +158
  Branches       4501     4530      +29
============================================
+ Hits          15346    15425      +79
- Misses        22208    22270      +62
- Partials       1735     1752      +17

Impacted Files
Coverage Δ

...hinscheduler/api/controller/ProjectController.java
50.00% <0.00%> (-18.43%)
:arrow_down:

...lphinscheduler/api/controller/UsersController.java
55.00% <0.00%> (-3.93%)
:arrow_down:

...er/api/service/impl/TaskDefinitionServiceImpl.java
29.00% <0.00%> (-2.09%)
:arrow_down:

...duler/api/service/impl/WorkerGroupServiceImpl.java
82.20% <0.00%> (-1.87%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
51.19% <0.00%> (-1.20%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
34.74% <0.00%> (-0.12%)
:arrow_down:

...inscheduler/api/service/impl/UsersServiceImpl.java
70.49% <0.00%> (-0.03%)
:arrow_down:

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <0.00%> (ø)

...scheduler/api/service/impl/ProjectServiceImpl.java
62.79% <0.00%> (+1.46%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[build_supp.sh] openmpi: use AOMP instead of LLVM_INSTALL_LOC

This change allows both of the following to work:
AOMP=/COD/LATEST/aomp/llvm AOMP_USE_CCACHE=0 ~/git/aomp20.0/aomp/bin/build_supp.sh
AOMP=/COD/LATEST/trunk AOMP_USE_CCACHE=0 ~/git/aomp20.0/aomp/bin/build_supp_llvm-flang.sh

AOMP should always point to the location that contains 'bin' so that upstream installs work as well as aomp installs.

Closing this PR in favor of an approach Ethan has proposed.


Add pages title

Implements #97, this PR represents an original approach.
About the title format, I propose:
Homepage: ReasonML
Top level pages: {pageName} - ReasonML. Example: Playground - ReasonML
Docs pages: {method} - {nameSpace} - ReasonML. Example: Global - JS - ReasonML.
Please let me know your thoughts.

Since we introduced frontmatter support with #135, i guess this PR will be stale... I will close this for now, feel free to reopen another one if it's still relevant!


[Feature Request] Common ERC20 API

Manual declare ERC20 token ABI
// smart contract functions
var (
	erc20FuncBalanceOf      = w3.MustNewFunc("balanceOf(address)", "uint256")
	erc20FuncCheckAllowance = w3.MustNewFunc("allowance(address owner, address spender)", "uint256")
	erc20FuncApprove        = w3.MustNewFunc("approve(address spender, uint256 value)", "bool")
	erc20FuncTransfer       = w3.MustNewFunc("transfer(address recipient, uint256 amount)", "bool")
)

This would be a welcome community effort!
So far I decided against including ABI functions, because I find it hard to draw the line between what to include, and what not.


Here's the current state of it.
Is there a minimal example of hosting a plugin?
Is GRPC really required for an in-process plugin?
I understand that this repo is mostly geared towards developing plugins with the SDK, not hosting them, so if there's a better place to ask this question, any guidance is appreciated.
Thanks!

Hey I'm really sorry to have missed this until now. I don't think there's an example of minimal hosting. We'd need @kaidaguerre to weigh on the GRPC question. Can you say a bit more about the scenario(s) you envision?

Well, I just find SQL a very nice API for the kind of stuff that steampipe does.
And whereas for exploratory stuff a shell is great, I'm sure being able to use it from within Go, is useful as well.
Now, obviously, if you're using Go you can always drop down to the AWS Go SDK, but again: (1) SQL is nice, and (2) being able to intelligently join across clouds/services with just SQL (!) bridging the gap really feels like a superpower.
Since plugins are Go, I feel that loading them as independent .sos using steampipe-sqlite through mattn/sqlite3 probably adds a lot of friction when compared to just getting to a (mostly?) cgo-free solution that you can just go build?

really feels like a superpower

Indeed it is!


[Bug] No space for escaped bounty

Describe the bug
Lost a duel to a criminal, but when they tried to escape, the division had no space for them. Potential race condition?
Steps to reproduce
Unknown
Message link
https://discord.com/channels/711548456019296289/721311036891725856/880834540795482192
Error Trace
(27/082021-15:21)-[MAIN::ON_MESSAGE]>OverflowError: An unexpected error occured when calling command 'check' with args 'pescal inartu'
Traceback (most recent call last):
  File "/root/New-BountyBot/bot/bot.py", line 588, in on_message
    commandFound = await botCommands.call(command, message, args, accessLevel, isDM=isDM)
  File "/root/New-BountyBot/bot/commandsManager/heirarchicalCommandsDB.py", line 166, in call
    await self.commands[requiredAccess][command].call(message, args, isDM)
  File "/root/New-BountyBot/bot/commandsManager/commandRegistry.py", line 71, in call
    await self.func(message, args if self.forceKeepArgsCasing else args.lower(), isDM)
  File "/root/New-BountyBot/bot/commands/usr_bounties.py", line 246, in cmd_check
    bounty.escape()
  File "/root/New-BountyBot/bot/gameObjects/bounties/bounty.py", line 259, in escape
    self.division.owningDB.addEscapedBounty(self, dbReload=dbReload)
  File "/root/New-BountyBot/bot/databases/bountyDB.py", line 371, in addEscapedBounty
    raise OverflowError(f"Division for the escaped bounty ({bounty.criminal.name}, level {bounty.techLevel}) is full")
OverflowError: Division for the escaped bounty (Oluchi Erland, level 5) is full

should be fixed by https://github.com/GOF2BountyBot/GOF2BountyBot/pull/583


ios compiling resulting in error (uncaught exception (&))

I can compile other projects just fine, but for this one it seems to not work all the sudden. this is the error i get:
Called from ? line 1
Called from CommandLineTools.hx line 1895
Called from CommandLineTools.hx line 22
Called from a C function
Called from CommandLineTools.hx line 126
Called from CommandLineTools.hx line 641
Called from lime/tools/PlatformTarget.hx line 98
Called from IOSPlatform.hx line 649
Uncaught exception - Invalid operation (&)

The line in question:
var image = new Image(null, 0, 0, size.w, size.h, (0xFF << 24) | (project.window.background & 0xFFFFFF));

Looks like project.window.background is null. It's normally allowed to be null, but apparently this code doesn't account for it. We should probably update the code, but for now, the fastest solution is to set a background color.


Incomprehensible sentence

Hello,
please rewrite this sentence: "For complex, large-scale Microsoft Windows Server Active Directory to Azure AD Sync needs such as synchronizing groups over 50,000 and device sync, customers can use Microsoft Entra Connect Sync to meet their needs."
It is not clear as such.
Kind regards,
Anne H., QC

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

ID: 53a27a13-93e8-55cf-f382-cafd97b60700
Version Independent ID: 26c98c27-8363-c663-a271-09c3ac138d33
Content: Solutions to automate identity provisioning to applications - Microsoft Entra
Content Source: docs/architecture/automate-provisioning-to-applications-solutions.md
Service: entra
Sub-service: architecture
GitHub Login: @janicericketts
Microsoft Alias: jricketts

@QueryCoordinator
Thanks for your feedback! We will investigate and update as appropriate.

Edited for clarity in https://github.com/MicrosoftDocs/entra-docs-pr/pull/2441

Hi @janicericketts, when will the update be live and seen on the page?


Usage of UUID VertexIDManager

Hi;
When I try this library with  the GREMLIN_TINKERGRAPH_VERTEX_ID_MANAGER configuration via conf.setProperty(GREMLIN_TINKERGRAPH_VERTEX_ID_MANAGER, TinkerGraph.DefaultIdManager.UUID.name());  it has no effect,
I suppose it is because of the line 702 of https://github.com/ShiftLeftSecurity/tinkergraph-gremlin/blob/master/src/main/java/org/apache/tinkerpop/gremlin/tinkergraph/structure/TinkerGraph.java
In the original implementation this line reads the configuration, you may see here at line 523
https://github.com/apache/tinkerpop/blob/master/tinkergraph-gremlin/src/main/java/org/apache/tinkerpop/gremlin/tinkergraph/structure/TinkerGraph.java
Is there any way to set UUID as VertexIDManager?
Thanks,
Regards.

Your analysis is correct. In the successor of this, overflowdb, there's only long ids, and I kicked out UUIDs along the way, mostly to keep the implementation simple. See https://github.com/ShiftLeftSecurity/tinkergraph-gremlin#successor-notice-overflowdb
You could bring the UUID id manager back in, but you'd have to adapt quite a few places that currently assume long ids. The relevant tests (https://github.com/ShiftLeftSecurity/tinkergraph-gremlin/blob/master/.travis.yml#L15) can guide you. If they pass, I'm happy to merge a PR.


celery services exit with status code 2 on docker compose setup (from master)

Im submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?

🐛

What is the current behavior?

celery services exit with status code 2 on docker compose setup (from master)

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Generate project from master:

Then run:
docker-compose -f local.yml build
docker-compose -f local.yml up

Got these errors:
celerybeat_1    | /entrypoint.sh: line 13: POSTGRES_USER: parameter not set
celeryworker_1  | /entrypoint.sh: line 13: POSTGRES_USER: parameter not set
api_celerybeat_1 exited with code 2
api_celeryworker_1 exited with code 2

Please tell us about your environment:

Using docker, so I guess this shouldn't be a problem?

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Full log just in case:

@jsmedmar seems like the problem is that celery containers are missing envs from .envs/.local/.django and .envs/.local/.postgres files -- try to alter celeryworker and celerybeat from local.yml as follows and restart:
celeryworker:
    <<: *django
    depends_on:
     - postgres
     - redis
    env_file:
      - ./.envs/.local/.django
      - ./.envs/.local/.postgres
      - ./.envs/.production/.celery
    command: /start-celeryworker.sh

  celerybeat:
    <<: *django
    depends_on:
      - postgres
      - redis
    env_file:
      - ./.envs/.local/.django
      - ./.envs/.local/.postgres
      - ./.envs/.production/.celery
    command: /start-celerybeat.sh

hey @webyneter this was exactly the problem! Seems like a quick fix. It only really needed the psql environment:       - ./.envs/.local/.postgres

@jsmedmar nice to hear that, I'll commit the fix later today.

@webyneter, I noticed is better to have all envs in the celery services:
    env_file:
      - ./.envs/.local/.celery
      - ./.envs/.local/.django
      - ./.envs/.local/.postgres


Input Map(joypad): both axis starts with -0.707107 when the joystick is connected.

Godot version
4.0.beta8.official [45cac42c0]
System information
Windows 10
Issue description
I defined move_forward as Joypad Axis 1 - and move_left as Joypad Axis 0 -.
When I run the project both keys starts and keep with the value -0.707107  until these keys are pressed:

Steps to reproduce
Just run the project, with a joystick connected.
Minimal reproduction project
JoystickProblem.zip

Can't reproduce

likely a hardware issue. Try increasing deadzones.

Maybe, I changed the deadzone to 0.1 and 1. Still having the problem. The Input.getActionStrength("move_forward") and Input.getActionStrength("move_left") starts with 1. When I move forward (axis 1) this problem stops, but move_left keeps with 1, so I have to move both axis at least one time to stop this behavior.
Well, since it couldn't be reproduced by another person, I'll close this issue, until it happens to someone else.


transport: authentication handshake failed: read tcp <IP_ADDRESS>:59307-><IP_ADDRESS>:59306: read: connection reset by peer

Hi,
I installed kim builder on an k3s node
➜  bin git:(main) ./kim builder install --selector k3s.io/build=my-builder-node --force
INFO[0000] Applying node-role `builder` to `stackit-containerd-ubuntu`
INFO[0000] Asserting namespace `kube-image`
INFO[0000] Asserting TLS secrets
INFO[0001] Asserting service/endpoints
INFO[0001] Installing builder daemon
INFO[0001] Waiting on builder daemon availability...
INFO[0008] Waiting on builder daemon availability...
INFO[0013] Waiting on builder daemon availability...
INFO[0019] Waiting on builder daemon availability...
```
The pod is running fine:

```
➜  bin git:(main) k get po -n kube-image
NAME            READY   STATUS    RESTARTS   AGE
builder-gl7nv   2/2     Running   0          6m2s
```
But if i try to build an image i get following message:

```
➜  bin git:(main) ./kim build --tag dirien/busybox .
[+] Building 0.0s (0/0)
Error: failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: read tcp <IP_ADDRESS>:59307-><IP_ADDRESS>:59306: read: connection reset by peer"
Usage:
  kim build [OPTIONS] PATH

Aliases:
  build, image build

Any hints?

The connection reset speaks to a crash of the backend service. Can you share the logs for the buildkit and agent containers in the pod? Additionally, please share your client and server architecture, amd64, arm64?

➜  bin git:(main) ./kim build --tag dirien/busybox .
[+] Building 0.0s (0/0)
Error: failed to dial gRPC: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:1234: i/o timeout"
Usage:
  kim build [OPTIONS] PATH

Aliases:
  build, image build

Logs:
➜  ~ k get nodes
NAME                        STATUS   ROLES                          AGE   VERSION
stackit-containerd-ubuntu   Ready    builder,control-plane,master   19m   v1.20.6+k3s1
 ~ kubectl -n kube-image logs ds/builder -c buildkit
time="2021-05-19T06:59:57Z" level=warning msg="using host network as the default"
time="2021-05-19T06:59:57Z" level=info msg="found worker \"sc8350l4a127adn2qw3m1edto\", labels=map[org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:stackit-containerd-ubuntu org.mobyproject.buildkit.worker.snapshotter:overlayfs], platforms=[linux/amd64 linux/386]"
time="2021-05-19T06:59:57Z" level=info msg="found 1 workers, default=\"sc8350l4a127adn2qw3m1edto\""
time="2021-05-19T06:59:57Z" level=warning msg="currently, only the default worker can be used."
time="2021-05-19T06:59:57Z" level=warning msg="TLS is disabled for unix:///run/buildkit/buildkitd.sock"
time="2021-05-19T06:59:57Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
time="2021-05-19T06:59:57Z" level=info msg="running server on [::]:1234"
 ~ kubectl -n kube-image logs ds/builder -c agent
➜  ~

@dirien is this still a problem?


Import DockerController from app data

It would be really handy to be able to import an existing marathon app into MC2.

Looks good. Not too sure about the asserts but we can probably add more error handling when we write the UI views

:+1:


get_network_name fails on windows 10

When I bring up the hosts in vagrant I get an error
[CNYWIT43] C:\projects\DevOps\devenv [feature/get_hyperv_working +5 ~3 -0 !]> vagrant up default
Bringing machine 'default' up with 'hyperv' provider...
[[[ lines removed for brevity ]]]
==> default: Setting hostname...
==> default: Mounting SMB shared folders...
    default: C:/projects/DevOps/devenv => /vagrant
[landrush] Using eth0 (<IP_ADDRESS>)
==> default: [landrush] hostname salt.dev.local does not match the configured TLD: vagrant.test
==> default: [landrush] You will not be able to access salt.dev.local from the host
==> default: [landrush] adding machine entry: salt.dev.local => <IP_ADDRESS>
[landrush] Using eth0 (<IP_ADDRESS>)
C:/Users/jrizzo/.vagrant.d/gems/gems/landrush-1.2.0/lib/landrush/cap/host/windows/configure_visibility_on_host.rb:133:in `get_networ
k_name': undefined method `captures' for nil:NilClass (NoMethodError)
        from C:/Users/jrizzo/.vagrant.d/gems/gems/landrush-1.2.0/lib/landrush/cap/host/windows/configure_visibility_on_host.rb:58:in
 `update_network_adapter'
        from C:/Users/jrizzo/.vagrant.d/gems/gems/landrush-1.2.0/lib/landrush/cap/host/windows/configure_visibility_on_host.rb:15:in
 `configure_visibility_on_host'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/capability_host.rb:111:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/capability_host.rb:111:in `capability'
        from C:/Users/jrizzo/.vagrant.d/gems/gems/landrush-1.2.0/lib/landrush/action/setup.rb:42:in `post_boot_setup'
        from C:/Users/jrizzo/.vagrant.d/gems/gems/landrush-1.2.0/lib/landrush/action/setup.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/providers/hyperv/action/start_instance.rb:12:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/providers/hyperv/action/net_set_mac.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/plugins/providers/hyperv/action/net_set_vlan.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/jrizzo/.vagrant.d/gems/gems/vagrant-hostmanager-1.8.5/lib/vagrant-hostmanager/action/update_all.rb:24:in `call
'

As you can see from the following debug session that the first line is blank.
[15] pry(main)> network_details[0].split(/\n/)
=> ["",
 "Configuration for interface \"vEthernet (DockerNAT)\"",
 "    DHCP enabled:                         No",
 "    IP Address:                           <IP_ADDRESS>",
 "    Subnet Prefix:                        <IP_ADDRESS>/24 (mask <IP_ADDRESS>)",
 "    InterfaceMetric:                      15",
 "    Statically Configured DNS Servers:    None",
 "    Register with which suffix:           Primary only",
 "    Statically Configured WINS Servers:   None"]
[16] pry(main)> network_details[0].split(/\n/)[1]
=> "Configuration for interface \"vEthernet (DockerNAT)\""

I updated the get_network_name method to filter empty lines.
      def get_network_name(ip)
        cmd_out = `netsh interface ip show config`
        network_details = cmd_out.split(/\n\n/).reject(&:empty?).select do |settings|
          begin
            lines = settings.split(/\n/).reject(&:empty?)
            subnet = lines[3]
            next false unless subnet =~ /Subnet Prefix/

            mask = IPAddr.new(subnet.match(%r{.* (\d{1,3}\.\d{1,3}\.\d{1,3}.\d{1,3}/\d{1,3}).*}).captures[0])
            address = IPAddr.new(ip)

            mask.include?(address)
          rescue
            false
          end
        end
        return nil if network_details[0].nil? || network_details[0].empty?
        network_details[0].split(/\n/)[1].match(/Configuration for interface "(.*)"/).captures[0].strip
      end
      end

Merged via pull request #335


Document the steps that an API ML extender needs to take to achieve SSO within Zowe

This the documentation of what an API ML extender needs to take to achieve SSO within Zowe.
It has been reviewed by @janan07 as a part of #937.
Resolves zowe/api-layer#438
Note to reviewers: Do not review or modify unrelated documentation in this PR, please open a new PRs for unrelated changes.
Is there a related issue for this PR?
Issue number: zowe/api-layer#438
Developer's Certificate of Origin (DCO)
Signed-off-by: Petr Plavjanik<EMAIL_ADDRESS>

@janan07 I think it can be merged. But the build fails (PDF could not be generated). Who can help with it?

@janan07 @plavjanik Merging this PR. The PDF failure is might be a Jenkins issue. Looking into that.


[OnlineMeeting&Aug.9]SeaTunnel community meeting Topic collect

CalvinKirs invites you to a meeting on Tencent Meeting
Meeting Topic: SeaTunnel Meeting
Meeting Time: 2022/08/09 20:00-21:00 (GMT+08:00) China Standard Time - Beijing
Click the link to join the meeting or to add it to your meeting list:
https://meeting.tencent.com/dm/GanukiGOWuRG
#TencentMeeting：119-773-151
One tap mobile
+8675536550000,,119773151 (Chinese mainland)
+85230018898,,,2,119773151 (Hong Kong, China)
Dial by your location
+8675536550000 (Chinese mainland)
+85230018898 (Hong Kong, China)
Copy this invitation and open in Tencent Meeting app (V2.13 or later) to join the meeting
if you have any issues wanna discuss, please leave issue number:

[discuss]Connector V2 release.

[synchronization] Progress of synchronization st-engine.

[discuss] How to implement user-defined schema in source connectors

#2383

[synchronization] Progress of synchronization st-engine.

please refer to #2272


Heap-buffer-overflow READ in libspdm_test_responder_chunk_send_ack_case1 test case

Verified on https://github.com/DMTF/libspdm/commit/4c92ff5ced7862e4f2eea945dd723d2e1b1fc476
Ubuntu 20.04.2 LTS

cd libspdm
mkdir build
cd build
cmake -DARCH=x64 -DTOOLCHAIN=LIBFUZZER -DTARGET=Release -DCRYPTO=mbedtls -DGCOV=ON ..
make copy_sample_key
make
cd bin
./test_spdm_responder_chunk_send_ack ./clusterfuzz-testcase-minimized-test_spdm_responder_chunk_send_ack-6712269464469504

The binary seed file to reproduce the issue: clusterfuzz-testcase-minimized-test_spdm_responder_chunk_send_ack-6712269464469504
clusterfuzz-testcase-minimized-test_spdm_responder_chunk_send_ack-6712269464469504.zip

The root cause is test case issue, not the libspdm function code issue.
Heap-buffer-overflow READ occur at line 137 test_spdm_message_header_t->request_response_code, due to we don't check the actual total size of test_spdm_message_header_t before reading its member variables request_response_code.
https://github.com/DMTF/libspdm/blob/4c92ff5ced7862e4f2eea945dd723d2e1b1fc476/unit_test/fuzzing/test_responder/test_spdm_responder_chunk_send_ack/chunk_send_ack.c#L135-L139

After analyzing, the above test code block is redundant in fact, we should remove them.

we have submitted PR to fix this test case issue.
https://github.com/DMTF/libspdm/pull/2647


Request failed with status code 406  Return : Maybe go away?

Environment Data

DeimosC2 Version:
DeimosC2 Build:
Operating System:CentOS7

Expected Behavior
Created Successfully
Actual Behavior
Request failed with status code 406
Steps to Reproduce Behavior
Misc Information

This should be an error when someone tries to create the inital admin after its already been created.
https://github.com/DeimosC2/DeimosC2/blob/9d62925a96b10c2228fd212d95a70f270cb5680d/c2/webserver/webserver.go#L482


SSL Woes? Device prorvisioning failed because this device went offline.

On my Mac, when I launch the Keybase app for the first time and put in my username, I'm given the following message:
There was an error provisioning
Device provisioning failed because this device went offline.
Please check your network connection and try again.

This is almost certainly due to our company gateway swapping out keybase.io's SSL certificate to be one that is trusted our machines (because the company put it there), but not the Keybase software. I found an exchange where a cert was added to the tool with keybase config set proxy_ca_certs <pemfile> ... and I imagine something like this should work for me, but I'm still working at it.
Is there a way to simply disable cert-based authentication entirely? I can't seem to find the option, if one exists. If that is an easy fix and it does solve the problem, what would be the security implications?
Thank you, Keybase & co!

Check out #14307 and the tickets linked from it, you'll get a more complete picture of the troubles with MitM proxies that Keybase is tripping on. If the proxy is resigning the traffic but not otherwise blocking Keybase completely, the above ticket's workaround may work for you. Let me know either way.

I have the same issue, but on Windows 10. Just downloaded Keybase, tried provisioning with QR code from phone. Didn't work. Tried it with typed in secret, get same error as OP. I am on my home network connected via AT&T cable modem.

Same issue I tried multiple times on my iphone and android device.


Occurrences not working correctly for super parameters

Given a file containing
class A {
  A(int x);
}

class B extends A {
  int y;

  B(super.x) : y = x * 2;

  B.x(this.y) : assert(y > 0), super(0);
}

If I select the reference to y in the assert, then that reference, the y in this.y, the y in y = x * 2, and the y in the field declaration are all highlighted. Basically, we've said that the this.y parameter and the field are the same, so any references to either one should all be highlighted at the same time.
On the other hand, if I select the x in super.x, then the field declaration (in A) is highlighted, but the x in x * 2 is not. I think that for consistency it needs to be.

I believe that it already works in DAS, but I will add a test.
https://dart-review.googlesource.com/c/sdk/+/234223
I think it does not work because IntelliJ plugin does not support super-formal parameters yet.
I'm actually not sure if IntelliJ uses AnalysisService.OCCURRENCES.
@jwren

IntelliJ plugin doesn't use AnalysisService.occurrences, but uses navigation for calculating the reference highlighting.
This case works fine
class A {
  int x;
  int y;

  A(this.x) : y = x * 2;
}

because the x in x * 2 targets x in the declaration int x, and not this.x.
However, in the case of
class A {
  A(int x);
}

class B extends A {
  int y;

  B(super.x) : y = x * 2;
}

The x in x * 2 targets super.x, and the latter then targets int x.
I find that targeting int x in the first example, while targeting super.x in the second one is inconsistent, or it least should be cleared before continuing with the IntelliJ part.

I agree that for field formal parameters (the first case) and super formal parameters (the second) navigation is inconsistent. I seems to me that for the super formal parameters it is more correct - x in x * 2 is a reference to the value passed to the constructor (where x is implicitly a final formal parameter). Similarly for the field formal parameter x in x * 2 does not read the field int x - it uses the formal parameter value (also implicitly final formal parameter).

https://dart-review.googlesource.com/c/sdk/+/244863


Enable autocompletion for scriptcs file

Since omnisharp-roslyn has support for scriptcs files, this PR enables autocompletion for csx files.

Works well. Thanks!


Error "Could not find a suitable TLS CA certificate bundle, invalid path" basically breaks VS Code

Getting the following error: Could not find a suitable TLS CA certificate bundle, invalid path: /Users/prodigy/.vscode/extensions/WakaTime.vscode-wakatime-1.1.21/out/wakatime-master/wakatime/packages/certifi/cacert.pem' and it's ruining my vs code - the window is super laggy and other extensions don't work. Screenshot of vscode console
Here's the full output:
{"now": "2018/09/21 12:04:11 -0400", "version": "10.2.3", "plugin": "vscode/1.27.2 vscode-wakatime/1.2.3", "time":<PHONE_NUMBER>.186508, "level": "WARNING", "message": "{'IOError': u'Could not find a suitable TLS CA certificate bundle, invalid path: /Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/certifi/cacert.pem',
'traceback': 'Traceback (most recent call last):\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/api.py\", line 107, in send_heartbeats\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/requests/sessions.py\", line 555, in post\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/requests/sessions.py\", line 508, in request\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/requests/sessions.py\", line 618, in send\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/requests/adapters.py\", line 407, in send\\n
File \"/Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/requests/adapters.py\", line 226, in cert_verify\\n
IOError: Could not find a suitable TLS CA certificate bundle, invalid path: /Users/prodigy/.vscode/extensions/wakatime.vscode-wakatime-1.2.3/out/wakatime-master/wakatime/packages/certifi/cacert.pem\\n'}"}

For me
python -m pip install --upgrade pip --user
and update to pip-19.1.1 helped

I had the same issue, reinstalling didn't help. However, it after removing all .wakatime. files in my user directory (/Users/[username]) and then re-entering the API key it did work again


VPC-SC factory JSON Schemas

As discussed, this only covers the VPC-SC module and does not yet integrate the schemas in FAST.

Generally - ❤ ❤ ❤ - as this may help me a lot in the future and I was bitten by this beast already.
One comment regarding making the schemas a bit more specific - set "additionalProperties" to false on all objects in JSON schema.
The other improvement I see, is to mark more fields as required based on experience (but this may easily explode into big schema, if we need to use "anyOf" or similar approaches).

schema needs to be a 1:1 translation of the variable type :)


Redirection issue using getServerSideProps

Describe the bug
I've encountered a redirection issue when utilizing getServerSideProps on my project. The expected behavior is that visiting "/en/contact" would redirect to "/contact" since I have set the default language to English. However, the redirection fails to occur when getServerSideProps is utilized. When I remove getServerSideProps, the redirection works as expected.
To Reproduce
Steps to reproduce the behavior:

Set up next-translate-routes with English as the default language.
Create a /contact page and implement getServerSideProps.
Visit "/en/contact" in the browser.
Observe that the redirection to "/contact" does not occur.

System information

OS: macOS
Browser: chrome
Version of Next.js: 13.3.1
Version of next-translate-routes: 1.10.2

Yes, you are right.
Unfortunately, this cannot be fixed using next-translate-route approach: trying to use a redirect would lead to a looping redirection.
The only way to do this seems to be using the middleware, as stated here.
I will update next-translate-routes docs to mention it.

Added to the docs here.


Uplift Sol003 driver from version 2.4.1 to 3.5.1 ( LifeCycleManagement Changes)

Some model changes and new model to align with version 3.5.1 of the ETSI SOL003 specification in Lifecycle Management where I there is  no implementation changes.
Issue: https://github.ibm.com/TNC/tnc-o-tracking/issues/3459

Fixes #3459 #44


PR to tide-local repo for updated sync-server

via Derek:
we need to get a PR out to the tide-local repo for the updated sync-server. This will be to update the docker-compose.yml, .env.dist, and README.md with the new environment variables.

https://github.com/wptide/tide-local/pull/8 waiting CR


Fatal Python error: Py_Initialize: unable to load the file system codec

I've compiled vim with
nmake -f Make_mvc.mak CPU=AMD64 GUI=no TERMINAL=yes PYTHON3=C:\Programs\Miniconda3 DYNAMIC_PYTHON3=yes PYTHON3_VER=36 LUA=C:\Programs\LUA\DLL DYNAMIC_LUA=yes LUA_VER=53 IME=yes CSCOPE=yes on Windows(amd64)
And uses Miniconda as a Python Environment.
It's similar to #1550 issue.
And I've tried to use the plugin:
Plug 'cjrh/vim-conda'
When I run vim, it shows

Fatal Python error: Py_Initialize: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'
Current thread 0x0000023c (most recent call first):

And it exited.
I used vim -N -u NONE
When I entered:py3 import sys
It shows

Fatal Python error: Py_Initialize: unable to load the file system codec
ModuleNotFoundError: '
Current thread 0x):

So how to solve the problem?

ModuleNotFoundError: No module named 'encodings'

And do you have that module? In general, I am not sure, we support anything other then the normal python installation for the reasons explained in #1550.

@chrisbra
I have that module.

Python 3.6.2 |Continuum Analytics, Inc.| (default, Jul 20 2017, 12:30:02) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import encodings

And no exceptions appeared.

It seemed like my conda has some problem. I've reinstalled it and it works right.


Open ai api key requests not working

Describe the bug
I'm trying to run this awesome project with my personal Open AI API key, but all requests seem to fail.
Link to the Bolt URL that caused the error
http://localhost:5173/chat/4 (but others failed too before)
Steps to reproduce

Insert valid Open AI api key
pnpm run dev
Promp anything
Request fails

Expected behavior
bolt should generate code
Screen Recording / Screenshot
https://github.com/user-attachments/assets/5c1f7c16-9cf1-4f18-a9f2-6b08742eeb7c

Platform

OS: macOS
Browser: Google Chrome Canary (others fail too)
Version: latest

Additional context
No response

Try to repull the repo. When u start up the dev server reload the page once after first visit. i got a similar error because bolt tries to get the gpt-4o model from Anthropic. after a reload it works for me.

facing the same issue on almost all of the models...

I am having the same issue " * API Key: Not set (will still work id set in .env file):. The OPEN_API_KEY is set, so is Mistral.
Any progress on that?

j'ai exactement le meme probleme idem OPEN AI et ANTHROPIC alors que les clés sont enregistrées dans le .env.local


Collapse input/output from cell menu doesn't work

Testing #122254

open GHI notebook
from the cell context menu select collapse input or collapse output
:bug: nothing happens

https://user-images.githubusercontent.com/1794099/116240294-f17c7b00-a763-11eb-9982-a28f97e9f71c.mov

c32f4d0afd175f090d26530310ffa63090aac810 @mjbvz

Pushed a quick fix but we need a review of actions in the multiselect context. https://github.com/microsoft/vscode/issues/119614
For example this should operate on the selections when invoking it from the toolbar, but only if the toolbar's cell is in the selection, like delete

but only if the toolbar's cell is in the selection, like delete

Set the selection when pressing the toolbar but don't reset multi-select when part of it?

Maybe


fix(debugging): Change order of logging

Change order of logging

:tada: This PR is included in version 1.2.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


example.com URL used instead of a returnUrl / cancelUrl

General information

SDK version: 3.32.1
Environment: sandbox and production
Browser and OS: any

Issue description
Hi Braintree, we experienced an issue where example.com/?token= ... URL was used instead of a valid returnUrl/cancelUrl (see image below, the example.com domain is used as the URL for "Cancel and return to" link). Although in reality while shopping, clicking the link would merely close the Paypal checkout's tab, we still had a customer reaching out that they were redirected to example.com. They claimed it happened after finishing the payment, using iOS. We couldn't reproduce this behavior, but clearly, something is going on with the return URL (open link in New Tab on the "cancel" link is a safe way to see the redirection).

This similar issue shows that createPayment function from your paypal-checkout.js uses dummy values returnUrl:"x",cancelUrl:"x". As is noted also in the other thread, we found it hard to override these values with anything meaningful. Can you please look whether this can be treated to avoid anything going to example.com?

The real solution here is to update PayPal's checkout.js to not require a redirect or cancel url as they are not actually supposed to be used in the flow. Whenever they do occur, that's a bug in the PayPal flow.
I've been lobbying to have these params removed as required parameters, but have had little success so far.

Thank you Blade, I found the related issue https://github.com/paypal/paypal-checkout/issues/562
I will wait for a resolution in that thread, we can close this issue.


Pipeline Pull Request event is firing for all "actions"

Rancher versions: 2.0 master 6/25
Steps to Reproduce:

Create a pipeline with trigger on new PR
Create a PR - pipeline is triggered
Label the PR as a duplicate - pipeline is triggered

Results:  Basically there are many "actions" related to the Pull Request webhook.  It should only fire when on commits for PR (like initial, rename, edit PR)

rancher/rancher:master 9/5
Pipeline is not being triggered for adding/removing labels, editing name, or assigning / un-assigning.


Add JSON to the list of recommended moduleFileExtensions for TS users

Fixes #3282
As the default is moduleFileExtensions: ['js', 'json', 'jsx', 'node'], I think it makes sense to add the ".json". Should we add the "node" -  I've never seen the filetype before?

Codecov Report

Merging #3283 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3283   +/-   ##
=======================================
  Coverage   63.89%   63.89%
=======================================
  Files         176      176
  Lines        6472     6472
  Branches        4        4
=======================================
  Hits         4135     4135
  Misses       2336     2336
  Partials        1        1

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 20f946b...fdaea13. Read the comment docs.


IE11 issue with nextTick

Vue.js version
2.2.1
Steps to reproduce
I'm not exactly sure how to reproduce this error. It started happening when I upgraded to v2.2.1. I downgraded down to 2.1.1 and the issue disappeared. Also, I removed all instances of this.$nextTick in my code, but the issue still persists.
What is actually happening?

which version of vue-resource are you using?

Since the error is coming from vue-resource.common.js, please open this issue at vue-resource's repo, thanks!

I also the same errors without vue.resource.common.js, but when removing vue-resource it seems to work fine. Will open an issue there. Thanks!


NNBD tool suggests casts for map keys

The NNBD migration tool suggests casts for keys to Map.operator[].
This operation has argument type Object?, so these casts are unnecessary, and in this case actually harmful since the code relies on lookups outside the map key type returning null.
Example from sdk/pkg/compiler/js/rewrite_async.dart

An additional problem is that the migration tool will insert as Block without ensuring Block is imported, and does not use the library prefix. Both problems with the inserted cast create broken migrated code.
/cc @stereotype441 @leafpetersen

Which type should be used as the context type when there are both read and write?
Always the index type from operator[]=? Or GLB with the index type from operator[]?
CFE can run this:
class A {
  int operator [](int index) => 0;
  operator []=(num index, int value) {}
}

void f(A a) {
  a[ g() ]++;
}

T g<T>() => 0 as dynamic;

main() {
  f( A() );
}

...and infers int as the type argument for g.
But not this:
class A {
  int operator [](num index) => 0;
  operator []=(int index, int value) {}
}

...reports:
bin/test3.dart:7:6: Error: A value of type 'num' can't be assigned to a variable of type 'int'.
  a[ g() ]++;
     ^

@stereotype441 is going to look at the example from @scheglov , cc @lrhn @munificent @eernstg

In the language specification, a[g()]++ is specified to be treated as (a[g()] += 1) which is again treated as (a1[g1] = a1[g1] + 1) where a1 is a fresh variable bound to the result of evaluating a, and similarly for g1 and g(); so it's essentially treated as let a1 = a, g1 = g() in a1[g1] = a1[g1] + 1.
So this means that there is basically nothing at all to build upon in the language specification for the context type of g(), and we'd need to have a separate rule to specify the context type in this case. Similarly, I don't see any such rule in any other specification document (in particular, in the null safety feature spec and in the inference feature spec).
However, GLB of the relevant formal parameter types of the two members that are invoked ([] and []=) seems to be the obvious choice.
We might want to have a rule to ensure that the two index parameters don't have completely incompatible types, but we don't currently have that, so we would just get a compile-time error for any usage of e1[e2]++ or e1[e2]-- (or pre-increments) in those cases, unless e2 has type dynamic or Never, but we don't have to change anything about that right now.
Cf. https://github.com/dart-lang/language/issues/2271.

Digging through the front end source code, for ordinary indexed reads (e.g. var x = e[i];), compound assignments (e.g. e[i] += v) and if-null assignments (e.g. e[i] ??= v), the context type it uses for the index expression is always the type of the index parameter to operator [].  Whereas for simple assignments (e.g. e[i] = v) it uses the type of the index parameter to operator []=.
Whereas the analyzer, IIRC, always tries to get its context type from the type of the index parameter of operator []=, regardless of whether it's an indexed read, compound assignment, if-null assignment, or simple assignment.  It only looks at the index parameter of operator [] if its lookup of operator []= fails.
As I see it, we have three options worth considering:

Switch the analyzer to match the front end behavior.  On the plus side, this is low effort (since only analyzer needs to be changed) and low risk (it's non-breaking, because any code that would be newly rejected by the change is code that the CFE currently rejects).  On the minus side, there's not really a good principled argument for this approach; it's just what the CFE happens to do right now.
Switch both the analyzer and front end so that they use the type from operator [] for ordinary indexed reads, the type from operator []= for simple assignments, and the GLB for compound and if-null assignments (as @scheglov and @eernstg suggest).  This has the advantage that it's very principled and easy to justify in the spec.  It has the disadvantage that it's potentially breaking (though I suspect breakages will be rare in practice), and since it requires changes both to the CFE and analyzer, it will either require coordination between the teams to roll out the change together, or it will require someone who is familar with both codebases (me perhaps) to change both the CFE and analyzer at the same time.
Do 1 now, and do 2 as a future improvement.  This has the advantage that it quickly solves the migration tool issue, and brings the CFE and analyzer behaviors into line with each other.  It has the disadvantage that it's a little more churn, since it means changing the analyzer behavior twice.

Note that regardless of the approach we take, it's necessary for soundness that we check for assignability between the static type of the index and the type of the index parameter of whatever operator (or operators) might get called.  In both the analyzer and the CFE, the logic to check for assignability is unrelated to the logic for choosing a context type, and as far as I'm aware, there are no bugs with the assignability checking logic.  So we should be able to choose among 1, 2, and 3 without worrying about soundness issues.
Personally I favor option 3 because it solves the worst problems (bad migrations and CFE/analyzer mismatch) quickly and with minimal effort, and it lets us postpone the effort to bring the implementation in line with a more principled spec (which, though important, is higher effort and lower reward than just bringing the analyzer into line with the CFE).

There was also some discussion about whether it would be good to have a lint to warn users when their definitions of operator [] and operator []= have different / incompatible index types.  Personally I don't see a lot of value in doing so, because (a) it's not really a problem unless someone tries to do a compound or if-null assignment, (b) we already have a concrete example of a case where it makes sense to some people for the index types to differ (Map), and (c) I'm not aware of any evidence that people are accidentally giving operator [] and operator []= mismatched index types, and then regretting it later.

There might be some completely different examples that someone can come up with—but conceptually, I would expect any actual design of a class that has an operator [] and an operator []= to have a notion of a 'key' type and a 'value' type, and it would then modify the state to use the given key for operator []=, and it would just search for the key with operator []. This makes the approach taken in Map a canonical one: The key type must be specified precisely for operator []=, but any supertype will do for operator [].
This means that we can expect the GLB of the two types to be, in practice, the type from operator []=.
This means that approach 1 is a bit inconvenient, because it uses the type from operator [] in some cases where []= is also invoked. For example:
class A {
  int operator [](Object? o) => 0; // Expected parameter type: Some supertype of `String`.
  operator []=(String s, int i) {}
}

void f(X Function<X>() whatever, A a) {
  a[whatever()]++; // CFE error, analyzer OK.
}

This actually serves as an argument against approach 1 and 3, and in favor of keeping the analyzer unchanged (such that the current analyzer behavior will not become a breaking change).
Of course, Map operator [] can return null, so we aren't going to have a[b]++ where a is a Map, but in the case where + will work (and in the case where we introduce a magic ! to the increment/decrement expressions ;-), the issue comes up there, too. Other compound assignments bring up the same issue as well.
So maybe we should aim for 2 after all?

We have a subtype restriction between getter return type and setter argument type (I never remember which, but one must be a subtype of the other).
That rule was driven by always wanting to allow this.x = this.x (so it must be getter subtype of setter), and preferably also this.x op= e, where x op e is assumed to be able to have the same type as x.
Using the same reasoning here, a[b] += 1 should be valid, which means that b the return type of operator[] should be a subtype of the type of the second argument of operator[]=.
(On the other hand, that's actually the opposite of what I'd advocate for, if we had started from scratch. It makes no sense to store a value that you cannot read out again. If you can set a num but only get an int, then the setter is not "setting", it's converting and setting, and it should be method instead. In practice, the two should probably just be the same.)
For the first argument, if we assume the two operators are related, it makes no sense to be able to store at a key that you cannot read at again afterwards, so maybe we should require the key of the []= to be a subtype of the key of the []. That matches what Map does, and likely most other well-behaved programs.
It'd be a breaking change, so just using GLB as context type for now is probably fine. Or simply require that at least one of the two is a subtype of the other.
About the desugaring: If the key argument is typed as dynamic, we'll need to do two downcasts, unless one implies the other. Say:
Map<num, num> m = ...l
m[0] += (... as dynamic);
/// equivalent to
let x = ...  as dynamic in m[x as Object?] = m[x as num] + 1

and if so, those downcasts are not governed by the context type. They cannot be.
With a class hierarchy where A and B has multiple possible maximal lower bounds, we may end up choosing a GLB (or none) which is not the actual type of the value, and where the actual type is another a subtype of both key types. So we should not use the GLB for downcasts.
(And never do type inference after expanding syntactic sugar, always do it directly on the original source, precisely because, as @eernstg showed, syntactic desugaring does not preserve context. Just like CPS transformation is precisely about removing syntactic context.)

With a class hierarchy where A and B has multiple possible maximal lower bounds, we may end up choosing a GLB (or none) which is not the actual type of the value, and where the actual type is another a subtype of both key types. So we should not use the GLB for downcasts.

Good point.  If we wind up going with option 2, we should definitely include a language test to check the behavior of this corner case.

That rule was driven by always wanting to allow this.x = this.x (so it must be getter subtype of setter), and preferably also this.x op= e, where x op e is assumed to be able to have the same type as x.
Using the same reasoning here, a[b] += 1 should be valid, which means that b the return type of operator[] should be a subtype of the type of the second argument of operator[]=.

+1. I think the correspondence between getter/setters and index/index setters should be strong. I really wish the language had a formal notion of "property" or maybe "l-value" that would subsume these. It's always confusing for users when a getter and setter don't stay in sync, and likewise with index operators.
It is true that Map's [] operator takes a looser type than []=... but that's arguably a bug and not a feature. It was done for the same reason that Iterable.contains() accepts Object instead of E and that causes so many user bugs that we have a recommended lint to avoid it. We should probably have a similar lint for Map.[].

This issue has come up again, so I think we should take some action to fix it.  After discussing it with @munificent and @leafpetersen last week, I think that in the short term, we should go with my suggestion 1 (switch the analyzer to match the front end behavior).  In other words, for ordinary indexed reads (e.g. var x = e[i];), compound assignments (e.g. e[i] += v) and if-null assignments (e.g. e[i] ??= v), obtain the context type for the index expression from the type of the index parameter to operator [].  For simple assignments (e.g. e[i] = v), obtain the context type for the index expression from the type of the index parameter to operator []=.
In the long term, we can consider changing the context type for indexed reads to use GLB for compound and if-null assignments.
My rationale is: the short term fix is easy and non-breaking, and it gets the migration tool to do the right thing.  The longer term fix is principled and easy to justify in the spec, but it's more effort to implement and it's technically a breaking change, so we should approach it with more caution.
If there are no objections, I'll coordinate with @scheglov later in the week about fixing this in the analyzer, and I'll file a language issue so that we don't forget about the long term plan.

FWIW, I had a fix for this since May, but never uploaded it, and for now it implements GLB.
https://dart-review.googlesource.com/c/sdk/+/256647
I will update it to the plan that Paul recommends.

We talked about this in the language team meeting and we're going to go with the plan I outlined above.  @scheglov, feel free to move ahead with your CL.  I'll file a separate issue to discuss the possibility of using GLB for compound and if-null assignments.

Fixed in d07005b4a23cc5c30a849daf634fea89ca6c1762.


Docs: linkable sections

Split section title and toggle button.

@sagarbehere it was implemented by 954d371.

Confirmed. This is working.


RandomClassProvider doesn't handle constructorless types correctly in all instances

RandomClassProvider has special handling for types like primitives and enums that don't have constructors. However, this special handling is only applied when mapping over direct constructor parameters. This means that constructor-less classes don't get built correctly if they are built under other circumstances, such as when they are included in a collection. For example:
package com.mr.reproducer

import io.github.serpro69.kfaker.Faker
import org.junit.jupiter.api.Test

data class Works(val case : AnEnum)

data class DoesNotWork(val case : List<AnEnum>)

enum class AnEnum {
    FOO,
    BAR
}

class TestCases {

    @Test
    fun `special handling occurs`() {
        Faker().randomProvider.randomClassInstance<Works>()
    }

    @Test
    fun `special handling does not occur`() {
        Faker().randomProvider.randomClassInstance<DoesNotWork>()
    }
}

Although I provide one specific way to reproduce this issue, anything that calls randomClassInstance can hit this bug. I believe this class of error could be handled for all cases by checking for constructorless cases at the top of randomClassInstance, but I haven't studied this question in detail.
If you're open to reviewing a pull request I'd be happy to submit one, but in either case thank you for your work on this project!

Hi @samcgardner ,
Thanks for opening this issue!
Yes, you're correct, the above case is broken. This is because an enum doesn't have a constructor as such, so when an enum is a type of a collection - it will fail, particularly in this part https://github.com/serpro69/kotlin-faker/blob/2a41e3ade343a9a32bd15800ba8944830a958574/core/src/main/kotlin/io/github/serpro69/kfaker/provider/misc/RandomClassProvider.kt#L133-L149
The fix should be pretty simple I think. For example, if no constructors are found, we can check if the receiver is an enum or not, and then call randomEnumOrNull on the receiver.
I'm always open to PRs that fix issues :) If you want do that - please feel free to open a PR. Otherwise I can take a look at fixing this myself. Just let me know how you want to proceed.


Hide Regex needle by feature and enable it by default

I think for people who don't uses Regex, it could be good to not include it as a dependency to decrease a crate size.
[features]
default = ["regex"]
regex = ["regex"]

So it could be used like this.
expectrl = { version = "0.0.1", default-features = false }

It's not possilbe because unix requires it anyway


error with cached_network_image 0.6.1

Because flutter_html_view 0.5.11 depends on cached_network_image ^0.5.0+1 and no versions of flutter_html_view match >0.5.11 <0.6.0, flutter_html_view ^0.5.11 requires cached_network_image ^0.5.0+1.
So, because attendance depends on both cached_network_image ^0.6.1 and flutter_html_view ^0.5.11, version solving failed.
pub get failed (1)

Same problem where.


Contributor can always see their totals during contribution process.

We've gotten lots of feedback that the app annoyingly makes people scroll back and forth to see how much monies they have left to allocate.
We can fix this by scrollfixing a tinier version of the round summary that currently exists to the top of the page when scrolling.
Tiny round summary needs design.

@jonlemmon - what do you think the MVP of this ticket is?

TBH it's pretty hard to say without putting design time in. The only thing
I can think of off the top of my head is a single-column layout.
On Tue, Mar 3, 2015 at 11:17 AM, derekrazo<EMAIL_ADDRESS>wrote:

@jonlemmon https://github.com/jonlemmon - what do you think the MVP of
this ticket is?
—
Reply to this email directly or view it on GitHub
https://github.com/open-app/cobudget/issues/45#issuecomment-76838810.

from Malcolm: "mini feature request: I’d love it if my funds balance stayed visible as I scrolled down the screen."


Pass opts to ws constructor to allow customization

It can be handy to allow users to pass options to ws websockets in node.
The options are not documented but you can find it in the source

Thanks! Released as 4.1.0.
Also, just added you as a collaborator 👍

OK thanks!


Added SortByPrice Functionality | Issue #1689

I have added the sort by price functionality in the Events.
https://github.com/user-attachments/assets/b02393c7-a6ca-4f01-8222-95492983dc7a
Completed #169

@Shariq2003 fix this broo

@Shariq2003 fix this broo

Yes @TejasNasre sir, I will definitely fix this, I am currently in college

Will fix this asap after college off

@TejasNasre sir, please check again

fix it ser

@TejasNasre Build compile successfully on Local, please check on Vercel now

@TejasNasre please check deployment its fine now,
Please merge this.

change branch to dev i will merge

change branch to dev i will merge

okay


check if http server support range request

I used to use python -m  http.server 80 to test databend copy into (so don`t have to start minio) .
seems it not support Range_requests.
obj.range_reader read from start and did not report error, which lead to unexpected behavior.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests

python's HTTP server doesn't support the range header. Even worse, it will ignore the range header without returning an error. OpenDAL can't detect it in a zero abstraction way.
I think the better solution is to not use the python HTTP server for testing...
Please take a look at https://github.com/datafuselabs/databend/pull/8431


not ever CSV-file is separated by commas...

Hello, in our data-files we typically cannot use commas nor semi-colons for delimiters, because they feature as part of our data.
So I am using a private delimiter. (If you are curious, I am using '#' but that does not matter).
So I have manually enhanced the code like this, to allow me to set my personal delimiter:
def getCsvData(self, csvfile):
    # Read CSV file and return  2-dimensional list containing the data
    reader = csv.reader(file(csvfile), delimiter='#') # set your personal delimiter in this line
    result = []
    for row in reader:
        rowlist = []
        for col in row:
            rowlist.append(col)
        result.append(rowlist)
    return result

I hope to write a version, where the GUI will ask the user, what delimiter he wants to use (while proposing the good ole comma)
Please integrate the choice of delimiter into the script, if you like the idea (because it took me a long time to read the script and find the command csv.reader and to look up the syntax re delimiter...
greetings and good job,
Martin Zaske

will integrate in next refactoring with command line support. thanks for the report.


Fix overlapping auto-generated ticks

It was reported in https://github.com/chartjs/Chart.js/issues/6109 that the time scale sometimes generates overlapping ticks. @kurkle debugged this and determined in https://github.com/chartjs/Chart.js/pull/6115 that the issue is because the time scale's auto-tick generation doesn't consider padding.
We'd like to take most of the intelligence out of the time scale's auto tick generation and instead generate a tick at every point and use the auto-skipper to automatically decide which ticks to display. For more details see https://github.com/chartjs/Chart.js/issues/4612
While the solution proposed in https://github.com/chartjs/Chart.js/pull/6115 fixes the bug it also adds more logic to the time scale which is not quite going in the direction we'd like to take things longer-term. This PR may seem a bit funny standalone because when ticks.source: 'auto' we're auto-generating ticks and then checking to see if we have too many and autoskipping some of them as well. We shouldn't really have two auto-tick logics. I have a branch on my machine locally that moves much of the time scale's auto-generation logic to the auto-skipper so that everything is contained there. The change in this PR is both necessary for that longer term solution and also in the short-term fixes the bug reported in https://github.com/chartjs/Chart.js/issues/6109
Closes https://github.com/chartjs/Chart.js/issues/6109 https://github.com/chartjs/Chart.js/pull/6115

Thanks for taking a look @kurkle. I'm happy to discuss more on Slack if this ends up getting too complicated for GitHub issues. But either way is fine with me

I don't think its good practice to override option based on another option.

In general, I agree. I think this case might be a bit different because we've essentially decided that we don't like the way one of these features is built so we're going to replace it and turn on the other feature,  which offers essentially equivalent functionality, to maintain backwards compatibility

Using autoSkip to fix bad tick generation is even further away from fixing the actual issue than #6115.

It depends what you think the actual issue is. I'm guessing we saw different things as being the root issue. I think the issue is that tick generation has to care about the scale size.  What I'm suggesting is to start going in that direction now rather than making the tick generation care even more about the scale dimensions

I think long term goal is also to move autoSkip to update. I suppose this same issue would arise even with autoSkip enabled then.

It's something I've suggested in the past, but I'm not entirely sure whether it aligns with my current thinking, which is still evolving. Another possibility is that update just generates the ticks independent of scale size and then _autoSkip is called after the scale dimensions are calculated and handles showing only the ones that fit. The other thing that could be beneficial as well is to stop calling update twice and call fit instead. This would align very well with making update not care about scale size

I don't think the underlying issue (width/height not being at their final values when ticks are generated) can be fixed without breaking changes.

I think that making tick generation independent of width/height and then calling _autoSkip after width/height has been calculated would be both simpler than what happens now and backwards compatible

I've been doing some profiling and I think that the solution that we had been talking about for improving auto-skip does not scale well enough, so I'll close this for now and approve the other PR for the time being


Restage of Application

A user should be able to restage or restart an application through the UI.

The staging API endpoint needs A BlobUID  to use when staging. The cli has that information from the previous call which uploads the code.
I understand this may not be possible in every flow, especially from the web UI. Maybe we can make that optional and use the last uploaded blob when the BlobUID is missing. Would that work for you?
Regarding "restart", we could either tweak the "Deploy" endpoint to not require a Stage or we can simply implement a new "Restart" endpoint.

@jimmykarily I missed this one from planning earlier, it has a dependency on https://github.com/epinio/epinio/issues/912 and you asked a question in your last comment that I'd defer to @agracey. I don't think it's a blocker for beta2 so have bumped out to 'later'

@jimmykarily Now that https://github.com/epinio/epinio/issues/912 has been completed, is https://github.com/epinio/ui/issues/10#issuecomment-946827905 now ready too or unblocked? If the later was there an epinio/epinio issue to track progress?

@richard-cox there was no issue I think but since we have an org-level board now, I will simply add this story to the backlog.

Created 2 stories:

Restage endpoint: https://github.com/epinio/epinio/issues/1073
Restart endpoint: https://github.com/epinio/epinio/issues/1074

I've now wired these two in and the feature will be included in the pending ui 0.3.3 release


Responsibility of Testing Schemes regarding quarantine

To be allowed to enter a (new) location, ALL testing schemes have to allow a person to go there. Since quarantine is handled by the MigrationRules, if you would call run_strategy twice, and there is no testing scheme with minimal time = 0, then it could actually change the result from the first call. Calling it twice in a row thus has to be avoided. Right now, this is fine since run_strategy is only ever called once for each location (where quarantine has already be checked for in the MigrationRules).

To add something to the discussion: In general, it is a good that the testing schemes are not responsible for the quarantine checks but only for testing and evaluating testing results. Thus, it could be enough to update the description of the return type of run_scheme to account for this fact.

The important part here is that currently no-one is released from quarantine, because the movement rules don't call the testing strategy (and therefore the tests) when a person is in quarantine. We need a mechanism that removes the quarantine somehow. This could be after a time or/and after a test is performed that was negative.
The handling of quarantine may not always be the same, depending on government and the type of virus. However, I propose that we go for a "freitesten" approach for now. So one could say that after a person enters quarantine, daily antigen tests are conducted and when there is a negativ one, a PCR follows to confirm and then remove the quarantine if it's negative.
The work in #866 should be taken into account and compared with, as it adds delays in testing.

Quick notes for me to discuss:

This probably makes things more complicated, but should we even have m_minimal_time_since_last_test ? in accordance to #866 there we already save the validity of a test and then can check for that`(if e.g. tests match -> automatically pass)? Con: this would prob lead to performance problems and we need time_since last test anyway.
In NRW we had 10 days for not testing, e.g. automatically cancel quarantine after 10 days.
After 5 days one could free themselves from quarantine with a PCR and normal test (side thiught: maybe differentiate between self etsting and official testing...)  as both tests had to be official, i would go for the PCR test right now

Quick fix in respect to time: we just set qurantine as fals after 5 days
sidenote: time_since_last_test to be set after set to 0


Share count for google plus

All of the articles I read either require an API key or a web scraper. I'm gonna go with the web scraper.
http://blog.sriraman.in/url-share-count-facebook-twitter/
Scape this url https://plusone.google.com/_/+1/fastbutton?url= and look for '#aggregateCount'

Is that going to be brittle down the line, though? It might be worth allowing for the API route if an env var with an API key exists and then falling back if one doesn't.

Actually, the google plus scraper is not a great idea. The button doesn't give an accurate number of shares. For example, this is what is returned.

1k

Yeah. I'd say just look for an API key for it somewhere. Environment variable, config file, etc.

Did some research. Brace yourself.
I got an google API key and followed the docs here. Didn't work. Their API is private. http://stackoverflow.com/questions/28203030/google-plus-api-count-call-failing
I found a russian website that will hook us up with the counts. Everyone seems to be using it.
http://jsfiddle.net/4gvghj51/
Current scraper method.
http://stackoverflow.com/a/15449276/5270126
Outrage from the rest of the community because there's still no API.
https://code.google.com/p/google-plus-platform/issues/detail?id=57

FOR MOTHER RUSSIA

Everything is broken including http://jsfiddle.net/4gvghj51/
This is also broken.
http://stackoverflow.com/questions/29016599/get-google-plus-url-share-count


fix(curriculum): Wrapped up CSS properties within the code element

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #57091

Hi @Swapnilyende5 . Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝

You're very welcome! I'm glad the changes were well-received, and I'm excited to continue contributing. Thank you for the opportunity and support! 😊


Newsroom Displayed in place of "Dashboard" when in Dashboard

Up at the top, the dashboard button should change to "Newsroom" and allow them to check out the newsroom from the Dashboard.

I'm going to take a stab at this.

Looks like you got it!


[FEATURE REQUEST] .select()

Is there a way or plan to do something like Model.select('name','email').exec... and only get name and email columns? Of course something like Model.select('name').populate('model2').exec would return only name and model2 data.
and only certain attributes for related models like Model.select('name').populate('model2',{select:['other','info']}).exec... would be nice. =)

Closing this as duplicate of #73 (PR #952).


[WIP] After setup error, do klog.Error not klog.Fatal, and move on

When an error happens during a setup step, instead of calling klog.Fatal which causes os.Exit, instead do klog.Error, break, run defer function with clean up steps, and return.

What type of PR is this?
/kind bug

What this PR does / why we need it:
I found this line to be the problem as to why our KinD cluster deletion was not happening as intended. As soon as an error value is passed during a setup step, klog.Fatalf(...) is called:
for _, setup := range setups {
    // context passed down to each setup
    if e.ctx, err = setup.run(e.ctx, e.cfg); err != nil {
        klog.Fatalf("%s failure: %s", setup.role, err)
   }
}

According to klog docs,

// Fatal logs to the FATAL, ERROR, WARNING, and INFO logs,
// prints stack trace(s), then calls OsExit(255).

To reiterate, klog.Fatal is stopping all operations and exiting program with os.Exit. This is not the behavior I want. What I want to happen is for the setup range loop to stop trying to do the setup steps, and try to get to the function return, return m.Run(). However, before returning, I expect the defer block to run next where the finishing steps, like cluster cleanup, happen.
Which issue(s) this PR fixes:

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

Gracefully exit when setup fails

Additional documentation e.g., Usage docs, etc.:

I'm thinking about how to write a test that ensures finish/clean up steps happen after setup step fails. This PR will be a WIP until I can get some tests up.

@codegold79 apologies for the delay.
let me know if this ready for another round of review.

Thanks, @vladimirvivien! I responded to your first review comment and tried to explain why I had to make a separate example and use TestMain.
As for your second review comment, I made the change as you suggested. I also got rid of the dummy test. as it doesn't help anything except to not trigger a warning that there are no tests. The thing is, I'm not testing any features, I'm making sure the final actions complete even after a panic in the setup, before any feature tests happen.
PR is ready for review again.

@codegold79 (apologies for the late reply)
I did spend sometimes to see if this can be tested using a normal test function and I think you are doing the right thing.
/lgtm

Hi @codegold79 can you please squash commits. Thanks.


Add ".env" to Laravel.gitignore

Laravel 5 uses vlucas/phpdotenv for env configuration.
http://laravel.com/docs/5.0/configuration#environment-configuration
Laravel 4 used env.php files.
The new configuration files do not have ".php" extensions
Pull req  #1380 addressed this, but included other things.
Fixes #1380.

Thanks!


[NEW] Night Mode For app

Description

Add night mode for the app.

Good idea, although under Android there is generally the possibility to activate night light.

Duplicates #975