pg library seems to be part of source code

Hi, I Just noticed I got a badge from this, even though we've never collaborated or been in contact.
This looks like it wholesale brings in brianc/node-postgres library in a very strange way (commits, rather than using package.json).
Not only is this a development burden (you'll need to manage backports etc), but it's not exactly clear what this does differently, in a good way, with commits such as: (totally ignoring bizare renaming of ssl to tls, changing copyright notices etc)

https://github.com/vertica/vertica-nodejs/commit/0db0b33c2a21ba30f8849f1c00485460ba33f2d8
https://github.com/vertica/vertica-nodejs/commit/9999867c8be146a8917da06e0580162918f9caa1

What is this, if not a nodeJS postgres library?

Vertica in it's beginning was a postgres derived database. It has since branched off enough that a client designed for postgres will not be compatible. Similarly, as you noticed, vertica-nodejs is node-postgres derived. It was originally a node-postgres fork but for visibility reasons was moved to a new repository duplicated and brought in through commits. So is it a nodeJS postgres library? Well, not anymore. I don't know how github badges work, but I assume it would have to be based on commit history. It may be that removing the commit history associated with node-postgres will resolve the issue. I can look into this. Apologies for any inconvenience.


Grant for microsoft graph application permissions using admin consent v2 end point?

I am working in Azure Application registration process to grant application permissions using V2 end point. I did following steps to do that.

I have added "Mail.Read" as an application permission to the azure app

I have used following URL to give admin consent with specified scope as "Mail.Read".
https://login.microsoftonline.com/ff63ebda-8bfe-4e14-aba1-504db5c53970/v2.0/adminconsent ?client_id=34dbd899-c9fa-415f-8646-28c644baf3ec &scope=https://graph.microsoft.com/Mail.Read &redirect_uri=https://google.com &state=12345

I accept the requested permission without an issue.

I checked the given permission after accepting and Mail.Read permission is added as "Delegated Permission" which is not the expected behavior.

Then I tried to give consent using default scope(https://graph.microsoft.com/.default).
https://login.microsoftonline.com/ff63ebda-8bfe-4e14-aba1-504db5c53970/v2.0/adminconsent ?client_id=34dbd899-c9fa-415f-8646-28c644baf3ec &scope=https://graph.microsoft.com/.default &redirect_uri=https://google.com &state=12345

I accept the permissions successfully.

Then permission is added as application permission which is the expected behavior.

My requirement is to use admin consent v2 end point with specified scopes to grant application permissions. I need to know what is the possible way of doing that using admin consent v2 end point.

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

ID: 0e056c00-a2a1-7019-fb36-0243819a7b99
Version Independent ID: a7a0b942-5e83-6e60-c9e8-32e0225de250
Content: Microsoft identity platform scopes, permissions, & consent
Content Source: articles/active-directory/develop/v2-permissions-and-consent.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@piyumi25 Thank you for your query . We will try to find answers for your query however we use azure-docs repository specifically for improvements in the documentation . I would suggest to open a thread on Microsoft QnA in future where we have a vibrant community who can help you with the same.

@piyumi25 I have posted an answer to your question here: https://docs.microsoft.com/en-us/answers/questions/431784/how-to-grant-application-permissions-with-dynamic.html?childToView=432040#answer-432040


Fix extracting pid form bpf_get_current_pid_tgid()

Based on Issue #35,
pid must be extracted from the return value by using an and operation with 0xFFFFFFFF.

Why? The documentation tells us:

Returns the process ID in the lower 32 bits (kernel's view of the PID, which in user space is usually presented as the thread ID), and the thread group ID in the upper 32 bits (what user space often thinks of as the PID). By directly setting this to a u32, we discard the upper 32 bits.

Therefore the current code seems to be correct.

I agree, The documentation states that PID is stored in the lower 32 bits. However the code actually throws away the lower 32 bits as in the line of code below:
data.pid = bpf_get_current_pid_tgid() >> 32;
If we insist on shifting the result to get the PID we might use something like this:
data.pid = (bpf_get_current_pid_tgid() << 32) >> 32;
Besides, the book refers to the higher 32 bits as PID as I mentioned in #35 and the current code would be correct if that was the case.

Thanks for this @AliJavidiCS.  Per the comments in #35 I think the code is actually correct here, though the footnote needs a better explanation!


Updated HMC implementation for new AHMC version

This PR makes Turing.jl compatible with the AdvancedHMC.jl's master branch, which will soon become a new release.

@torfjelde It seems that the CI time increased due to some recent PRs, which leads to more often timeouts. Maybe splitting the Turing-CI workflow into two workflows to resolve the time limits of a single workflow?

@torfjelde It seems that the CI time increased due to some recent PRs, which leads to more often timeouts. Maybe splitting the Turing-CI workflow into two workflows to resolve the time limits of a single workflow?

Am fully aware; been trying to fix it for a couple of days now. I'm also not certain it's due to any of the recent PRs; it might be some other dependencies that slow things down.

E.g. integration tests in DPPL passed within an hour in our last PR-merge just 3 days ago: https://github.com/TuringLang/DynamicPPL.jl/actions/runs/1031412449. Then it suddenly started timing out without any changes made to master: https://github.com/TuringLang/DynamicPPL.jl/actions/runs/1034731795.

Uhhh I have no idea why but it seems like https://github.com/JuliaStats/Distributions.jl/pull/1362 is causing the freeze. I noticed it would halt when testing
https://github.com/TuringLang/Turing.jl/blob/d02919825f816712cd61bad31f3b720464d4612f/test/test_utils/models.jl#L73-L77
for ESS sampler. Removing this and everything runs as per usual, it seems.

Uhhh I have no idea why but it seems like JuliaStats/Distributions.jl#1362 is causing the freeze. I noticed it would halt when testing

cc @devmotion

David is one vacation so not sure he'll respond :confused:
Also, instead look at #1663 where I've added some more info.
Should we maybe upper-bound Turing.jl to<EMAIL_ADDRESS>too, rather than just the tests? Worried peoples code might be running into similar scenarios (though I still don't understand why it fails).

Should we maybe upper-bound Turing.jl to<EMAIL_ADDRESS>too, rather than just the tests? Worried peoples code might be running into similar scenarios (though I still don't understand why it fails).

Happy to upper-bound Distributions before we figure out why CI times out.


Chapter 15: a virtual machine

Inch through chapter 15 building a stack-based virtual machine.
Includes challenge 3, an extensible stack with underflow and
overflow detection.

Updated to include top-of-stack cache in the VM bytecode interpreter.
Interesting. In JLox, there was a "throw error on divide-by-zero" challenge
that is not repeated in CLox. I think I'll implement it.

Decided to disallow divide by zero, or any computation that
results in NaN or Inf values.


 I can log out, delete my browser cache but nothing helps. Even restarting the server does not help. I am lost.

@FinnStutzenstein FinnStutzenstein added a commit to FinnStutzenstein/OpenSlides that referenced this issue 7 hours ago

I tried this fix but this does not help me, also not with a new database. As soon as I press identify, I can no longer project anything.

@emanuelschuetze please verify this. I do not know why this didn't work without the fix. When creating the message and countdown PR this was working perfectly..?

With current master (which includes now the pr #2529) the identify feature works as expected: after some seconds the identify messages are removed.
@donovaly Please retest with next test version.

after some seconds the identify messages are removed.
@donovaly Please retest with next test version.

But now nothing happens. There is no identify message shown anymore.

@emanuelschuetze closed with PR #2663

Thanks, this is now fixed as I wanted.


RoBERTa + RACE accuracy might be wrongly calculated

Hi, I have a question for RoBERTa authors. When I tried to evaluate RoBERTa on RACE dataset, I met the same problem as #1534 #1181 I am able to reproduce the official result with the following script:
MAX_EPOCH=5           # Number of training epochs.
LR=1e-05              # Peak LR for fixed LR scheduler.
NUM_CLASSES=4
MAX_SENTENCES=1       # Batch size per GPU.
UPDATE_FREQ=16         # Accumulate gradients to simulate training on 8 GPUs.
DATA_DIR=./bin
ROBERTA_PATH=checkpoints/checkpoint_best.pt

fairseq-train $DATA_DIR --ddp-backend=no_c10d \
    --restore-file $ROBERTA_PATH \
    --reset-optimizer --reset-dataloader --reset-meters \
    --best-checkpoint-metric accuracy --maximize-best-checkpoint-metric \
    --task sentence_ranking \
    --num-classes $NUM_CLASSES \
    --init-token 0 --separator-token 2 \
    --max-option-length 128 \
    --max-positions 512 \
    --truncate-sequence \
    --arch roberta_large \
    --dropout 0.1 --attention-dropout 0.1 --weight-decay 0.01 \
    --criterion sentence_ranking \
    --optimizer adam --adam-betas '(0.9, 0.98)' --adam-eps 1e-06 \
    --clip-norm 0.0 \
    --lr-scheduler fixed --lr $LR \
    --fp16 --fp16-init-scale 4 --threshold-loss-scale 1 --fp16-scale-window 128 \
    --max-sentences $MAX_SENTENCES \
    --required-batch-size-multiple 1 \
    --update-freq $UPDATE_FREQ \
    --max-epoch $MAX_EPOCH \
    --valid-subset test \  then change this to `test1` after completion
    --save-dir ./checkpoints/RACE \
    --save-interval-updates 1 \

The trick here is to replace the dev data with test data and set the evaluation interval to once per iteration. After the first evaluation on test data we can exit the program and repeat this process on test1.
However, there might be an error when calculating the gross accuracy on RACE data, the correct value should be:
# Number of samples: 1436 (Middle) and 3498 (High)
# Accuracy: 86.5% (Middle) and 81.3%(High)
>>> (1436 * 0.865 + 3498 * 0.813) / (1436 + 3498)
0.8281341710579652

Which is different from the reported result 83.2% in paper

please show me your RACE Evaluation code.

There are a few options:

During training you can set --valid-subset valid,test,test1 and it will print results for valid, test and test1 during training.
Alternatively you can use fairseq-validate to evaluate an existing finetuned model on a new dataset. I'll add some instructions for this approach in a bit.


update pipeline/component reference doc

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

Refer:
Doc: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/ml/azure-ai-ml/documentation_guidelines.md
PR: https://github.com/Azure/azure-sdk-for-python/pull/30601/files

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml

Hi Stephen,
The following classes/methods are also Component/Pipeline. Could you please include them in this PR?

load_component
ComponentOperations
pipeline

Hi Chenyang,
The following classes/methods are also Component/Pipeline. Could you please include them in this PR?

load_component
ComponentOperations
pipeline
'PipelineJobSettings`

Some class have already added usage methods, while others are private and not for external use, so there is no need to add them.


Size miscalculations with bigboot role

If bigboot_size is given as bytes, i.e., a whole number without an IEC suffix, the bigboot.sh script fails when kicking off the sfdisk --move-data. See example failure below. The reason for this is that in the absence of a suffix, the sfdisk utility size units default to sectors, not bytes. This is the root cause even though the error output complains about "disk is currently in use"...
[   13.237233] Shrinking PV /dev/nvme0n1p2 to<PHONE_NUMBER>8 bytes
[   13.311795] Shrinking partition 2 in /dev/nvme0n1
[   13.332752] Moving up partition 2 in /dev/nvme0n1 by 419430400
[   17.349876] [dracut-pre-mount] Failed to extend boot partition: Failed to shift partition '/dev/nvme0n12': Checking that no-one is using this disk right now ... FAILED
[   17.349876]
[   17.349876] This disk is currently in use - repartitioning is probably a bad idea.
[   17.349876] Umount all file systems, and swapoff all swap partitions on this disk.
...

We also sometime see LVM logging "Device has size of X sectors which is smaller than corresponding PV size" warnings. I think this is because the pvresize is rounding to the closest multiple of physical extent size which may not align with the new partition size. For example...
lvm: WARNING: Device /dev/nvme0n1p2 has size of 65107968 sectors which is smaller than corresponding PV size of 65112031 sectors. Was device resized?
lvm: One or more devices used as PVs in VG VolGroup00 have changed sizes.

Recommend fixing the bigboot.sh script to prevent these issues.

Fixed by #60.


Filtering tables in the table window

Some times ago I wrote about HeidiSQL filtering search for tables. I think it's a cool feature that allow to simple find required table. I agree with you, that it isn't logic to do it in left panel, but I think it possible to add it in a table window.
So, I see two ways how to realize it.

When you clicked ctrl+f  you will see only those tables which went through a filter. I think it allow to find required table faster then current method when you highlight a table by green color.
It works as in the previous example, except you should click shift+ctrl+f. So you can use ctrl+f or ctrl+shift+f where ctrl+f will still work to highlight tables by color and ctrl+shift+f will filter result.

I ask you to think about it! :)

+1
You should rename this to 'filtering tables in table window'

Agreed, that makes sense.
And will make UI more consistent.

I'll keep only "filter" search (first one). I don't want to overcomplicate simple feature.
Let's see how it will go..


Unsupported Range index types should fail with table validation

I got this error when segments were trying to seal
[2024-11-12 19:13:15.648954] java.lang.RuntimeException: Unsupported data type TIMESTAMP for range index
[2024-11-12 19:13:15.648973] 	at org.apache.pinot.segment.spi.index.creator.CombinedInvertedIndexCreator.add(CombinedInvertedIndexCreator.java:53

This is indeed unsupported, https://github.com/apache/pinot/blob/master/pinot-segment-spi/src/main/java/org/apache/pinot/segment/spi/index/creator/CombinedInvertedIndexCreator.java#L53, but it's not clear to me why it fails after the table is created

I think this is a bug. Range index should be applicable to TIMESTAMP type


Fail to read delta table on mounted disk

Environment
Delta-rs version:
0.7.0 (latest main)
Binding:
Python
Environment:

Cloud provider: N/A (mounted server disk)
OS: *NIX
Other:

Bug
What happened:
I'm trying to read a delta-table, that located on a local server.
If we run the following code:
from deltalake import DeltaTable
path = 'file:///mnt/path/to/table/'
DeltaTable(path).to_pyarrow_table()

We will get the following error:

Traceback
Traceback (most recent call last):
  File "/path/to/main.py", line 2, in <module>
    dt.to_pyarrow_table()
  File "/path/to/deltalake/table.py", line 401, in to_pyarrow_table
    return self.to_pyarrow_dataset(
  File "pyarrow/_dataset.pyx", line 369, in pyarrow._dataset.Dataset.to_table
  File "pyarrow/_dataset.pyx", line 2818, in pyarrow._dataset.Scanner.to_table
  File "pyarrow/error.pxi", line 144, in pyarrow.lib.pyarrow_internal_check_status
  File "pyarrow/_fs.pyx", line 1551, in pyarrow._fs._cb_open_input_file
  File "/path/to/deltalake/fs.py", line 22, in open_input_file
    return pa.PythonFile(DeltaFileSystemHandler.open_input_file(self, path))
deltalake.PyDeltaTableError: Object at location /mnt/network_expansion/path/to/table/part-00000-aaaaaa-1111-2222-bbbbb-333333333.c000.snappy.parquet not found: No such file or directory (os error 2)

The *.parquet file is present.

What you expected to happen:
Succeful read
How to reproduce it:
More details:
Worth noting:

If we run similar code, but written in Rust, it will work just fine.
The full network path contains characters that get URL-encoded.
If we try to save schema (file://) in url-path, as suggested in this issue, the code will do some more progress (it will find and read all *.parquet files), but will fail with a SIGABRT.

From (1) I'm taking a guess, that there's a broken logic either somewhere in deltalake python wrapper, because (looking at the traceback):
File "pyarrow/_fs.pyx", line 1551, in pyarrow._fs._cb_open_input_file is a call from PyArrow to a SystemHandler, which is DeltaFileSystemHandler

Apparently, the current version (0.7.0) is unable to read a table, locally or over a network, if the path contains characters like space, which will be encoded with percent. This issue is related to this issue.
@wjones127, I attempted some hotfixes for my use case, which can be found in that PR. Please let me know if you would like me to open this PR in the main repo, as I would be eager to help.
The reason it is not working currently is that the str from the user gets converted to a Url representation, where all "bad" characters get encoded. Then, when DeltaObjectStore::try_new is called, the URL gets converted to a Path object, where all "bad" characters get encoded again.
My use case is a little more complex, as the path to the mounted folder does not contain any "bad" characters. However, when this path is expanded to some network server address, it contains URL-encoded characters. Therefore, I had to do something with the file:// schema.

So I think the problem is when we load a delta table we take the path (as a string) and convert it into a Url (which percent-encodes values). This makes sense for objects stores, but not local file systems. I think we need to think about a better way to handle this. cc @roeap

I thinking we should instead use a type like:
enum TableUri {
    LocalPath(Path),
    RemoteUrl(Url)
}

What do you think of that @roeap?

Huh, actually it might be that object_store just won't support paths that contain spaces?
https://docs.rs/object_store/0.5.5/object_store/path/struct.Path.html#path-safety
But it seems like we should be able to support arbitrary characters above the root, as long as we are passing them along correctly?
https://github.com/apache/arrow-rs/blob/71ecc39f36c8f38a5fc93bc3878a607c831b2f12/object_store/src/local.rs#L1252

@wjones127 - sorry for taking so long, this somehow slipped my attention.
I think if just want to support spaces in the table root, we should get it to work, somehow like you described. As you mentioned object store is quite strict around how paths should look like, but I have right now no feeling on how limiting that is. I.e. if other writers can create somemting in an object store, that we would not be able to read.
To me all of this eventually points to handling absolute paths in the log as well since this will require different path handling quite deep into the log handling. While I have not yet really thought about this problem, I also haven't had an idea yet on that area that resonated..


feat: support dart: packages in TypeChecker.fromPackage and TypeChecker.fromName

fixes #278

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

Could you add tests for this?

I've added a small test similar to the existing TypeChecker.fromPackage test :+1:

Thanks!


Add bash based bootsrapping

Description of changes:

Adding bootsrap.sh as an alternate to cloudformation
Update README

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jmgrubb I've tested this that this script runs and deploys end to end and deploys resources. Can you please review, test, and confirm that all seems ok. Thanks


TFRS - Saving User Profile Bug

Describe the Bug
When updating the user’s information in the user profile, after going to save the information, the user must confirm the update to the profile by clicking Yes on a confirmation alert (pop up window). The confirmation alert window does not disappear after the user confirms that they want to update the profile.
Expected Behaviour
The confirmation alert should disappear after the user clicks on the “Yes” button to confirm the changes to their user profile.
Actual Behaviour
The confirmation alert window remains on the screen despite the user selecting "Yes" to confirm the update and the system saving the updated information.
Steps To Reproduce
For both BCeID & IDIR Users:

Click on the User’s Name in the top right-hand corner of the page
Click on Settings, then click on the ‘User Profile’ sub-tab
Make a change to the information in one of the fields for the user profile
Click the ‘Save User’ button
The confirmation alert window will appear asking the user to confirm the update
Click “Yes”, the Confirmation window remains on the page.

Screenshot(s):
Notes
Probably just an issue in the handleSubmit() function of UserEditContainer.

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @jig-patel @tim738745


Bump the memory limit as the job is running out of memory.

Feeds is currently hitting the 512Mb limit regularly.

Is this because of recent changes?


Extract demo

Just a CI test

Ok, @jvdp1 I've created this PR on my own fork of stdlib just to see if that pull/665 would fix the entire PR pull/662 so we don't need to wait as much.
The "fpm CI" it's satisfied but intel compilers don't allow the formatted IO using the '(A)' (character) descriptor. I guess either changing it to '(DT)' descriptor or just "importing" the write(unformatted) and then printing using print*, will do the trick.
I'll go ahead and push a few commits in your extract_demo branch then I will re-run the CI to see if the problem is gone or if there's anything else to fix.
You can see the intel CI here
The following tests FAILED:
	232 - padl (Failed)
	233 - padr (Failed)
	234 - replace_all (Failed)

Great, now the example with padr passes which means using DT instead of A makes intel Fortran happy
Errors while running CTest
The following tests FAILED:
	232 - padl (Failed)
	234 - replace_all (Failed)


Update to PRT 2.2 and basic array attribute support

This is a big PR covering multiple topics:

Update to PRT 2.2 (includes requiring MSVC 14.2 on Windows)
Adding array attribute support both when creating initial shapes and when re-emitting them onto the generated models.
Fixing the unit tests.
Pruning Houdini 17.0 from the CI pipeline.
Various code cleanups and small improvements.

Thanks for review. I've factored out the attribute conversion and made it a bit more symmetrical. Still some more opportunities to deduplicate the code in AttributeConversion.cpp but I'll stop here for now.


fix test tool assign overflow of create

Description
following cases failed due to
CodeDB::empty_code_hash().to_word() - callee_prev_code_hash),    arithmetic overflow.
CreateCollisionToEmpty_d2_g0_v0
CreateCollisionToEmpty_d2_g0_v1
Issue Link
[link issue here]
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Contents

[item]

Rationale
[design decisions and extended information]
How Has This Been Tested?
[explanation]

How to fill a PR description
Please give a concise description of your PR.
The target readers could be future developers, reviewers, and auditors. By reading your description, they should easily understand the changes proposed in this pull request.
MUST: Reference the issue to resolve
Single responsability
Is RECOMMENDED to create single responsibility commits, but not mandatory.
Anyway, you MUST enumerate the changes in a unitary way, e.g.
This PR contains:
- Cleanup of xxxx, yyyy
- Changed xxxx to yyyy in order to bla bla
- Added xxxx function to ...
- Refactored ....

Design choices
RECOMMENDED to:

What types of design choices did you face?
What decisions you have made?
Any valuable information that could help reviewers to think critically

\b run testool 1


Skip obsolete logs when recovering

When recoveing logs, the database was operating under assumption that re-applying older commits is generally fine. In reality there are consistency issues when a  older commit is re-applied without also replaying the whole sequence that leads to the latest commit. Here I've added a file that keeps the last record id. This file gets fsynced after syncing all the data files. Which should guarantee that all previous records are solid. When recovring logs there's now a check for such obsolete records and all such records are skipped.

Imagine the database has commits A, B, and C fully applied in order. Than after the restart the logs for B and C are still arround. Re-enacting B and C would simply overwrite the same records and the database still ends up in the same state C. The problem is when the log for B is present, but the log for C is missing. We don't want to apply just B because it will break consistency.

We don't want to apply just B because it will break consistency.

Genuine question (sorry if it's a dumb question): I am not sure to grasp how it breaks consistency. If we apply just B it means the database will be recovered up to B and not up to A if we don't recover. How is it breaking consistency more to recover up to B?

Genuine question (sorry if it's a dumb question): I am not sure to grasp how it breaks consistency. If we apply just B it means the database will be recovered up to B and not up to A if we don't recover. How is it breaking consistency more to recover up to B?

Remember, that in this premise "C" was also applied previously. So the database has entries added in C. Aplying B over C may violate app logics. E.g. in substrtate  C sets both the best block and best finalized block pointer to 2. B sets the best block to 1. If you re-apply B over C you'll end up with best block=1 and best finalized=2 which violates substrate invariants.  It is better to just not allow that on the database level.

On the second thought this implementaiton does not guarantee that the record file contents matches the state on-disk. The problem here is that we dont fsync individual commits, but rather just fsync periodically.
There's a simpler way to solve the issue I think. That is to simply make sure the logs are dropped always in order, so that recovery ends up with the actual latest log.

On the second thought this implementaiton does not guarantee that the record file contents matches the state on-disk. The problem here is that we dont fsync individual commits, but rather just fsync periodically. There's a simpler way to solve the issue I think. That is to simply make sure the logs are dropped always in order, so that recovery ends up with the actual latest log.

I did like the direction where we got specific record id register and checked (eg for debugging purpose), not sure if it can be kept in some way.


How to use ngx-translate in electron app?

I have searched hard on Google without finding an answer to this issue.
I have an Electron + Ionic + Angular app. ngx-translate works well in the Angular part. I have also a top menu in the Electron desktop app that I would like to localize (plus a few other messages coming from the Electron part).
Let's say that I have an IPC mechanism to sync between the Electron and Angular parts the current language. How do I retrieve the current localization on the Electron part? How do I instantiate ngx-translate in Electron?
Is there a best practice how to localize the Electron part of an Electron + Angular part? Another idea is to translate the Electron top menu structure in Angular and send the whole to Electron via IPC but that seems to be very "complicated".
Also asked on SO: https://stackoverflow.com/questions/75332326/how-to-use-ngx-translate-in-electron-part-of-angularelectron-app

Ping? Is this possible to get some help? Is it possible to use ngx-translate in electron? Is there a tutorial or some documentation somewhere?


HBASE-27001 The deleted variable cannot be printed out

The deleted variable cannot be printed out, add it

Co-authored-by: selina.yan<EMAIL_ADDRESS>Signed-off-by: Pankaj<EMAIL_ADDRESS>(cherry picked from commit b8558d30d0027d031ce6dec8b2ba0243c3a58554)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
2m 52s
branch-2.4 passed

+1 :green_heart:
compile
2m 35s
branch-2.4 passed

+1 :green_heart:
checkstyle
0m 38s
branch-2.4 passed

+1 :green_heart:
spotless
0m 41s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 35s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 35s
the patch passed

+1 :green_heart:
compile
2m 53s
the patch passed

+1 :green_heart:
javac
2m 53s
the patch passed

+1 :green_heart:
checkstyle
0m 43s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m 59s
Patch does not cause any errors with Hadoop 2.10.2 or 3.1.4 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 52s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s
The patch does not generate ASF License warnings.

39m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4883/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4883

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux f0876a07ebad 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / f7b2efc7b7

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4883/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 27s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
2m 31s
branch-2.4 passed

+1 :green_heart:
compile
0m 42s
branch-2.4 passed

+1 :green_heart:
shadedjars
4m  7s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 26s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 21s
the patch passed

+1 :green_heart:
compile
0m 42s
the patch passed

+1 :green_heart:
javac
0m 42s
the patch passed

+1 :green_heart:
shadedjars
4m  5s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
160m 50s
hbase-server in the patch passed.

180m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4883/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4883

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2ce60d51910b 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / f7b2efc7b7

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4883/1/testReport/

Max. process+thread count
2729 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4883/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Fix: check any VIPs and Nodes left before delete a partition.

If there is nothing (VIPs and Nodes) left on a partition,
then we can delete that partition.
Do not let the user add a node or a vip manually by web GUI.

LGTM.

Thanks


support data-owns

As per https://github.com/krautzource/aria-tree-walker/issues/12#issuecomment-789595374 pp we often do not need aria-owns but can use a custom attribute, thus reducing ID related overhead for authors.
We should probably continue to support aria-owns so this should be a feature (and not a breaking change).

This need downstream support.

=> https://github.com/krautzource/aria-tree-walker/issues/26

We'd need another attribute to serve the equivalent of ID. Is data-id too generic? data-own-id? data-tree-id (but then data-tree instead of data-own)?

Slight snag: aria-activedescendant still needs an ID (I didn't actually turn off IDs during the earlier tests). So we'll need to test switching to a roving tabindex as well.

So we'll need to test switching to a roving tabindex as well.

I'm struggling with this actually. But I had another idea, "roving id", where we could re-use an id across the tree. That way we'd only have a single ID to worry about (and only during exploration). A quick test with NVDA worked but this needs more research.

A quick test with NVDA worked but this needs more research.

Orca seems good. JAWS doesn't seem to like returning to the root; needs looking into.

JAWS doesn't seem to like returning to the root; needs looking into.

Actually NVDA also failed. That's likely because a node can't be its own active-descendant (as per spec, anyway). Quick test on VO also didn't seem much worse. More testing needed in any case.

Reconsidering roving tabindex after realizing I had not read the APG pattern properly. It looks (much) simpler after all.

To recap: the second attempt with roving tabindex works well. NVDA, JAWS, Narrator seem ok on Chrome and FF, Orca on FF has a minor issue (returning to root is silent), VO is ok on Chrome, FF (issue like Orca) and bareable on Safari, ChromeVox (ChromeOS) is also ok.

Maybe this should become breaking change after all. Switching from aria-activeDescendant to a roving tabindex appoach is a rather large change and while not formally changing the API it might break things.
For example, our docs use :focus to style the background of the root which will break as (DOM) focus starts to move around. Hardly a huge change but nevertheless breaking.

Thinking about this some more, I think we can remove aria-owns support altogether. Aria-owns is only necessary on the tree root so authors should only have to duplicate aria-owns as data-owns at the root.
That would make this a truly breaking change (but also much simpler).


Add Open Horizon to Landscape

Logo = https://github.com/lf-edge/artwork/blob/master/openhorizon/horizontal/color/openhorizon-horizontal-color.svg
Website = https://www.lfedge.org/projects-old/openhorizon/
GitHub = https://github.com/open-horizon/

@bprestonlf Do you feel that Platforms > IoT-Focused is the most appropriate category for this listing?

Comment from Joe Pearson in regards to category:

Options that spring to mind in order of preference for Platform sub-categories:

Application & ML Model Delivery (wordy but descriptive, maybe too specific)
Application & Asset Distribution

If we were to create a sub-category like one of those, both Open Horizon and KubeFlow could be placed into it, off the top of my head.

Application & Model Delivery


add hive queries

Tomek - there are some queries that  contains 'explain' statements - could you please clean them before merging?


Use libusb with sleep crash fix

Update to use fixed libusb to prevent Windows crash on sleep. Fixes #220, #124
Test version available by installing as follows:
npm i usb@testing

Currently untested
cc @jeremywho

I just tested it.
No Crash!
Let me know if I can help with any other testing or any other data collection to get this in.


use push_cc_arg for options add

This commit forms proper command line for nvcc on windows. At least it now can compile.

Thanks!


[ci] test 32-bit R in CI

Based on https://github.com/microsoft/LightGBM/issues/3585#issuecomment-731663718. We were recently surprised by some test failures on 32-bit Windows checks for CRAN.
I think this is because I thought we were running tests with a 32-bit version of R on Windows (#3311 ) but maybe we never actually were.
I think that the root cause is that the test setup for our R environment doesn't install i386 components for R-win.exe, as documented in https://cran.r-project.org/bin/windows/base/rw-FAQ.html#Can-I-customize-the-installation_003f.
As of this PR, 32-bit R will be installed in GitHub Actions jobs and the R package will be tested against both architectures (x86 and i386).
Questions for Reviewers
In #3585 , we ran into issues only on CRAN's R 3.6 + Windows (32-bit) job. Today, the only tests of the CRAN package are on R 4.0. That's a gap between this project's CI and CRAN, which means we could run into this situation again in future CRAN submission. In this PR I'd like to also add an R 3.6 + Windows + build_type: cran job.
GitHub Actions gives you 20 concurrent job runs, and right now we have 17 jobs that run on every PR.
How do you feel about adding this additional job?
          - os: windows-latest
            task: r-package
            compiler: MINGW
            toolchain: MINGW
            r_version: 3.6
            build_type: cran

I think this worked! Now the behavior in CI matches what we're seeing on CRAN...the R3.6 + cran build is failing with the exact same issues described in #3585
https://github.com/microsoft/LightGBM/pull/3588/checks?check_run_id=1437170140
  == testthat results  ===========================================================

  FAILURE (test_learning_to_rank.R:52:9): learning-to-rank with lgb.train() works as expected

  FAILURE (test_learning_to_rank.R:53:9): learning-to-rank with lgb.train() works as expected

  FAILURE (test_learning_to_rank.R:130:5): learning-to-rank with lgb.cv() works as expected

  FAILURE (test_learning_to_rank.R:136:5): learning-to-rank with lgb.cv() works as expected

And also a new compiler warning we haven't noticed before
./include/LightGBM/utils/common.h:47:0: warning: "_mm_free" redefined
 #define _mm_free(a) free(a)
 ^

./include/LightGBM/utils/common.h:46:0: warning: "_mm_malloc" redefined
 #define _mm_malloc(a, b) malloc(a)
 ^

How do you feel about adding this additional job?

Totally fine!

@StrikerRUS I just moved the changes to the tests from #3586 over to this PR. Since it seems like #3586 might be delayed for an unknown amount of time waiting for CRAN to reply, I think we should merge this PR with the updated tests + the new CI job sooner.
I want this new CI job to be sure that new bugfixes and features (for example, #3405) don't break the 32-bit CRAN checks.

checked the logs one more time and I can see the tests are now running for both i386 and x64 architectures


Bug in g_path_regularize loss in multi-gpu case

In https://github.com/rosinality/stylegan2-pytorch/blob/master/train.py#L96
there are lines
path_lengths = torch.sqrt(grad.pow(2).sum(2).mean(1))
path_mean = mean_path_length + decay * (path_lengths.mean() - mean_path_length)
path_penalty = (path_lengths - path_mean).pow(2).mean()

However this would not produce the same penalty in multi-gpu case compared to single-gpu case if we consider the same total batch size.
Instead there should be something like:
path_lengths = torch.sqrt(grad.pow(2).sum(2).mean(1))
path_mean_cur = all_reduce_mean(path_lengths) # must be differentiable version
path_mean = mean_path_length + decay * (path_mean_cur - mean_path_length)
path_penalty = (path_lengths - path_mean).pow(2).mean()

As an analogy one can think about nn.SyncBatchNorm vs nn.BatchNorm

Yes, but I don't know synchronization is needed for training. (I think official repository does not sync statistics.)


thead and tbody get mixed starting from second page

I'm creating a pdf from a html with thead and tbody tags, I have already removed all style I had and I'm still with the same problem.
Starting from second page the tbody overwrite thead, like on image bellow:

It is very strange because it works on the first page (image below) and I don't have any style on this page.

It seems to happened too with the guy who opened this issue: https://github.com/marcbachmann/node-html-pdf/issues/36. But he didn't want to have table headers on all pages, I want to.
Do you ever experienced this problem? Is there a way to solve it?

Is there any known solution?

Having the same issue here.

Any luck?

@kodamirmo  In the latest release of nodeice, I switched to the phantom-html-to-pdf package by @pofider which doesn't have this bug. :sparkles:

@IonicaBizau and @kodamirmo .... phantom-html-to-pdf has the same bug if you set the orientation the landscape :-(
pageSize: {
     orientation: 'landscape'
}

That maybe works. https://github.com/marcbachmann/node-html-pdf/issues/36#issuecomment-110530819

Sitting the proper css rules seemed to work for me:
thead {
  display: table-header-group;
}

tr {
  page-break-inside: avoid;
}

Headers repeated correctly without overlap. One trick is that you can't have any of those rules inside of a @print media rule, as it seems that it can't calculate the repeating headers correctly when doing so.

I seem to be unable to get this to work on my end. A working example of this would be greatly appreciated :)

I've been unable to get it to repeat headers, using v2.1 of this lib. Any update?
This might be related: https://github.com/ariya/phantomjs/issues/13324

Same here. Did you find a workaround in the meantime @sonu27?

Hi,
table thead section is not repeating after page break. I am using simple html.

 header

data

Is anyone found solution?
Regards,
Rohit

Can this be closed?


Support for USING clause for joins

Use case:
The PostgreSQL JDBC client invokes the following query when using
conn.getMetaData().getVersionColumns(...).
Part of the query uses JOIN (...) as r USING (nspname). This triggers an
error in CrateDB: UnsupportedFeatureException: join criteria JoinUsing not supported
USING is a short-hand for equi-joins when the columns of both relations have
the same name. See Simplifying Joins with the USING
keyword
The full query:
SELECT
    typinput = 'array_in'::regproc,
    typtype
FROM
    pg_catalog.pg_type
    LEFT JOIN (
        SELECT
            ns.oid AS nspoid,
            ns.nspname,
            r.r
        FROM
            pg_namespace AS ns
            JOIN (
                SELECT
                    s.r,
                    (current_schemas(FALSE))[s.r] AS nspname
                FROM
                    generate_series(1, array_upper(current_schemas(FALSE), 1)) AS s (r)
            ) AS r USING (nspname)) AS sp ON sp.nspoid = typnamespace
WHERE
    typname = $1
ORDER BY
    sp.r,
    pg_type.oid DESC
LIMIT 1

https://github.com/crate/crate/pull/9629


Add nested arrays and slash commands

I found the following two features useful:
Nested arrays
! array time = always sometimes often
! array period = day month year
! array nested = @time @period

Slash commands
Use in trigger:
+ /help

Cheers,
Paweł

Nested arrays sound useful. Can you add a call to self._warn() in the event that the array named doesn't exist yet? One reason I hadn't added nested arrays in the past is that RiveScript files should be loadable in any order, and if an array in file "A" embeds a nested array that was defined in file "B", then it won't work how the user expected if those files are loaded in the wrong order.
Defining all arrays that refer to each other inside the same file makes that problem a little easier, but the parser should emit a warning whenever it sees an embedded array that hasn't yet been defined.
Another complication with nested arrays will be with the deparse()/write() methods; after parsing, since all the sub-arrays were expanded out, the actual names of the sub-arrays get lost and can't be reproduced when written back to disk. These functions are for advanced use cases though so it's not the worst problem in the world.
Also what happens if the nested array contains more arrays itself?
! array primary = red green blue
! array secondary = magenta cyan yellow
! array monochrome = gray grey black white
! array rgb = @primary @secondary
! array colors = @rgb @monochrome orange brown pink

I think a more robust solution to all of the above problems will be to only expand nested arrays at reply matching time. So after parsing, the "colors" array above would contain literal @rgb type entries, and in the _reply_regexp() function use a while loop when processing arrays. So, if after processing one array you get new @array parts in the result, process it again; the while loop would run until there are no more @array, or the trigger text doesn't change from one loop to another, or when self._depth is reached (to give a warning and break when you have two arrays that reference each other in an infinite loop).

As for the Slash Commands, you should be able to just use them as-is when UTF-8 mode is enabled (rs = RiveScript(utf8=True)), which causes the syntax checker for triggers to be a lot looser.

Hi, thanks for comments. I added a more robust implementation and tests, removed the unnecessary slash command changes.


Package microtype Warning: Unable to apply patch 'eqnum' and 'footnote'

When I am using \RequirePackage{microtype} on @overleaf with TeX Live version 2021 and XeLateX, I get no warnings.
But, If I change the TeX Live version to 2022 I get the following warnings:
Package microtype Warning: Unable to apply patch 'eqnum'
Package microtype Warning: Unable to apply patch 'footnote'

If I back to 2021, I have no more warnings again.
I have found a workaround. If I put \RequirePackage[nopatch={eqnum,footnote}]{microtype}, the warnings will disappear, but I guess that this solution is not the best way, because in the previous version was working fine.
I found a similar question to mine, but with no answer: https://tex.stackexchange.com/questions/654914/how-to-resolve-this-message-package-microtype-warning-unable-to-apply-patch-e

@manascimento - could you provide a minimal example that reproduces this problem with the Overleaf TL 2022 image? If you send this to Overleaf support<EMAIL_ADDRESS>that would be helpful.
If you add the latest microtype.sty file to your Overleaf project, does that resolve the issue? Overleaf's current version of microtype is microtype 2022/03/14 v3.0d which is slightly behind the latest version.

I suspect these warnings were due to the fact that Overleaf had an outdated version of microtype. In view of your report (and other similar questions), I've asked the good people there to update to the current version, which they've thankfully agreed to and which hopefully should resolve the issue for you and everybody else using Overleaf. Therefore I'm closing this as a duplicate. Should you still get warnings, please provide a minimal example.

@dmackinnon1 and @schlcht thanks so much for your answers. I just sent an e-mail to @overleaf team as @dmackinnon1 suggested. I'm waiting for the answer from them.
As soon, they replied, I will do another test. If OK, I will update you. If not, I bring more details about the issue.
But, I agree with you that the problem could the version is outdate.

Hi everybody!
The @overleaf team helped me to fix this issue.
The order that I was loading some packages raised the warning. Three packages were involved: microtype, hyperref and setspace.
Solution:
\usepackage{microtype} should be the first package to be loaded. And \usepackage{setspace} must be before \usepackage{hyperref}.
So, changing the order to:
\usepackage{microtype}
\usepackage{setspace}
\usepackage{hyperref}

The warning disappeared.
The reasons you can find here: https://tex.stackexchange.com/questions/188273/using-setspace-package-breaks-footnotes-link.
Thank you, Dan (@overleaf support team) for your attention.

Great to hear that your problem is solved now. Just for the record, the order issue only involves setspace and hyperref, whereas microtype may be loaded at any time (before, between or after the two packages). Also just for information, Overleaf now provides the latest version of microtype (thanks, @overleaf!).


Ejected app from expo crashes android

If I have
project.ext {     excludeAppGlideModule = true }
in build.gradle,
Android app crashes with:

Otherwise app crashes silently.
I just ejected from expo, and this library was the only reason why I ejected. Now I cannot build it or even run it on android. :(
Dependency versions

React Native version: expo sdk 33
React version: 16.8.3
React Native Fast Image version: 6.0.3

I googled already a lot, added everything to progurad-rules.pro ... but no luck...
Any ideas?

These look similar #516

This will need to wait until Expo updates to React Native 0.60.0.


Opening devtools while in text input element writing "î" on french keyboards

Here's the problem:
Opening devtools using the keyboard shortcut (cmd + alt + i) on a french AZERTY keyboard on OS X Yosemite happens to write an "î" (alt + i on french keyboard) if focus is on any text-input element (textarea, input, atom editor).
Spotted on Atom 1.3.1 (Electron v0.34.3).
I hope I provided enough information.
Thanks for the good work!

It has been fixed in Electron 0.36.0 and will be included in Atom once Atom updates the electron version.


UX/Visual: Input error validation placement redesign

Detailed description
UX/Visual question
When validation is triggered form input error messages are currently rendered below the input field where the error occurred. In areas where there is not enough space to accommodate this added element you get a jump in the layout.

This seems to be a common issue/annoyance for consumers as some people have been asking for guidance on how to deal with this layout jump. I wanted to share my team's solution which has been to absolutely position the error message to the top and then translate up 100% to deal with different lengths of message. Super long messages are still handled but not ideal. Feedback on whether this is an acceptable pattern and whether any improvements could be thought of would be appreciated.

Proposed solution

Is this issue related to a specific component?

Form Inputs

What browser are you working in?

Chrome

What version of the Carbon Design System are you using?

latest
Add labels
Visual

cc @carbon-design-system/design if you all have any input/typical guidance for these kinds of discussions!

So we ran into a similar issue when doing inline edit in a data table. This is the solution we came up with:

The error icon is always there but the validation message "tooltip" only appears on field focus or when the user hover/focuses on the error icon

That is interesting. I like this approach. Only being visible on focus would probably be an issue in certain uses cases. I do like the flexibility to allow for larger error messages.

I'm going to close this simply because work on inline data-table editing has been halted, and the jumping should be solved with the new input fields. We can reopen this if this becomes a more pressing need


accept failing in ECell on Rubinius

When I run ECell (not-quite-yet-released Celluloid project, sorry) on Rubinius and then start Reel, the @server.accept call in Server#run seems to never return. If I start Reel by itself without setting up ECell first, it works fine.

Can you please include a quick gist of these scenarios and mention which version of rbx? Will look at this.

The Reel Piece in the ECell repo displays this issue on rubinius 3.50 (2.3.1 8a6c33ad 2016-07-25 3.8.0) [x86_64-linux-gnu]


Bump WOM utils to allow GB constituent countries

Depends on https://github.com/wise-old-man/wiseoldman-runelite-plugin/issues/42 because this breaks RL plugin searches for players with new country flags.

The required changes to the plugin have been PRed to the plugin hub. https://github.com/runelite/plugin-hub/pull/5976.
This PR can be merged when that PR has been merged.


Resolve issue with Build badge

Correct path in README for Build.yml.
Hey @valadas - you may want to update the template too for this.

Thanks for the reminder, it is now implemented in the template too https://github.com/valadas/Eraware_Dnn_Templates/pull/447


la-go-live

Docs Build status updates of commit d248b34:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/onboard-teams-dev-platform/build-your-first-app/build-real-world-app.md
:warning:Warning
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/apps-upload.md
:bulb:Suggestion
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/publish.md
:bulb:Suggestion
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/using-teams-client-sdk.md
:bulb:Suggestion
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-messaging-extensions.md
:bulb:Suggestion
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-tabs.md
:bulb:Suggestion
View
Details

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-webhooks-and-connectors.md
:bulb:Suggestion
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/IIS.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/solution-configurations.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/visual-studio-web-dev-module.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/build-your-first-app/add-channel-tab.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/build-your-first-app/add-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/build-your-first-app/build-and-run-with-toolkit.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/capabilities-overview.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/debug.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/designing-overview.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/extensibility-points.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/capabilities-overview.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/channel-tab-tutorial-content-installed.PNG
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/channel-tab-tutorial-content.PNG
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/favicon-16x16.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/overview-bots.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/overview-connectors.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/overview-graph.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/overview-messaging.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/overview-tabs.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/personal-tab-tutorial-content.PNG
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/personal-tab-tutorial-updated-theme.PNG
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/tab-running.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/toolkit-add-tabs.PNG
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/images/vs-code-extensions.png
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/importing-custom-microsoft-apps.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/integrating-web-apps.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/prepare-your-o365-tenant.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/share-to-teams.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/teams-ui-conventions.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/overview.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/what-are-cards.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/visual-studio-code-overview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/visual-studio-overview.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/vs-overview.md
:white_check_mark:Succeeded

msteams-platform/webhooks-and-connectors/how-to/connectors-using.md
:white_check_mark:Succeeded
View

msteams-platform/onboard-teams-dev-platform/build-your-first-app/build-real-world-app.md

Line 28, Column 39: [Warning-file-not-found] Invalid file link: '../doc-links/capabilities-overview.md'.

msteams-platform/onboard-teams-dev-platform/doc-links/apps-upload.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Upload your custom app in Microsoft Teams - Teams' is duplicated in: 'concepts/deploy-and-publish/apps-upload.md(2,8), onboard-teams-dev-platform/doc-links/apps-upload.md(2,8)'. Titles must be unique within a docset.
Line 6, Column 1: [Suggestion-duplicate-h1s] H1 'Upload an app package to Microsoft Teams' is duplicated with other articles: 'concepts/deploy-and-publish/apps-upload.md(6,1), onboard-teams-dev-platform/doc-links/apps-upload.md(6,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

msteams-platform/onboard-teams-dev-platform/doc-links/publish.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Microsoft Teams app approval process guidance - Teams' is duplicated in: 'concepts/deploy-and-publish/appsource/publish.md(2,8), onboard-teams-dev-platform/doc-links/publish.md(2,8)'. Titles must be unique within a docset.

msteams-platform/onboard-teams-dev-platform/doc-links/using-teams-client-sdk.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Using the Teams client SDK - Teams' is duplicated in: 'onboard-teams-dev-platform/doc-links/using-teams-client-sdk.md(2,8), tabs/how-to/using-teams-client-sdk.md(2,8)'. Titles must be unique within a docset.
Line 8, Column 1: [Suggestion-duplicate-h1s] H1 'Using the Teams client SDK' is duplicated with other articles: 'onboard-teams-dev-platform/doc-links/using-teams-client-sdk.md(8,1), tabs/how-to/using-teams-client-sdk.md(8,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-messaging-extensions.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'What are messaging extensions? - Teams' is duplicated in: 'messaging-extensions/what-are-messaging-extensions.md(2,8), onboard-teams-dev-platform/doc-links/what-are-messaging-extensions.md(2,8)'. Titles must be unique within a docset.
Line 8, Column 1: [Suggestion-duplicate-h1s] H1 'What are messaging extensions?' is duplicated with other articles: 'messaging-extensions/what-are-messaging-extensions.md(8,1), onboard-teams-dev-platform/doc-links/what-are-messaging-extensions.md(8,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-tabs.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'What are custom tabs in Microsoft Teams? - Teams' is duplicated in: 'onboard-teams-dev-platform/doc-links/what-are-tabs.md(2,8), tabs/what-are-tabs.md(2,8)'. Titles must be unique within a docset.

msteams-platform/onboard-teams-dev-platform/doc-links/what-are-webhooks-and-connectors.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'What are webhooks and connectors? - Teams' is duplicated in: 'onboard-teams-dev-platform/doc-links/what-are-webhooks-and-connectors.md(2,8), webhooks-and-connectors/what-are-webhooks-and-connectors.md(2,8)'. Titles must be unique within a docset.
Line 8, Column 1: [Suggestion-duplicate-h1s] H1 'What are webhooks and connectors?' is duplicated with other articles: 'onboard-teams-dev-platform/doc-links/what-are-webhooks-and-connectors.md(8,1), webhooks-and-connectors/what-are-webhooks-and-connectors.md(8,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Framed Cloud offsets are a bit of a jumble

I found this when I replaced cloud-popup-relative.png with a translucent version.
The "stem" of the popup (div id="foo_FrameDecorationDiv_4") is variously 33px, 33px, 35px, 35px in height (when in the top left, tr, bl, br respectively) but the rest of the popup is always positioned a vertical 32px away from the relevant edge of the foo_GroupDiv . These 1 and 3 pixel overlaps between the stem and the rest of the popup make no difference on a solid fill cloud-popup-relative.png as shipped with openlayers, but give artefacts on translucent ones.
https://github.com/openlayers/openlayers/blob/master/lib/OpenLayers/Popup/FramedCloud.js has the sizes and offsets. It's pretty clear that the stem sizes are inconsistent, but so are many of the other number (e.g. vertical offsets for the bottom of the main cloud of -631, -632, -629 all appear). I haven't made any effort (yet) to untangle them all.
I suspect the inconsistency are somewhat cancelling each other out on the default image, unless there is some subtlety that I'm missing?

https://github.com/cyclestreets/toolkit/blob/f76130e6aef41cd497d5e3c4604d1f846631fc84/public/openlayers/img/cloud-popup-relative.png is an example of a translucent cloud-popup-relative.png , based closely on the original opaque version. http://thunderflames.org/temp/ol-popup.png shows the overlap between the stem and the rest of the popup.

Nice background!
Yes, for some time Popus worry me (I'm not OpenLayers team), something like this can be seen with opaque image, the line lower right corner has two pixels.
I also worry that automatic sizing is not the same in all browsers... I tried, but so far I have not stability.


One-shot key support

Closes #122

Still needs to implement timeout, also needs to filter the events after the one shot so other modifiers or layer actions don't release the modifier.
Current implementation releases the modifier on the next key press, doing it on key release would be difficult since we would need to process every other key press inside process_key_action_oneshot. Maybe the other approach discussed here can give more flexibility.

Current implementation releases the modifier on the next key press, doing it on key release would be difficult since we would need to process every other key press inside process_key_action_oneshot. Maybe the other approach discussed https://github.com/HaoboGu/rmk/issues/122#issuecomment-2453224924 can give more flexibility.

The issue here is we want some keys not to be affected by one-shot key, so we have to do another full processing logic inside process_key_action_oneshot.

@HaoboGu The core feature seems to be done. I'd like to know what are your ideas on how the one shot should work on some edge cases, I'll need that to add to the documentation as well.

What about specifying which type of actions affect the one shot state? For example, pressing a modifier (or one shot modifier) after a one shot layer should disable the layer, so that OSL(1) -> LShift (hold)  -> key will result in LShift + key if LShift is on layer 1 and key is on layer 0. But pressing a modifier after a one shot modifier should do nothing.

@HaoboGu The core feature seems to be done. I'd like to know what are your ideas on how the one shot should work on some edge cases, I'll need that to add to the documentation as well.

Cool! I'm thinking about can we have one-shot behavior for any Action? Currently only Action::Modifier(m) and Action::LayerOn(n) are supported.
For example, Action::LayerOff(n) could also be used as one-shot behavior, which is very similar with Action::LayerOn(n)

Sure, i'll work on that.

What about specifying which type of actions affect the one shot state?

Yes, I think we should have this. Some Actions will have no effect when making it one-shot.

Ok, just now realized that zmk, has the answer, I think this is a good rule to follow.

If you find it difficult to achieve, we can also merge this PR as-is, since vial supports only OSL and OSM 😅

If you find it difficult to achieve, we can also merge this PR as-is, since vial supports only OSL and OSM 😅

Yeah, i think we can leave the "All Actions" part to another issue. I'll just change the way OSL works to match zmk as I linked above


chore(build): remove motion_utils.hpp in common/

Description
https://github.com/autowarefoundation/autoware.universe/issues/4821
depends: https://github.com/autowarefoundation/autoware.universe/pull/4829
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[X] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[X] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@isamu-takagi Can you approve this PR?


[FEAT] Add envsubst or placeholders to image

Is your feature request related to a problem? Please describe.
When using the Conduktor CLI to deploy resources (e.g., clusters), the configuration often includes sensitive data such as usernames and passwords. Currently, there is no standard way to safely hide or manage these sensitive values in CI/CD pipelines, which increases the risk of exposing credentials.
Describe the solution you'd like
I would like to have a standard method integrated into the Conduktor CLI for securely handling sensitive information in CI/CD environments. This could include support for tools like envsubst or a built-in placeholder system that securely replaces sensitive data during pipeline execution without exposing it.
Describe alternatives you've considered
I’ve considered using third-party solutions like envsubst to replace environment variables in configuration files, but this requires additional setup and doesn't ensure consistency across pipelines.

Hi @FelixGaebler
Good news, latest version of the Conduktor CLI (v0.3.1) include environment variable expansion in YAML manifests !
When reading YAML manifests, the Conduktor CLI search for ${ENV} patterns and replace them using found environment variable matching ENV name.
It also supports default values as fallback using POSIX notation ${ENV:-default}.
It fails if environment variable is not found or set empty.
You can avoid a crash and use empty string as default value if with permissive CLI flag.
You have an example test here
Hope this help !

Thanks alot! Still - you should include this into your documentation! :)

We missed this in our documentation, it's now fixed https://docs.conduktor.io/platform/reference/cli-reference/#using-environment-variables-for-secrets
Thank you for the reminder.


WIP: IT Rate FW setup

Big picture notes / questions

General:

Why do whe need a "Hit" class? Isn't this functionally the same as the Digi class?
Current QCoreProducer also prduces binary streams -> Separate stream creation from QCore production

adjustEdges: treatment of large pixels

Current implementation seems like it would sometimes generate multiple Hit objects with same row/column. Naively, would expect that the correct operation here would be to sum the ADC counts of multiple such pixels. Why is the current treatment OK?

ReadoutChip::get_organized_QCores:

Current workflow generates one QCore per hit, then loops again to remove duplicates

Duplicates are not merged. Does that not imply that all QCores have exactly one hit pixel?

Why is this multi-step method preferable to just creating well-defined, non-overlapping QCore objects from the start?
QCore sorting:

Could use C++ sort implementation with custom comparator, replace ReadoutChip::organize_QCores

Refactoring / class organization:

Current implementation has helper methods (adjustEdges, splitByChip) that have hardcoded geometry information -> Refactor into separate ChipGeometry class?
Current implementation has parts of stream encoding in Chip, parts in QCore class

-> Encapsulate encoding information in one single place
-> separate hit data storage structure from encoding format


Laravel Octane Support: Scoped service binding

See https://github.com/laravel-filament/filament/issues/2010
@danharrin As I was working on this I found there is an issue with octane itself where scoped services aren't being flushed correctly because of a discrepancy between octane and laravel itself. https://github.com/laravel/octane/issues/500
There is a workaround where after this pull request is submitted you can add the filament service to octane's flush services in the config like so:
config/octane.php:
<?php

...

return [

   ...

    /*
    |--------------------------------------------------------------------------
    | Warm / Flush Bindings
    |--------------------------------------------------------------------------
    |
    | The bindings listed below will either be pre-warmed when a worker boots
    | or they will be flushed before every new request. Flushing a binding
    | will force the container to resolve that binding again when asked.
    |
    */

    'warm' => [
        ...Octane::defaultServicesToWarm(),
    ],

    'flush' => [
        'filament'
    ],

  ...

];

Is that something that should be added to the documentation or do you want to just refer people here? Once the issue in the octane package is resolved we won't need to add that item to the flush in the config

Hey, let's refer people here. I don't want to add documentation that we then have to remove later when Laravel fixes the issue.
Thanks for the PR!


Create mulockgooi.txt

Website: http://www.mulockhouwer.nl/

How do I see when you accepted it?

The pull request will be marked accepted when your school is.


Demo - Deployer - Delete from staging bucket on publish

[x] Give Deployer permission to delete from staging bucket
[x] Delete from staging bucket after copying is done in Deployer

Duplicates #148


page-align uncompressed .so files

Thanks for providing a Java implementation of zipalign.
From my perspective it looks quite good, it only misses the possibilities to align .so files by 4096 instead of default 4.
This options is becoming more and more important as recent Android Gradle plugin versions automatically set extractNativeLibs=false which means they are no longer extracted from the APK file upon installation, but directly used from within the APK.
For doing so it is required to store the .so files uncompressed and align them to page boundaries (4096), independent of the value the other files are aligned to.

Hi!
I have been thinking about adding this feature, but haven't got the time for it and it's a bit difficult to do it with the current system. It's just adding a special case for .so files to align it by 4096, right? I'll try to do it whenever possible, thanks for the reminder.

I also need it very much. I hope the author has time to upgrade it. Thank you very much

I'm happy to share that aligning .so files will land on 1.1.0. I had just implemented in in the branch so-align. Thanks guys!


Enable multiple hooks to be added

Hello
I had a use case where I have 2 linters that both install hooks using git-validate, the problem came that the second would not install because hooks are not appended, just added. To fix this I merged the new hooks with the old hooks
Thanks
Jonathan

if you can remove the writing PATH to a file stuff and clean up the arrayUnique method to pass linting, this is a good fix

Made the changes but raised a different PR https://github.com/nlf/git-validate/pull/51


Milestone 0.10.1

Coverage increased (+0.4%) to 86.842% when pulling c8b7868fd626c8472f7d9f11c767479f3ad66e05 on milestone-0.10.1 into 3b7d918682367badceff0364118fddfd72cd52dc on master.


Swift 4.2 support

This Pr adds support for Swift 4.2.
It basically just applies the suggested migrations and bumps the swift-version file.

please merge this PR. thx


Upgrade Eclipse/Equinox to 2020-03

This PR also bumps the versions of most of the dependencies Snow Owl depends on:

Upgrade Equinox to 3.20
Upgrade Eclipse Platform to 4.15.0
Upgrade Groovy Eclipse to 3.7.0 (e4.15.0)
Upgrade Net4j to 4.9.0
Upgrade Orbit update site to R20200224183213
Upgrade Xtext/Xtend to 2.21.0
Upgrade EMF to 2.21.0
Upgrade MWE2 to 2.11.2
Upgrade Guava to 27.1.0
Upgrade classgraph to 4.8.77
Upgrade owlapi to 4.5.24 (b2i version)
Remove unused dom4j.

Codecov Report

Merging #547 into 7.x will increase coverage by 0.00%.
The diff coverage is 75.00%.

@@            Coverage Diff            @@
##                7.x     #547   +/-   ##
=========================================
  Coverage     52.89%   52.89%
+ Complexity    13562    13561    -1
=========================================
  Files          1793     1793
  Lines         86005    86010    +5
  Branches      11266    11266
=========================================
+ Hits          45493    45498    +5
+ Misses        35749    35742    -7
- Partials       4763     4770    +7

Impacted Files
Coverage Δ
Complexity Δ

...2international/commons/AlphaNumericComparator.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...e/src/com/b2international/commons/StringUtils.java
30.08% <50.00%> (ø)
18.00 <0.00> (ø)

...nternational/snowowl/core/events/util/Promise.java
70.53% <100.00%> (+1.37%)
19.00 <0.00> (ø)

...index/src/com/b2international/index/es/EsNode.java
84.33% <0.00%> (-1.21%)
15.00% <0.00%> (-1.00%)

...d/ecl/parser/antlr/internal/InternalEclParser.java
56.47% <0.00%> (-0.11%)
366.00% <0.00%> (-2.00%)

.../snomed/core/ecl/SnomedEclRefinementEvaluator.java
88.04% <0.00%> (+0.58%)
110.00% <0.00%> (ø%)

...snomed/datastore/index/taxonomy/PropertyChain.java
58.82% <0.00%> (+5.88%)
6.00% <0.00%> (+1.00%)

...om/b2international/index/es/log/Slf4jAppender.java
64.70% <0.00%> (+11.76%)
5.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

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


not working

I downloaded the script and launched it and it instantly closed then I copy-pasted the code and most of the import stuff just doesn't exist anymore

They do exist, but have been renamed
This code was written for Py 2.x.x and I think the creator left the project dead


Bug: Multiple Emoji description does not appear in the repo page

Describe the bug
Looking at https://app.opensauced.pizza/s/qrev-ai/qrev and noticing their description does not show
####open-sauced

####github

Steps to reproduce

Note https://app.opensauced.pizza/s/qrev-ai/qrev
Confirm description exists https://github.com/qrev-ai/qrev

I'm not sure if this is a timing thing and they may not have had a description before we indexed it or if it is the triple emoji thing. open-sauced-app shows up fine. Pandas also shows fine too.

If they updated it today after you visited the page, the page will be cached for two hours. Check a bit later to see if it's still an issue.

I just wanted to mention that the issue still exists. The page still doesn't show the description.

Screenshot

Network Request

Checking a new repo today and noticed the missing description - https://oss.fyi/middlewarehq/middleware

Hmm, if it has a description it should render in the OG image. I'll take a peek at this once some Lunch week stuff settles down.

Seems like any new repo index doesn't show a description. react-compiler open sourced yesterday.

Debugging this, and the API returns an empty string for the description.

Looking at the repo though (should have done this first 😅 ), there is no description.

Hmmm, debugging and MiddlewareHQ/middleware's description appears. Maybe there was a bug fix for this?

On beta it's all good.

On production it's missing.

Any bug fixes related to description for repo pages this past week @open-sauced/engineering?

Closing for now. If this is still happening after the Tuesday release, please reopen.


Rest Issue

Describe the bug Rest has several issues.

The rest is unable to send images.
TimeoutOverflowWarning:<PHONE_NUMBER>763 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
at new Timeout (node:internal/timers:168:17)
at setTimeout (node:timers:164:19)
at Module.setTimeout (/home/container/node_modules/@deno/shim-timers/dist/index.js:6:18)
at Object.handleCompletedRequest (file:///home/container/node_modules/discordeno/esm/rest/createInvalidRequestBucket.js:78:44)
at Object.sendRequest (file:///home/container/node_modules/discordeno/esm/rest/sendRequest.js:45:36)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.processGlobalQueue (file:///home/container/node_modules/discordeno/esm/rest/processGlobalQueue.js:6:5)
Is a error

Fixed


Wrong behavior on multiple cursor

VSCode Version: Code 1.19.2 (490ef761b76b3f3b3832eff7a588aac891e5fe80, 2018-01-10T15:49:04.682Z)
OS Version: Darwin x64 17.3.0
Extensions:

Extension
Author (truncated)
Version

erb
Cra
0.0.1

code-settings-sync
Sha
2.8.7

cobol
bit
1.7.6

code-runner
for
0.8.7

ruby-linter
hoo
1.0.0

Untabify
ili
0.0.2

ruby-rubocop
mis
0.5.0

Ruby
reb
0.15.0

vscode-icons
rob
7.19.0

vim
vsc
0.10.9

(3 theme extensions excluded)

Steps to Reproduce:

add multiple cursors on first column with shift-alt-cmd + (up or down)
when window scroll down or up  to add cursor on line above/below takes to much key repetition and editor start to flashes
have to wait while all key repetition are consumed.

Reproduces without extensions: Yes/No

@fascox Please open an issue against https://github.com/VSCodeVim/Vim


Ignore files that cannot be handled during the scan

When running a scan on a directory that contains files that cannot be handled, such as internal errors, or lack of permissions in a specific file in the scanned path, the scan fail and exit immediately.
I would like to ignore such files and collect them on the metadata of the scan itself instead.

@cxMiguelSilva what is your take on this one?
We did a small research and find our that majority of tools will log and skip such problems.
We can decide to have such logic "flag based"

The approach described seems good to me.
The files that failed to scan should be skipped and have a log message. Should a list of those files be present on the results files once the specified flag is used?


[CHORE][TESTS] Update config.yml

@RocketChat/android

Closes #ISSUE_NUMBER
Changes: [Add here what changes were made in this issue and if possible provide links.]
Screenshots or GIF for the change:

Closing this PR...


add version info in index file

What changes were proposed in this pull request?
Add index version info in index file, to support backward compatibility while further optimization
How was this patch tested?
Exists tests.

I'll merge this today.


Unable to use more than one BLE node in one flow

Version: 2.0.2 installed from https://flows.nodered.org/node/node-red-contrib-generic-ble
When adding one "Generic BLE in" or "Generic BLE out" type node to a flow, we have successfully read respectively written two Bluetooth Smart devices' GATT characteristics (one device is always read, one always written to).
However, when combining both BLE in and BLE out nodes in one flow, it appears that only one of them is operational, i.e. only one is reading or writing characteristics as configured.
We believe, the problem is associated with the fact, that in the ~/.node-red/flows.json there is always only one entry of type "Generic BLE" present, although several "Generic BLE in" or "Generic BLE out" nodes are defined, which all reference the same "Generic BLE" type node in their "genericBle" attribute.

Can you please post a flow so that I can reproduce the issue?
And if possible, can you try the latest version (2.0.3) of the node?

Trying another version is difficult for me, because I wouldn't know how/where to upgrade it. I'm not that familiar with node.js. But I can provide my flows JSON:

[
   {
      "id":"d7f065d7.718a38",
      "type":"tab",
      "label":"Flow 1",
      "disabled":false,
      "info":""
   },
   {
      "id":"266715cb.9b79ea",
      "type":"Generic BLE",
      "z":"",
      "localName":"alarmlight",
      "address":"87:10:dc:e9:6d:50",
      "uuid":"8710dce96d50",
      "muteNotifyEvents":false,
      "operationTimeout":"",
      "characteristics":[

      ]
   },
   {
      "id":"11f80c0c.815394",
      "type":"inject",
      "z":"d7f065d7.718a38",
      "name":"inject on",
      "topic":"",
      "payload":"{\"4001\":\"01\",\"writeWithoutResponse\":true}",
      "payloadType":"json",
      "repeat":"",
      "crontab":"",
      "once":false,
      "onceDelay":0.1,
      "x":920,
      "y":60,
      "wires":[
         [
            "e038f1cc.b60d3"
         ]
      ]
   },
   {
      "id":"ae75e723.a61678",
      "type":"inject",
      "z":"d7f065d7.718a38",
      "name":"inject off",
      "topic":"",
      "payload":"{\"4001\":\"00\",\"writeWithoutResponse\":true}",
      "payloadType":"json",
      "repeat":"",
      "crontab":"",
      "once":false,
      "onceDelay":0.1,
      "x":800,
      "y":120,
      "wires":[
         [
            "e038f1cc.b60d3"
         ]
      ]
   },
   {
      "id":"d1c5561b.aed528",
      "type":"debug",
      "z":"d7f065d7.718a38",
      "name":"",
      "active":true,
      "tosidebar":true,
      "console":false,
      "tostatus":false,
      "complete":"payload",
      "x":950,
      "y":320,
      "wires":[

      ]
   },
   {
      "id":"56e9af47.60507",
      "type":"function",
      "z":"d7f065d7.718a38",
      "name":"",
      "func":"var char2014 = msg.payload.characteristics[2014];\nvar sensor1 = char2014[0] + (char2014[1] << 8);\n\nif (sensor1 < 2700)\n{\n    return { \"payload\": {\"4001\":\"01\",\"writeWithoutResponse\":true} };\n}\n\nreturn { \"payload\": {\"4001\":\"00\",\"writeWithoutResponse\":true} };\n",
      "outputs":1,
      "noerr":0,
      "x":730,
      "y":220,
      "wires":[
         [
            "d1c5561b.aed528",
            "e038f1cc.b60d3"
         ]
      ]
   },
   {
      "id":"5b51a4a3.f956dc",
      "type":"debug",
      "z":"d7f065d7.718a38",
      "name":"",
      "active":true,
      "tosidebar":true,
      "console":false,
      "tostatus":false,
      "complete":"false",
      "x":650,
      "y":320,
      "wires":[

      ]
   },
   {
      "id":"e27ebb08.117d88",
      "type":"Generic BLE in",
      "z":"d7f065d7.718a38",
      "name":"",
      "genericBle":"266715cb.9b79ea",
      "useString":false,
      "notification":true,
      "x":420,
      "y":220,
      "wires":[
         [
            "5b51a4a3.f956dc",
            "56e9af47.60507"
         ]
      ]
   },
   {
      "id":"e038f1cc.b60d3",
      "type":"Generic BLE out",
      "z":"d7f065d7.718a38",
      "name":"",
      "genericBle":"266715cb.9b79ea",
      "x":1110,
      "y":220,
      "wires":[

      ]
   },
   {
      "id":"8b2e95a9.7684e8",
      "type":"inject",
      "z":"d7f065d7.718a38",
      "name":"",
      "topic":"2014",
      "payload":"",
      "payloadType":"date",
      "repeat":"",
      "crontab":"",
      "once":false,
      "onceDelay":0.1,
      "x":180,
      "y":220,
      "wires":[
         [
            "e27ebb08.117d88"
         ]
      ]
   }
]

Trying another version is difficult for me, because I wouldn't know how/where to upgrade it.
You can re-install it by one of the following methods:

Click menu icon(三), choose Manage palette and enter ble to filter this node. And you will find a button to upgrade it.
On the command terminal, cd ~/.node-red; npm uninstall node-red-contrib-generic-ble; npm cache clean; npm install node-red-contrib-generic-ble

Regarding the issue you reported, I'd say the device requires some delay to accept the following process. Can you please add delay node between the function node and Generic BLE out node?

Close the issue. You can reopen it if necessary.


Request for de-listing Sigma88 mods

I would like to request the de-listing of my mods from CKAN
the interested mods are:

Sigma Dimensions
Sigma Binary
Galactic Neighborhood
Sigma: OPM Recolor
Sigma: Jool Recolor
Sigma: PluronKhato
Sigma: Antennas
Sigma: OPM Tilt
Sigma: EveRecolor
Sigma: OuterSpaceComms
Sigma Binary - DunaIke

If you want to freeze them or remove them completely that's your choice.
Before I come back to ckan I want to see how the attitude evolves and I want to consider the possibility of managing my metadata myself.
The longer this request gets ignored, the less likely I am to come back to ckan in the future.
None of my mods will get any updates untill this has been solved.

I see you had time to add new mods to ckan but not time to respect your policy about de-listing.
I'll take care of that by myself if this cannot be achieved asking nicely
after all this is totally legal right?

Freezing is fine for me as well

I've updated the text of the issue
if anyone cares

Sorry, I missed this one. Doing it now.

You didn't include Eve Recolor. I'm going to assume you meant to include it.

All Sigma88 mods removed.

I did include the eve recolor (third from last)
you probably missed it because the identifier was different
no problems there, I've added a PR
thanks for accepting to delist my mods and good luck with your "wake up call" to the ckan team

@Sigma88  are you still against CKAN?

I'm not against CKAN as long as everything is handled without asking me to do stuff
however, my mods are not updated to 1.7 and I don't really know how long before I will get the time to work on them


Update package-biz-apps-org-list-template.md

Adding step 5 details for an unmanaged solution export

Added note on solution as unmanaged


Default renderer performance improved

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/table/GridColumn.java, line 61 [r1] (raw file):
Use create node instead of setting html, it's much faster.

Comments from the review on Reviewable.io

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/table/GridColumn.java, line 61 [r1] (raw file):
Done.

Comments from the review on Reviewable.io


Fastnlight: Watch WebToNative

Fastnlight requests the watch of the watch_keyword WebToNative. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

WebToNative has been seen in 3 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Infinite loop in Autoprefixer::fwrite_stream()

Getting  infinite loop in for loop , because  $fwrite value is 0.
System : Ubuntu 15.10
Node : v5.2.0
PHP : 5.6.11-1

http://php.net/manual/en/function.fwrite.php#96951


feature: Adds initial structure and requirements management

As described in #2 and #3 I decided to create a structure for our app.
What I have mainly done:

ran django-admin startproject ikita . on this repo in order to create the django structure.
ran rye init rye add django and rye sync in order to have the requirements file set up.

Closes #2 #3

You can reveiw the commits individually as they are from different "scopes".
The second commit contains the pre-commit configuration. This config will make sure that we do not send changes that are not compliant with the linting or formatting.
I would recommend you to test on your machine by:

Cloning the repository and checkout to this branch.
Install rye
run rye sync into the repository
run python manage.py runserver to check if the application runs


Filter breed options on species selection

🔗 Issue
No issue :eyes:
✍ Description
A small UX improvement I thought of.
When you select a species ("Dog" for example), we can reduce the number of options for the breed drop-down and only show dog breeds.
📷 Screenshots/Demos
screencast3.webm

Ah nevermind, I see this is being refactored in #1070


dev: clean up comments as discussed with the team

From @enitrat
imo we go from

/// ADDMOD operation.
/// Addition modulo operation
/// # Additional informations:
/// - Since:  Frontier
/// - Group: Stop and Arithmetic Operations
/// - Gas: 8
/// - Stack consumed elements: 2
/// - Stack produced elements: 1
/// # Arguments
/// * self - the execution context
fn exec_addmod(ref self: ExecutionContext) {

to

/// MULMOD operation.
/// (a * b) % N: integer result of the multiplication followed by a modulo.
/// All intermediate calculations of this operation are not subject to the 2^256 modulo.
/// If the denominator is 0, the result will be 0.
fn exec_mulmod(ref self: ExecutionContext) {

my big issue with comments is that you should never trust a comment, but code can be "trusted"


Also call onNodesChange when a selected node is clicked again

Please describe the feature that you want to propose
I want to allow users to de-select a (selected) node by clicking it again. Currently I have to use onNodeClick and check whether the clicked node is selected and if so, de-select it. I would like to move this logic into onNodesChange so that when a selected node is clicked again onNodesChange gets called with the following node changes:
{id: '$nodeID', type: 'select', selected: false}
Wdyt? Does this make sense?

Prop deselectOnClick or similar could make sense as a prop for <ReactFlow />

I like this idea. We will check it for the v12 release.

We decided not add a new prop for this specific use case. If you want to implement it, you can use the new updateNode helper like:
const onNodeClick = () => {
  if (selected) {
    updateNode(id, { selected: false });
  }
};


refactor($compile): added component text when asserting directive name

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Considering the Angular 1.5 introduction of components, when creating a component with an uppercase, the error thrown mentions a directive. This fix/update will provide the user information for when he has created an uppercased component (in general terms, not differentiating between directive and component).

What is the current behavior? (You can also link to an open issue here)
The error thrown includes the text: Directive name 'ThisExample' is invalid. The first character must be a lowercase letter

What is the new behavior (if this is a feature change)?
The error thrown includes the text: Directive/Component name 'ThisExample' is invalid. The first character must be a lowercase letter

Does this PR introduce a breaking change?
No.

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

Could you also update the contents of the actual error page: https://github.com/angular/angular.js/blob/master/docs/content/error/%24compile/baddir.ngdoc ?
Other than that, it LGTM :+1:

Here you go, @gkalpak.


Replace getCert.sh with Ruby code

getCert.sh can probably be replaced with just Ruby code in bb-server.rb

Regardless if the download is just ruby code the LetsEncrypt installer is bash so this does not seem worthwhile.


Files uploaded via web UI do not appear in files list immediately

After uploaded a file via the web UI, the file does not appear in the files list immediately. The page must be refreshed.
Environment: Sandstorm Oasis, Firefox 42, Fedora 23
Steps to reproduce:

Select Upload from the web UI menu
Select a file from the file browser, click "open"

When the upload finishes, the file list does not show the new file, but it will appear on refresh. Server returns a 200 "ok" response after upload. The console shows a syntax parsing ember-cli-live-reload.js:
It looks like the request for ember-cli-live-reload.js is actually returning HTML:
<!DOCTYPE html>

    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title>Davros</title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <base href="/" />
<meta name="davros/config/environment" content="%7B%22modulePrefix%22%3A%22davros%22%2C%22environment%22%3A%22development%22%2C%22baseURL%22%3A%22/%22%2C%22locationType%22%3A%22auto%22%2C%22EmberENV%22%3A%7B%22FEATURES%22%3A%7B%7D%7D%2C%22contentSecurityPolicy%22%3A%7B%22default-src%22%3A%22%27none%27%22%2C%22script-src%22%3A%22%27self%27%22%2C%22font-src%22%3A%22%27self%27%22%2C%22connect-src%22%3A%22%27self%27%22%2C%22img-src%22%3A%22%27self%27%20data%3A%22%2C%22media-src%22%3A%22%27self%27%22%2C%22style-src%22%3A%22%27self%27%22%7D%2C%22APP%22%3A%7B%22name%22%3A%22davros%22%2C%22version%22%3A%220.0.0+03670927%22%7D%2C%22contentSecurityPolicyHeader%22%3A%22Content-Security-Policy-Report-Only%22%2C%22exportApplicationGlobal%22%3Atrue%7D" />

    <link rel="stylesheet" href="assets/vendor.css">
    <link rel="stylesheet" href="assets/davros.css">

Oh, that looks like a packaging mistake on my part. ember-cli-live-reload.js should only be enabled in development mode and should never have made it into production. In fact, I see "environment: development" in the config here. I'll make a new point release that fixes it.

Could this be #19 as well? Everything seemed to 'work', but didn't update or display.

It's extremely likely. I'll push out a new version and test it with Edge as well.

Ok, I submitted v0.14.2 to the marketplace. If you'd like to test it ahead of then, you can do so here: https://mnutt.sandcats.io/shared/hNttoEKpQeWvGUCRmybPMReK9At3QjgZlOqpr54CIjd

Just started a new grain from the marketplace, and it's fixed. Thanks!