Named addresses not working with Dove run 1.6.0-86817ac

Hello!
Using TaoHe, consider the following file, and place it to scripts/:
script {
    use TaoHe::Errors;

    fun dummy_1() {
        assert(true, Errors::ownable_not_owned());
    }
}

It results the following error message while running dove run -v "dummy_1()":
error[E03002]: unbound module
   ┌─ /home/ville/projects/taohe/scripts/dummy.move:17:9
   │
17 │     use TaoHe::Errors;
   │         ^^^^^^^^^^^^^ Invalid 'use'. Unbound module: 'TaoHe::Errors'

error[E03002]: unbound module
   ┌─ /home/ville/projects/taohe/scripts/dummy.move:20:22
   │
20 │         assert(true, Errors::ownable_not_owned());
   │                      ^^^^^^ Unbound module alias 'Errors'

...while this works fine (also you can use the upstream dummy() to verify this):
script {
    fun dummy_2() {
        assert(true, 123);
    }
}

TaoHe namespace (and even TaoHe::Errors) is used multiple times in sources/, and is compiling fine. This problem (or some variation of it) seems to occur with dove test too.

This is still happening with 1.5.4, however, one should use the following file to replicate the error:
script {
    use TaoHe::Errors;

    fun dummy_1() {
        assert!(false, Errors::ownable_not_owned());
    }
}

The error message is also different now:
Execution failed due to unresolved type argument(s) (i.e., `--type-args 0x1::M:T` when there is no module named M at 0x1 or no type named T in module 0x1::M)

(Also, maybe dove prove is also experiencing the same problem?)

This problem is still present in 1.6.0, and now the test problem fixed in 1.5.6 resurrected in 1.6.0.
The test problem being:
┌── test_wrap ──────
│ ITE: An unknown error was reported. Location:
│ VMError (if there is one): VMError {
│     major_status: UNEXPECTED_VERIFIER_ERROR,
│     sub_status: None,
│     message: Some(
│         "Unexpected verifier/deserialization error! This likely means there is code stored on chain that is unverifiable!\nError: VMError { major_status: MISSING_DEPENDENCY, sub_status: None, message: None, location: Module(ModuleId { address:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001, name: Identifier(\"DiemAccount\") }), indices: [(FunctionHandle, 0)], offsets: [] }",
│     ),
│     location: Module(
│         ModuleId {
│             address:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001,
│             name: Identifier(
│                 "DiemAccount",
│             ),
│         },
│     ),
│     indices: [
│         (
│             FunctionHandle,
│             0,
│         ),
│     ],
│     offsets: [],
│ }
└──────────────────

Might open a new issue for this for clarity :slightly_smiling_face:


Improve navigator fragment performance

Even after the last update, the user who can't use GPS on the navigator fragment (ANR) is still unable to use it. I've only received one ticket for this, but performance improvements will benefit everyone.

[ ] Identify performance bottlenecks
[ ] Improve compass draw performance

Unfortunately Android Studio's performance monitor tool isn't working for me, I've made some changes to the most likely bottlenecks and will reach out to the user once that is released.


Typo while defining the ingression rate of self-serve scalable and legacy dedicated clusters

While reading the documentation to understand the different types of clusters provided by Event Hubs dedicated cluster, I found a typo in explaining the ingression rate of the legacy cluster. It is mistakenly written as a self-serve scalable cluster instead of a legacy cluster, because it makes sense that the legacy cluster has an ingression rate of 50 MB/s to 100 MB/s(based on its core definition).
Link to the paragraph - https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-dedicated-overview#legacy-clusters
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cda815fa-f05d-a1c7-3509-1ef8ba35203e
Version Independent ID: 79468aa7-09e1-3102-df04-44ed835f51c0
Content: Overview of Azure Event Hubs Dedicated tier - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-dedicated-overview.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

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

Hi @AnanyaGarg28
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@AnanyaGarg28
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#Please-close


MPT-7B: 'NoneType' object has no attribute 'bool'

Ran the following code to quantize MPT-7B, met the following error.
from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
model_path = "mosaicml/mpt-7b"
quant_path = './mpt_7b_awq'
Load model
model = AutoAWQForCausalLM.from_pretrained(model_path, cache_dir="./huggingface_transformers/")
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)
Quantize
quant_config = { "zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM" }
model.quantize(tokenizer, quant_config=quant_config)
Error
AttributeError                            Traceback (most recent call last)
Cell In[3], line 4
1 # Quantize
2 quant_config = { "zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM" }
----> 4 model.quantize(tokenizer, quant_config=quant_config)
File ~/SageMaker/vllm/lib/python3.10/site-packages/torch/utils/_contextlib.py:115, in context_decorator..decorate_context(*args, **kwargs)
112 @functools.wraps(func)
113 def decorate_context(*args, **kwargs):
114     with ctx_factory():
--> 115         return func(*args, **kwargs)
File ~/SageMaker/vllm/lib/python3.10/site-packages/awq/models/base.py:89, in BaseAWQForCausalLM.quantize(self, tokenizer, quant_config, calib_data, split, text_column, duo_scaling, modules_to_not_convert)
83 @torch.no_grad()
84 def quantize(self, tokenizer=None, quant_config={},
85                    calib_data: Union[str, List[str]]="pileval",
86                    split="train", text_column="text", duo_scaling=True, modules_to_not_convert=None):
87     self.quant_config: AwqConfig = AwqConfig.from_dict(quant_config)
---> 89     quantizer = AwqQuantizer(
90         self, self.model, tokenizer, self.quant_config.w_bit, self.quant_config.q_group_size,
91         self.quant_config.version, calib_data, split, text_column, duo_scaling, modules_to_not_convert=modules_to_not_convert
92     )
93     quantizer.quantize()
95     self.is_quantized = True
File ~/SageMaker/vllm/lib/python3.10/site-packages/awq/quantize/quantizer.py:36, in AwqQuantizer.init(self, awq_model, model, tokenizer, w_bit, group_size, version, calib_data, split, text_column, duo_scaling, modules_to_not_convert)
34 self.duo_scaling = duo_scaling
35 self.modules_to_not_convert = modules_to_not_convert if modules_to_not_convert is not None else []
---> 36 self.modules, self.module_kwargs, self.inps = self.init_quant()
File ~/SageMaker/vllm/lib/python3.10/site-packages/awq/quantize/quantizer.py:362, in AwqQuantizer.init_quant(self, n_samples, seqlen)
358     pass
360 # Update the layer kwargs with prepare_inputs_for_generation method
361 # that takes care of everything to avoid unexpected errors.
--> 362 layer_kwargs = self.model.prepare_inputs_for_generation(samples, **layer_kwargs)
363 # Pop the input_ids as they are not needed at all.
364 layer_kwargs.pop("input_ids")
File ~/.cache/huggingface/modules/transformers_modules/ada218f9a93b5f1c6dce48a4cc9ff01fcba431e7/modeling_mpt.py:300, in MPTForCausalLM.prepare_inputs_for_generation(self, input_ids, past_key_values, inputs_embeds, **kwargs)
298 if inputs_embeds is not None:
299     raise NotImplementedError('inputs_embeds is not implemented for MPT yet')
--> 300 attention_mask = kwargs['attention_mask'].bool()
301 if attention_mask[:, -1].sum() != attention_mask.shape[0]:
302     raise NotImplementedError('MPT does not support generation with right padding.')
AttributeError: 'NoneType' object has no attribute 'bool'

Hmm, a new error with MPT models. I fixed one not too long ago and had a successful quantization with this model and I see the last time they introduced a change was 2 months ago. Do you by chance have an old version of their model downloaded?

Currently not. Just tried to learn the basics of AutoAWQ then met this issue.

I got the same error.
Do you have any idea how to fix this? @TobyGE @casper-hansen
Traceback (most recent call last):
  File "/lustre/scratch/client/scratch/research/user/datnq9/AutoAWQ/convert.py", line 13, in <module>
    model.quantize(tokenizer, quant_config=quant_config)
  File "/usr/lib/python3/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/lustre/scratch/client/scratch/research/user/datnq9/AutoAWQ/awq/models/base.py", line 155, in quantize
    self.quantizer = AwqQuantizer(
  File "/lustre/scratch/client/scratch/research/user/datnq9/AutoAWQ/awq/quantize/quantizer.py", line 56, in __init__
    self.modules, self.module_kwargs, self.inps = self.init_quant()
  File "/lustre/scratch/client/scratch/research/user/datnq9/AutoAWQ/awq/quantize/quantizer.py", line 472, in init_quant
    layer_kwargs = self.model.prepare_inputs_for_generation(samples, **layer_kwargs)
  File "/root/.cache/huggingface/modules/transformers_modules/mpt-7b/modeling_mpt.py", line 300, in prepare_inputs_for_generation
    attention_mask = kwargs['attention_mask'].bool()
AttributeError: 'NoneType' object has no attribute 'bool'

Getting a similar error but with Llama and some Catcher class:
from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
AWQ_CONFIG = { "zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM" }
tokenizer = AutoTokenizer.from_pretrained(pretrained_model_name_or_path="meta-llama/Llama-2-7b-hf")
llama = AutoAWQForCausalLM.from_pretrained(model_path="meta-llama/Llama-2-7b-hf")
llama.quantize(tokenizer=tokenizer, quant_config=AWQ_CONFIG)

Traceback (most recent call last):
  File "/home/liamdodds/projects/quantization/quantize.py", line 20, in <module>
    llama.quantize(tokenizer=tokenizer, quant_config=AWQ_CONFIG)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/models/base.py", line 155, in quantize
    self.quantizer = AwqQuantizer(
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/quantize/quantizer.py", line 56, in __init__
    self.modules, self.module_kwargs, self.inps = self.init_quant()
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/quantize/quantizer.py", line 472, in init_quant
    layer_kwargs = self.model.prepare_inputs_for_generation(samples, **layer_kwargs)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 1256, in prepare_inputs_for_generation
    if past_key_value := getattr(self.model.layers[0].self_attn, "past_key_value", None):
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1688, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'Catcher' object has no attribute 'self_attn'

Has anyone made any headroom with this yet? Managed to get past AttributeError: 'NoneType' object has no attribute 'bool' by passing in the attention_mask manually, but have been running into a chain of other issues.

Getting a similar error but with Llama and some Catcher class:
from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
AWQ_CONFIG = { "zero_point": True, "q_group_size": 128, "w_bit": 4, "version": "GEMM" }
tokenizer = AutoTokenizer.from_pretrained(pretrained_model_name_or_path="meta-llama/Llama-2-7b-hf")
llama = AutoAWQForCausalLM.from_pretrained(model_path="meta-llama/Llama-2-7b-hf")
llama.quantize(tokenizer=tokenizer, quant_config=AWQ_CONFIG)

Traceback (most recent call last):
  File "/home/liamdodds/projects/quantization/quantize.py", line 20, in <module>
    llama.quantize(tokenizer=tokenizer, quant_config=AWQ_CONFIG)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/models/base.py", line 155, in quantize
    self.quantizer = AwqQuantizer(
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/quantize/quantizer.py", line 56, in __init__
    self.modules, self.module_kwargs, self.inps = self.init_quant()
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/awq/quantize/quantizer.py", line 472, in init_quant
    layer_kwargs = self.model.prepare_inputs_for_generation(samples, **layer_kwargs)
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 1256, in prepare_inputs_for_generation
    if past_key_value := getattr(self.model.layers[0].self_attn, "past_key_value", None):
  File "/home/liamdodds/projects/quantization/.env/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1688, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'Catcher' object has no attribute 'self_attn'

I got the same error.

facing this issue as well


@PrepareForTest(fullyQualifiedNames={...}) should support packages

From<EMAIL_ADDRESS>on November 14, 2008 15:01:19
This enables us to byte-code manipulate all classes in a particular
framework easily.
Original issue: http://code.google.com/p/powermock/issues/detail?id=74

From<EMAIL_ADDRESS>on January 29, 2009 01:59:29
Isn't this possible already?

From<EMAIL_ADDRESS>on September 19, 2009 14:44:41
Works, you can now use wildcards
Status: Fixed


Update to futures-preview 0.3.0-alpha.16

This includes a switch to new await syntax. Warrants a version bump as well.

Thanks so much! Do you know if the generators feature is still needed?

generators feature is not necessary any more. Removed it.


Trim dependencies

We definitely don't need

sklearn
seaborn
ipython

Need to trim before version 1.0
Also python3.7 is breaking for some reason ...

Looks like seaborn and ipython aren't used anywhere in the current codebase, although sklearn is (we're importing check_random_state from it). Weirdly enough the setup.py and conda_requirements files don't mention needing sklearn... I guess everyone has just been installing into environments where sklearn is already present :)
This relates to something I've been thinking of for a bit -- we should ideally try to make all of the dependency info consistent. There are (at least) three locations where this info is specified for Songbird:

setup.py
ci/conda_requirements.txt
conda-forge meta.yaml recipe

And all of these are slightly different in some ways -- e.g. setup.py has a different min numpy version than conda_requirements, and the conda-forge recipe explicitly mentions needing sklearn while the other two don't.
Ideally we should be able to make this info consistent somehow (would it be possible to just delegate everything to the setup.py file?), or at least periodically check in to make sure stuff's in sync.


train target-WEED detection model

downloading a random, but representative subsample of weeds (different species and different states locations)
start with 300 images (must have gray mat). @mkutu  will send a csv of images with mats. You can get them from the backup in SUNNY at /mnt/research-projects/r/raatwell/longterm_images3/weedsimagerepo/blobs/weedsimagerepo/
label using LabelIMG
use YOLOv8n (smallest model) for quick inferencing speed
test on hard images
inspect results thoroughly

@navjot-nangia

upload dataset to azure
push train3 results to Field-AnnotationPipeline as a new branch in data/models
add documentation to pipeline flow chart to Miro board (see slack for miro board link)
Experiment with various YOLOv8 sam predictor methods including auto_annotate, SAM("sam_b.pt"), Predictor, etc. looking at the tradeoffs between accuracy and speed.
Experiment with the auto_annotate method in yolo    - Use your trained detection model

parsing and inspecting results from various models

implement detection model in overall pipeline by using standard hydra config format that we've been using fro SemiF-AnnotationPipeline and Field-DataExploration


[infra] feat: jenkins docker build and publish integration

Still WIP, created for communication purposes, please don't merge!

superseded by https://github.com/NemProject/nem/pull/196


Requesting an invalid path returns a 200 response

$ curl -v https://earth-search.aws.element84.com/v0/invalid
...
< HTTP/2 200
< content-type: application/json
< content-length: 0

This will be fixed by #92


Figure out PSDesiredStateConfiguration.psm1

This is a follow-up from #1590
Context
Currently, we are using PSDesiredStateConfiguration 1.0.0-alpha01 nuget package to deliver PSDesiredStateConfiguration.psm1 in the final package, so DSC Configuration -> mof compilation can work on Linux.
https://github.com/PowerShell/PowerShell/blob/48d87842b112bf6c42f1f295d3007e3a2ee39803/src/powershell-unix/project.json#L59
It's sub-optimal.
PSDesiredStateConfiguration.psm1 is a huge file that contains dynamic keyword Configuration definition (that's what we need for compilation) but also DSC runtime code.
Proposition
We can try to extract the code that is needed for Configuration compilation from PSDesiredStateConfiguration.psm1 and replace nuget package by this separated, compilation-specific code.
cc @nitinbps @nanalakshmanan @johnkord

@PowerShell/powershell-committee reviewed this and the work item is to decouple DSC from PSCore eventually

@StevenBucher98 can this be closed now that PSDesiredStateConfiguration is in its own repo and shipped separately?


No pool statistics in UI after provisioning a volume with StorageClass "name": rpc error: code = Internal desc = Not enough space in pool PoolX

After adding a additional  FlashSystem Storage Class and creating PVC with it the PV creation failing due to "Not enough space in pool PoolX" error pool statistics in ODF UI are not showed properly:
Created PVC with too big PV size:
Events:
  Type     Reason                Age                  From                                                                               Message
  ----     ------                ----                 ----                                                                               -------
  Warning  ProvisioningFailed    13m (x15 over 41m)   block.csi.ibm.com_ibm-block-csi-controller-0_c89c8a35-02f6-4703-8ad3-558376e55e36  failed to provision volume with StorageClass "flashsystem-sc-pool6": rpc error: code = Internal desc = Not enough space in pool Pool6
  Normal   Provisioning          3m9s (x18 over 41m)  block.csi.ibm.com_ibm-block-csi-controller-0_c89c8a35-02f6-4703-8ad3-558376e55e36  External provisioner is provisioning volume for claim "openshift-storage/pvc-test05-pool6"
  Normal   ExternalProvisioning  80s (x167 over 41m)  persistentvolume-controller                                                        waiting for a volume to be created, either by external provisioner "block.csi.ibm.com" or manually created by system administrator

After some time ODF UI stopped showing capacity for FlashSystem

hi, @TymoT Please provide the cluster name and configuration for investigation?

waiting for reproduce. please hold the env after reproduced.

@shdn-ibm issue recreated, details in https://jira.xiv.ibm.com/browse/ODF-65

I managed to recreate this issue two times. The first time I thought the stats got back to normal after deleting too large pv (but the issue could as well dissapear on it's own). The second time the stats got back to normal after several minutes without any intervention. Than the issue didn't recreate in three trials at all. I tried once again today and couldn't recreate too. It looks this problem self heals on his own or doesn't recreate. I wold say this ticket could be closed @shdn-ibm unless you want to try something more.

ODF-65 was closed due to can't reproduce the issue, closed the issue, thanks.


Revert to fork start

Hi, thanks for pull request. But what is the purpose of the pull request?
I don't understand Revert to fork start 's purpose. Please tell us your purpose.


Support auto updating

That might be a really awesome thing to implement :smile: Would make the update process smooth as butter ^_^

Switched from NSIS from Squirrel. Will need to test autoupdate

https://github.com/tahnik/devRantron/pull/85


Possible Typo?

Didn't see a contact form or anything on the following website: http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell
I believe there is a typo at the bottom of this article; however, I'm probably wrong.  It seems the "Divergent history" graph references 'c2b9e' to the Testing branch, and '87ab2' to the master branch.  The console output below it however states the reverse.

It looks like this is fixed in the progit2 repository by changing the image to match the console output, in commit https://github.com/progit/progit2/commit/87254184fd3642148c284df68c59ae20751ca44a

what is it needed to have the image updated on the website also @peff ? I though the images were reused from the book repository

I'm not sure why we don't have the updated images (if we failed to import them, or if they're in the repo but need something special done with the asset code to be served on the site). Some discussion in https://github.com/git/git-scm.com/issues/515#issuecomment-279069880, but I haven't had a chance to dig deeper.

It was fixed last november. We haven't pulled since then.

I don't think that's it. The versions I pulled in #775 have several fixes. E.g., see https://github.com/git/git-scm.com/pull/775/files#diff-812dfc5fbd8656872fbf64fe9ffd8c57 for this case.
But the ones you added in https://github.com/git/git-scm.com/commit/4d71b81a565ad2f30a0aa5fc232d47c470330f65 don't have the fixes. So I think we actually were fixed for a while, but regressed recently.
The ones from #775 were mined out of the Atlas-generated zipfile (and as a result, you can see in the diff linked above that the resolution isn't quite as good). So I think we need to re-import, but do it directly into your new image hierarchy.

Fixed by #952.


Dynamic claim values

This PR, next to several bugfixes,
adds the option to specify desired values for ID token claims.
This is standardized per OIC Core Spec, Section 5.5.
Additionally, we also support requesting claims for an access token in a similar matter when requesting said token.
This behaviour is not standardized, but follows this IETF draft.
Other changes:

ENV is now immediately written to config (this also fixed some subtle bugs)
Added a script to execute all tests one after the other for convenience

Bugfixes:

Replaced wrong occurences of token with id_token
disable ID token creation when openid functionality is disabled
wrongly expected nil in /token
unconfigured logout redirect
Issue #18 : temporary mitigation by means of explicit OPTION request handling

I will rework the README and merge then


Can I use this

What is your question?
The title says it all

Go for it! Outta curiosity, what're you gonna use it for?

Our mod.
On Sun, 19 Dec 2021 at 06:09, ThermiteFe8 @.***> wrote:

Go for it! Outta curiosity, what're you gonna use it for?
—
Reply to this email directly, view it on GitHub
https://github.com/ThermiteFe8/FNF-Psych-Engine-Winning-Icons/issues/1#issuecomment-997271155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRYFG6XQCLDXQSBEMLBSNLURTMAJANCNFSM5KJ3WBEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Fair enough - I'd love to see it once it's finished!

Cool!
On Mon, 20 Dec 2021 at 09:11, ThermiteFe8 @.***> wrote:

Fair enough - I'd love to see it once it's finished!
—
Reply to this email directly, view it on GitHub
https://github.com/ThermiteFe8/FNF-Psych-Engine-Winning-Icons/issues/1#issuecomment-997470599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRYFGZHBSMJTWXWQKCG7ELURZKCTANCNFSM5KJ3WBEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Ill also give you credit


Fatal error when uploading the theme to Ghost

I get the following error. I checked default.hbs and found where "match" is used, but can't quite figure out what the problem is with it

Fatal error:  Templates must contain valid Handlebars
Oops! You seemed to have used invalid Handlebars syntax. This mostly happens, when you use a helper that is not supported.
See the full list of available helpers here.
Affected files:
default.hbs: Missing helper: "match"

Seems to only affect https://mindspun.io/ and not ghost.io

Hey @AlDjuric,
{{#match}} helper support was added in Ghost 4.19.0, and the custom theme settings support was added in 4.20.0. Make sure you're using the latest version of Ghost to get the new features working on your site.


Ensure that replacements are performed to the tail

If the match occurs on the last character, the replacement isn't correctly
processed.
This adds support for that scenario.
This seems to be working for my scenario, and I added a test to check (and all other tests still pass) but I'm kinda concerned that this will break something :-s
The issue is a double barrel of:

an infinite loop when the match finishes on the last character of the input, and the totalMatches is never incremented - and if the regex is non-global; it keeps matching (hence infinite)
and, the data in the tail is then outputted unchanged (ie the replacement isn't performed) because the end flushes tail - but it hasn't had the change applied in the lastPos check.

Now that I think about it, I think this will break the totalMatches counter when it's not the end (because it will have been incremented twice for the one chunk (because the tail is processed a second time)). Will go look at that :-)
Again, I think this may be a bad fix... As I wasn't sure the most logical way to do it... I had a very specific scenario to fix, and I think this may break more general, existing, usages.

Okay, I've added some code (and a test to match) to fix the totalMatches issue I mentioned above.

Thanks :).
I'll take a look at this tonight.

I think to fix this all we need to do is check that lastPos on lien 46 is greater than haystack.length.
if (lastPos > haystack.length && regexMatch[0].length < options.max_match_len) {
        tail = regexMatch[0]
}

Does that work?

Yeah, I think that looks good :-)
I'll close this PR and make a new one with that change and a test :-)


syslog drains added new tags to log messages that were not there before

the new agent is adding and sending a lot more data per line by adding a bunch of “tags” this was not announced as a breaking change.  for many of our customers this additional data can cause issues with the the licensing limits to the amount of log data being sent.  these tags were not included in the cf-syslog-drain release log lines but now are.  I see no way to turn them off to reduce this “noise” for our customers.   we really need to have someway to turn this additional tags information off to get the log lines looking exactly as they were with cf-syslog-drain-release
https://github.com/cloudfoundry/cf-syslog-drain-release/blob/develop/src/adapter/internal/egress/tcp.go#L109
How the rfc5424 messages were created in cf-syslog-drain (note no StructuredData!)
Code to convert this to the string being sent out is here …
https://github.com/cloudfoundry-incubator/rfc5424/blob/master/marshal.go#L148
VS the new code which is adding the structuredData even for the log lines.
https://github.com/cloudfoundry/loggregator-agent-release/blob/develop/src/pkg/egress/syslog/rfc5424.go#L146
We need to have the ability to turn this structured data off for log type messages or it should be turned off by default to match the previous functionality.

We'll be adding a per-drain opt-out for these tags, via a query parameter on the drain URL. There's been a number of commercial consumers who've already made use of this, so we can't turn it off by default, but we want to offer app developers/operators the individual choice between the extra metadata on these logs and saving bandwidth.
This opt-out will be added in version 6.1.0, which we will be releasing within the next two weeks.

@pianohacker can you please let us know when 6.1.0 is available and how to add the toggle to false?

@pianohacker - Can you please inform me when 6.1.0 is available and how to add the toggle to false?

@pianohacker : any news on this item? thx

There have been some delays on our end due to internal support obligations, apologies. The team is finishing delivery of the work, a release should be forthcoming very soon.

We've validated that this is working, and will be releasing it once #34 is also complete.

To clarify how this will work, it will be possible to opt out of tags-as-structured-data on app and aggregate drains by appending ?disable-metadata=true to the drain URL.

@pianohacker - When will this get released, any dates?
Once this is released will it take IBM 2 weeks to test and validate, correct?

@ranjith-rajaram The release of this work was pending the work on #34 , which is now done. I need to test that, then a release should be headed out the door shortly.

This has shipped in Loggregator Agent 6.1.0.


feat(lint): upgrade ESLint to 8.18

Use new rule added in 8.14 to detect constant conditions when working with ??, ||, and &&

rule will likely be added to eslint:recommended in ESLint v9

sounds good. are we passing it now? if not we should probably make changes to pass too

sounds good. are we passing it now? if not we should probably make changes to pass too

Yes, otherwise the CI checks would have failed. I also verified it would work, by adding expressions that should trigger it and running the linter locally.


change diff update to whole buffer

diff update has bug .back to update whole buffer

Eliminate update bugs caused by calculating the buffer area

Could you explain this part?🤔

nope. just a try. diff update has bug. now back to update whole buffer if has result .

Any idea why🤔?

diff return data like 240, 0, 241, 1 of start_a, start_a, start_b, count_b Didn't understand the rules. Causes buffer confusion after update.  So first go back and update the entire buffer. I think a benchmark is needed here. Because we need to know whether using diff is worth it. The time to update the entire buffer and the time to run the diff algorithm. It should be possible to benchmark large files

not sure. I remember this code will cause a format bug.
local t = {}

function t.a()
end

function t.b()
end

return t

Some limited benchmarking:
https://github.com/xiaoshihou514/guard-bench
Tested by manually toggling update methods and nvim -u init.lua

All files have the spaces changed to 8 spaces, in this case diffing is about 25% percent slower on average
(diff 8ms, no diff 6ms with big.js)

All files have " = " changed to "=", in this case diffing does better, but still does worse than not diffing
(diff 7ms, no diff 6ms with big.js)

Someone may be interested to do more rigorous and automated benchmarking to find the overall balance, but at this point I think there is really no point perfing the update method. big.js is 10k LOC, which is about what you can get when writing serious code, but updating buffer only takes less than 10ms, which I argue is pretty insignificant compared to the heavy lifting done by the formatter itself. Whether or not the file is big, diffing or not does not really change the user experience in terms of formatting speed, it is mostly determined by the formatter itself. And if diffing the buffer contents causes bug from time to time, I would vote for removing it.

@glepnir mergable yet?

@glepnir mergable yet?


keyToggle not working with modifier keys (mac)

Expected Behavior
robot.keyToggle("shift", "down") should hold down the Shift key.
Current Behavior
It doesn't hold it down long enough to modify the next keyboard event.
Seems similar to these issues: https://github.com/octalmage/robotjs/issues/132 https://github.com/octalmage/robotjs/issues/683
Possible Solution
Fix it?  Or don't.  What I really want is to do a is command+click, so if we implemented passing modifier keys to mouseClick and mouseToggle that would serve my use case.  This was brought up in https://github.com/octalmage/robotjs/issues/355 but the work-around there isn't working for me because keyToggle doesn't appear to work for modifier keys on my mac.
Steps to Reproduce (for bugs)
If I run this script, it types "a".
robot.keyToggle("shift", "down")
robot.keyTap("a")

But if I run this script, it types "A".
robot.keyTap("a", ["shift"])

This just does a regular click, not a shift+click.
robot.keyToggle("shift", "down")
robot.mouseClick()

Context
I want to be able to command+click.
Your Environment

RobotJS version: 0.6.0
Node.js version: v15.12.0
npm version: 7.6.3
Operating System: Mac OS Big Sur Version 11.6 (20G165) on a MacBook Air (M1, 2020)

Did it got fixed?


isomiR annotations wrong

The coordinates of the isomiR annotations prepared in the PREPARE workflow are (almost?) all wrong.
Example from the first six entries from file isomirs_annotation.bed generated by a test/test_workflow_slurm.sh run:
1	-2	-1	MIMAT0027619	.	-	.	miRNA	.	ID=MIMAT0027619;Alias=MIMAT0027619;Name=hsa-miR-6859-3p_5p-1_3p-1;Derives_from=MI0022705
1	-2	-1	MIMAT0027618	.	-	.	miRNA	.	ID=MIMAT0027618;Alias=MIMAT0027618;Name=hsa-miR-6859-5p_5p-1_3p-1;Derives_from=MI0022705
1	-2	-1	MIMAT0005890	.	+	.	miRNA	.	ID=MIMAT0005890;Alias=MIMAT0005890;Name=hsa-miR-1302_5p-1_3p-1;Derives_from=MI0006363
1	-2	-1	MIMAT0049032	.	-	.	miRNA	.	ID=MIMAT0049032;Alias=MIMAT0049032;Name=hsa-miR-12136_5p-1_3p-1;Derives_from=MI0039740
1	-2	-1	MIMAT0004571	.	+	.	miRNA	.	ID=MIMAT0004571;Alias=MIMAT0004571;Name=hsa-miR-200b-5p_5p-1_3p-1;Derives_from=MI0000342
1	-2	-1	MIMAT0000318	.	+	.	miRNA	.	ID=MIMAT0000318;Alias=MIMAT0000318;Name=hsa-miR-200b-3p_5p-1_3p-1;Derives_from=MI0000342

As a consequence, the isomiR quantification in the QUANTIFY workflow test fails. It was therefore disabled until this issue is resolved.
To do:

[ ] Fix the preparation of isomiR annotations (correct coordinates)
[ ] Reenable isomiR quantification in the tests.

I think we can close this, as we will not need this anymore with the new quantification design (see #7)


More useful header for Resource overview page

I notice the overview page has a title and then an explanation repeating the title (this was also the case in the older version of the IPT):

Can I suggest to replace this with instructions:

Note:

I removed the i button next to the title. I think that content is now partly replaced by the instructions. The text regarding DOI assignment should go into the registration section imo.
I removed Overview: from the title. I find the title of the dataset a better title for this page. In the sentence below it is indicated this is an overview page for the resource.

Good idea. I've change the subtitle, but left "Overview" as it distinguishes it from the published page and keeps it consistent with all the other editing pages.

@MattBlissett can we close this please?

Yes, thanks.


Sync markdown preview to current editor line

when adding images to MD docs I see the preview does not align smartly which the line I am editing
I am at line 17
I would like to see in the preview

instead I have to use the mouse to scroll the right panel manually and waste time

desired

add option: Scroll Preview Sync With Current Editor Line or similar

update the view of the preview with the current line in the editor

Using mushan.vscode-paste-image to copy/paste image, I am sure it does not affect the markdown preview ... but better to mention it

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

fyi
TobiasTao.vscode-md
has similar feature in the split view - it woks nicely

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Feature Request: Add a highlight option similar to flanking but for reach.

i think it would be relaly neat after v12 and everything that has died down to add a similar behaviour for flanking but for reach. with the rule that affects ignoring the first diagonal.
it would be cool to have a hotkey to open the squares available to a tokens reach so gms can quickly see the reach of their monsters.

Reach isn't assessed, which is a prerequisite for highlighting reach assessment.

would it be a waste of resources to do so for this feature?

Seems you want us to implement something like what tactical grid does, which does have the unfortunate side effect of swallowing our aura animations.


More detailed documentation on compiling packages?

Nuitka version, full Python version, flavor, OS, etc. as output by this
command.

1.7.10
Commercial: None
Python: 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]
Flavor: Debian Python
Executable: /usr/bin/python3
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 22.04.2
Version C compiler: /usr/bin/gcc (gcc).

How did you install Nuitka and Python

I used google colab as test enviroments, nuitka was installed with pip !pip install nuitka without a virtualenv.

Also supply a Short, Self Contained, Correct, Example

I need to distribute a python library that I maintained for others to use, and I want to use Nuitka to compile this package in order to get some degree of encryption (I do not want others to see the source code).  So I created an example module to test. This module is very simple structure as follows:
mymodule
└── funcs
    ├── __init__.py
    └── load.py

with load.py as
def print_consts():
    print(1, 2, 3)

I followed Use Case 3 - Package compilation, and succeesfully executed the following commands:
!python -m nuitka --debug --module mymodule --include-package=mymodule, which outputs:
Nuitka-Options:INFO: Used command line options: --debug --module mymodule --include-package=mymodule
Nuitka:INFO: Starting Python compilation with Nuitka '1.7.10' on Python '3.10' commercial grade 'not installed'.
Nuitka:INFO: Completed Python level compilation and optimization.
Nuitka:INFO: Generating source code for C backend compiler.
Nuitka:INFO: Running data composer tool for optimal constant value handling.
Nuitka:INFO: Running C compilation via Scons.
Nuitka-Scons:INFO: Backend C compiler: gcc (gcc).
Nuitka-Scons:INFO: Backend linking program with 8 files (no progress information available for this stage).
Nuitka-Scons:WARNING: You are not using ccache, re-compilation of identical code will be slower than necessary. Use your OS package manager to install it.
Nuitka:INFO: Keeping build directory 'mymodule.build'.
Nuitka:INFO: Successfully created 'mymodule.cpython-310-x86_64-linux-gnu.so'.

I renamed the so files as !mv mymodule.cpython-310-x86_64-linux-gnu.so mymodule_new.so and then failed to import it:
ImportError                               Traceback (most recent call last)
[<ipython-input-14-11b9f18f8646>](https://localhost:8080/#) in <cell line: 1>()
----> 1 import mymodule_new

ImportError: dynamic module does not define module export function (PyInit_mymodule_new)

It seems that some extra steps need to be done, but I can not find more details in the official documents. It would be great if anyone could provide more guidelines on this.
BTW, is it recommended to use Nuitka for my purpose (encrypting python source code)? I'm expecting one could import the .so file just as one would normally import the python module, or maybe I misunderstand how Nuitka works?

Renaming the module is not expected to work at all, rendering it invalid. Python enforces module name and filename of extension odules to align.
Module mode exposes your Python API, but of course not the source code. In Nuitka commercial we have some advice if this is what you need to do, to protect it somehwat from low skill attacks.

I will agree that the user manual can state it better though, I am adding these.  You need to move to another folder and have it in sys.path before the source or instead of it.
.. important::

   The filename of the produced extension module must not be changed as
   Python insists on a module name derived function as an entry point,
   in this case ``PyInit_some_module`` and renaming the file will not
   change that. Match the filename of the source code what the binary
   name should be.

.. note::

   If both the extension module and the source code of it are in the
   same directory, the extension module is loaded. Changes to the source
   code only have effect once you recompile.


E-Stop questions

Hello,
I have noticed that the machine always remains in E-Stop mode after removing the E-Stop code.
Could you please explain why this is the case?
At the moment I am not able to take the machine out of E-Stop mode via the graphical user interface (GUI) (without the E-Stop code in the HAL)
Greetings Mücke
demo2023_ini.txt
main_hal.txt
io_hal.txt

It's an internal function of LinuxCNC that must be connected by some means in hal.
https://github.com/jethornton/mesact/blob/master/mesact/src/libmesact/buildhal.py#L470


Easy single-container run scripts (enhancement #1903)

Note: DefectDojo is now on Python3 and Django 2.2.1 Please submit your pull requests to the 'dev' branch as the 'legacy-python2.7' branch is only for bug fixes. Any new features submitted to the legacy branch will be ignored and closed.
When submitting a pull request, please make sure you have completed the following checklist:

[ ] Your code is flake8 compliant
[ ] Your code is python 3.5 compliant
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/dd_migrations folder.
[ ] Add applicable tests to the unit tests.

I think it can be helpful to people to have this, it will require maintenance though.

Also prepared documentation here

I don't know if we really need another setup method. We already have bash, docker-compose and kubernetes/helm. For a demo we have the demosite. It will be very hard to maintain als these methods. I agree that we have so improve the documentation and maybe simplify the setup but I don't think another container solves this problem.

I have never had much of an issue just doing docker-compose up, so I am not leaning towards having an extra method either.
However, improving documentation could be it.
We're also working on having more regular and frequent releases, so it should ease the process too. I believe quite some frustration stemmed from the fact people had to use dev, which not everyone wants to do.

@alles-klar Maybe the demo app is cool but I see this caption for long time

And this is the first reason of my tryings to get quick and ready environment to put first data and show it in my company.
The next reason is that we don't use docker-compose. And the third reason is that when we was tried to run defectDojo in local K8s we've got tons of errors in nginx and the question "why we need 5 containers if we do not have such huge amount of vulnerabilities and services" :)
But if these scripts are off-top and there is no need with them the maintainers may feel free to close the issue :) I'll put it in my github library because they are really helpful for me and my environment.

I am also more leaning towards improving the existing docker(-compose) setup instead of a new single container variant. Especially since the single container scripts seem to involve multiple manual steps for initializing things.

@alles-klar Maybe the demo app is cool but I see this caption for long time

You are right, but there is a person working on it. Should be available soon.

And this is the first reason of my tryings to get quick and ready environment to put first data and show it in my company.
The next reason is that we don't use docker-compose. And the third reason is that when we was tried to run defectDojo in local K8s we've got tons of errors in nginx and the question "why we need 5 containers if we do not have such huge amount of vulnerabilities and services" :)

Docker is designed to have one process per container. One reason for this is scalability. But I agree that it is may a bit of overhead for a simple demo.
Did you deploy DefectDojo in K8s with the helm? Should be very straight forward. There is also a  	"KUBERNETES.md" which includes some documentation.

But if these scripts are off-top and there is no need with them the maintainers may feel free to close the issue :) I'll put it in my github library because they are really helpful for me and my environment.

Would be sad to waste your effort. Feel free to add your scripts here: https://github.com/DefectDojo/Community-Contribs

https://github.com/DefectDojo/Community-Contribs/pull/10


fix: BQ Sink retain column descriptions when Truncate option is set

JiraTicket: https://issues.cask.co/browse/PLUGIN-387

Do we see this problem after fixes for https://issues.cask.co/browse/PLUGIN-395?
We shouldn't be making any schema changes if "Update Table Schema" is false. Can you please add the check to make sure "Update Table Schema" is set to true here.


Change the links to absolute so they work on supermarket

Description
Changes the style of links to documentation in hopes it will fix the link display in supermarket.
Supermarket doesn't support relative link values.
Issues Resolved
#147
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

This change is

          1 Warning

:warning:
This Pull Request is probably missing tests.

  Generated by :no_entry_sign: Danger


Terminal tooltips render markdown if they span a range that includes colons

If the range returned from a TerminalLinkProvider spans a colon, it seems to cause the tooltip to render markdown instead of being a clickable link.
Normal:

But if I increase the returned length slightly to include the space/line/col, it does this:

The TerminaLink I'm returning looks like this:
{
	length, // This is the only property changing between the screenshots
	startIndex,
	tooltip: "Open file in editor",
});

Is this issue still? I'm available to work on it

@samrg123 yep, here are some code pointers:

Where all the link logic is held https://github.com/microsoft/vscode/tree/master/src/vs/workbench/contrib/terminal/browser/links
The hover widget used by the links https://github.com/microsoft/vscode/blob/master/src/vs/workbench/contrib/terminal/browser/widgets/terminalHoverWidget.ts

Thanks!

Sorry for the long delay. Finally got around to look into the issue.
Looks like the problem isn't from spanning colons, but actually from spanning spaces (or control characters 0x00-0x1f).
TerminalLinks get rendered via "marked.js" which parses markdown into html with the help of some regular expressions.
When you hover a link in the terminal a MarkdownString in the form of '[Name](PATH)' is sent to marked.js which only gets parsed as a link if 'PATH' matches the regular expression '[^\s\x00-\x1f]*'. Otherwise the string gets rendered as a paragraph element instead.
To fix this I'd escape the TerminalLink URI before creating a MarkdownString in TerminalLinkManager.ts::_getLinkHoverString, but wanted to run this by you guys to first to see if there were any other suggestions.

/duplicate https://github.com/microsoft/vscode/issues/110509


See Comments

Upcoming concerts now sort by date
Reviews sort by lastest entry
Likes update automatically
Error at the end of reviews was becaus eit was trying to query without going into the modal first, error line was deleted because it is not necessary.

Also switch search bar on header to button that take suser to /concerts

Last push was for the artists to be added along with the concert to the user's data, we can also create a new mutation to let the user add any artists they they haven't been to a concert to, but for now I think this works :)


[new] added new file MST Seating Plan.pdf

added new file MST Seating Plan.pdf]]
#18

nice pr
baaki agar hacktober reject karde isko spammy bolke to ek aur naayi daaldiyo meaningfull code ke saath


DS4v2/PS-Slim: Audio over USB

A little bird told me that the new DS4v2 controllers and the PS4-Slim support audio over USB.
If there is a Linux user with a DS4v2 can you please connect via USB(/BT), and for each send the output from 'lsusb -vv' and a copy of the HID descriptor file '/sys/bus/hid/devices/0003:054C:09cc.0006/report_descriptor'?
Cheers,
Simon.
PS: There is a kernel patch to make the DS4v2 work in the 'next' kernel, if you can't wait...
https://patchwork.kernel.org/patch/9365239/

ds4v2_bt_lsusb_vv.txt
ds4v2_usb_lsusb_vv.txt
report_descriptor_bt.txt
report_descriptor_usb.txt


fixing typo in record-create.spec.js

Just fixing this console.log message since it will be called for the Opportunity create test as well.

Thanks for spotting that @nancyheiss, do you mind signing the CLA so that we can move this further? That's a required step before we can merge any PR

Thank you! I reported the CLA issue to our OSS team, they are looking into so if you hit this issue again please let us know. Meanwhile, we have the green light to merge your PR! Thank you for your contribution


Small STORE registry fixes

See commit messages for details

Looks good, but do you need to make update to get the OSSL_STORE_R_LOADER_INCOMPLETE symbol picked up?

Thanks for the reminder.  Done!

Merged.  6f9c5062682c0f30d62af54b15ad6904e4dd8cb6 and 5ee407460b3b68aa4695f17cf8c43e0d07cb18a8

Thanks!


Issues with Determining the ISO3166 Country Code given a phone number, validation

In our app I'm given a phone number. I don't know what country it is from, but we require the end user to enter the E164 +xxx country code.
With this library I cannot seem to turn a "+1 314 246 xxxx" phone number into the value "US" nor "+1 787 246 xxxx" into "PR"
Our customers are all over the world, and I don't want a "Country Code Picker" either.
LibPhoneNumber can determine that the +1 314 246 xxxx is in the US, I'm not sure why this library does not expose it.
Help!
The big challenge here is that this library uses isValidNumberForRegion() as implemented in this library, in Java:
https://github.com/nashfive/phone_number/blob/d4ff262c4f91b2880f03a0d6072b5c7073772ad4/android/src/main/java/com/julienvignali/phone_number/PhoneNumberPlugin.java#L107
Now I have to know the region ahead of validation, but I don't know it, but it should be implied by the number, not requiring me to include the region.
It would be nice to be able to have access to a different .validate function to match the Google LibPhoneNumber options, such as .isPossibleNumber() and .isValidNumber() rather than the very specific .isValidNumberForRegion()
Without this flexibility and access to the rest of the functionality of libphonenumber, I'm struggling to accomplish reliance on the value that LibPhoneNumber provides!

At least for consistency with IOS, Android LibPhoneNumber should use isValidNumber() rather than isValidNumberForRegion()

I guess the option here is to fork and modify myself? This is disappointing that there's no response from the developer in a month. I see that it is being updated with the latest dependencies, but frustrating that no actual code changes or improvements are occuring.

@nashfive @deandreamatias @iamsahilsonawane Any chance you're willing to address this? I'm willing to make a pull request if you'll acknowledge it and review it and potentially accept it. I'm going to write the code either way.

Hi @ooglek
Sorry for delay answer.
I can review your code if you open a pull request.
I don't have time to enter and learn how the code is implemented. The is the motive that I don't start to fix bugs and develop new features. Also I don't has a lot experience to flutter plugins.
In another way, I really sorry for problems that this bugs can will be cause, but remember that this plugin is open source and we don't  receive money to work in it.
I believe that all contributors has some priorities to solved before develop this plugin.
Take a look to this discussion that I started to solve this and other problems
https://github.com/flutter-form-builder-ecosystem/flutter_form_builder/discussions/1038


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 5ff5874, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 8642 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 6f9b115 after 5 minutes.


Report a bug is not working

Describe the bug
The "Report a bug" button is not working on the documentation site
Steps to reproduce

Go to 'https://nextui.org/docs/components/button'
Click on any of the Live editors
Try to click on 'Report a bug'

Expected behaviour
It should send the user to the "Issues" project section
Screenshots

Environment / Context

Desktop or Mobile?: Desktop
Operating System: macOS
Browser and version: Chrome last version
Device: MacBook Pro

Additional info
This problem could be generated by the 'display: none' in the editor.tsx

Hello, this seems like something I'd like to work on. Could you please assign it to me, if possible?

Hi @TechManos yeah for sure, thank you!

Hi, If it's still open could you assign me this issue? When I look down at the project I think I found the fix.

Hi, @ibrahimtelman I going to assign this to you, thanks!
@TechManos I appreciate your interest in solving this bug but since @ibrahimtelman already know the solution and the users currently can't report a bug from the website I'm reassigning it to him


[CMake] Link static libraries as PUBLIC

Summary
I noticed a curious thing when generating graphviz files based on Swift's CMake: graphs do not show a dependency from swiftDriver to swiftBasic, even though swiftDriver links in swiftBasic.
Using a "standalone" build configuration such as the one I describe in SR-5778, I ran a cmake --graphviz= command in order to generate a graph, as per the CMake documentation here. The generated graph did not show a line extending from swiftDriver to swiftBasic, seemingly indicating that there is no dependency between these two libraries.

In fact, the graph shows no lines pointing to swiftBasic at all, as if no libraries depend upon it.
It turns out that, while swiftDriver does specify LINK_LIBRARIES swiftBasic in order to link it in, the libraries themselves are linked as INTERFACE.
According to the CMake mailing list:

When A links in B as INTERFACE, it is saying that A does not use B in its implementation, but B is used in A's public API.

This does not appear to be the case, however, with swiftDriver. One trivial example would be swift::Driver::printVersion, which invokes swiftBasic's getSwiftFullVersion.
This commit changes the link keyword to PUBLIC, which again according to the mailing list means "that A uses B in its implementation and B is also used in A's public API."
It also means that graphs now show a dependency between libraries; notice that in the graph below, an arrow extends from swiftDriver connecting it to swiftBasic:

Test plan
A clean build and test succeeds: rm -rf /path/to/build && utils/build-script --test

@jrose-apple, you mentioned someone had recently taken on some responsibilities with Swift CMake, could you point them here for their thoughts?

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 67ab638284e3eba819544f8efbcb6ac4de9bd882

@modocache Can you be sure to do clean tests with this.
@shahmishal Is there any possibility that we can get some sort of ability to force a clean after cmake builds. I am worried that cmake PRs are going to cause problems for other smoke tests.

@modocache I think that @jrose-apple was talking about @Rostepher.

@shahmishal Is there any possibility that we can get some sort of ability to force a clean after cmake builds. I am worried that cmake PRs are going to cause problems for other smoke tests.

Yes, I will see if I can add this by end of September.

@jrose-apple's description is a really accurate and good description of the issue. We do this in LLVM as well. Basically any dependency of a STATIC_LIBRARY target should be an INTERFACE dependency because on every platform I'm aware of static libraries don't actually link in their dependencies, instead the dependencies are required to be listed on the link line of whatever uses the static library.
It is also worth noting that CMake's graph generation generates the build dependency graph, which is not the same as the code dependency graph. You can have code dependencies (like libSwiftDriver depending on libSwiftBasic) which are not actually build dependencies because ar will not read libSwiftBasic when generating libSwiftDriver.

@llvm-beanz @jrose-apple Seems like something that should be written down somewhere. From what I understand @Rostepher is writing something up. @Rostepher, can you add this to your list of things to document?

👍

Thanks! = ).

Ah OK, interesting, thanks for the info everybody, very educational!

On top of this, our intra-compiler dependencies are still pretty messed up. We still have circular dependencies, which leads to having libraries specified multiple times in executable and unit test targets. I'm not sure I believe anything about our dependency graph without dealing with that.

@jrose-apple Is there a task for this? At my first glance it seemed like Swift's intra-compiler dependencies look very similar to Clang's. Are they both in need of improvement?

It is also worth noting that CMake's graph generation generates the build dependency graph, which is not the same as the code dependency graph.

@llvm-beanz That's a really good point, thanks. One bit I'm still not understanding, though: shouldn't the build dependency graph, even when using INTERFACE, show a dependency between something and swiftBasic? You mention that "ar will not read libSwiftBasic when generating libSwiftDriver", but wouldn't it read libSwiftBasic when generating the swift executable?

On top of this, our intra-compiler dependencies are still pretty messed up. We still have circular dependencies, which leads to having libraries specified multiple times in executable and unit test targets. I'm not sure I believe anything about our dependency graph without dealing with that.

@jrose-apple Is there a task for this? At my first glance it seemed like Swift's intra-compiler dependencies look very similar to Clang's. Are they both in need of improvement?

SR-1240 covers upward dependencies in swiftAST, but I don't know if we have anything for other libraries (or how bad a shape other libraries are in). I think the process is something like

Remove #includes that are layering violations.
Make the dependencies of static libraries sensible.
Make the dependencies of the tools, dylibs, and unit tests sensible (and order-independent).
Figure out some way to enforce it. I'm not sure if CMake already checks for explicitly making circular dependencies even in INTERFACE requirements, but we'd need some check on the built libraries to really get it to stick.

@modocache, yes, you should see swiftc depending on libSwiftBasic. I do see that in my generated ninja file lib/libSwiftBasic.a is a dependency of the link action for bin/swift. Unfortunately because CMake gets weird about handling interface dependencies I'm not really sure if it does the right thing or not in generating the graphviz dependency graphs. This was part of why I wrote my own implementation of generating graphviz in CMake... I still need to see if I can find those patches...

I do see that in my generated ninja file lib/libSwiftBasic.a is a dependency of the link action for bin/swift.

Oh cool, yeah, I took a look and I see that as well.

Unfortunately because CMake gets weird about handling interface dependencies I'm not really sure if it does the right thing or not in generating the graphviz dependency graphs. This was part of why I wrote my own implementation of generating graphviz in CMake... I still need to see if I can find those patches...

Yeah, I'll chalk this one up to some quirks in CMake graphviz, I guess. Please do send those patches my way if you can, I'd love to see them!
In any case it looks like this change isn't correct, so I'll close this pull request.

For anyone curious, here are the patches mentioned above: https://twitter.com/thegreatbeanz/status/903654270695653376


multi-gpu training

hello,
thanks for the brilliant project!
I want to know how could I train the model with multi-gpu on one machine. Looking forward to hearing from you, thank you in advance!

I am now having error like this: RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity


修复authentication types : NSURLAuthenticationMethodNTLM, NSURLAuthenti…

…cationMethodNegotiate, NSURLAuthenticationMethodClientCertificate, or NSURLAuthenticationMethodServerTrust 设置taskDidReceiveAuthenticationChallenge无效的问题
https://developer.apple.com/documentation/foundation/nsurlsessiontaskdelegate/1411595-urlsession

Thanks, but we won't be accepting this PR.


Update 'opentracing-cpp' to v1.4.2

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/JonathanO/hunter/build/1.0.7
https://travis-ci.org/JonathanO/hunter/builds/392794301

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4129
https://travis-ci.org/ingenue/hunter/builds/392889564?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.4131
https://travis-ci.org/ingenue/hunter/builds/392893652?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.22.16


Styling does not match KeyValue Field

The style on the index page does not match:

The style on form page does not match:

I can open a PR to fix this if you want.

Here's what it should look like:


Hue Entertainment mode does not resume after no signal

[x] I confirm that this is an issue rather than a question.

Bug report
Hue Entertainment doesn't re-enable after no signal/turning off input and then restarting again. I have to go into the Hyperion UI & open the LED Hardware page & click save for it to drive the LEDs again
Steps to reproduce
Setup Hue Entertainment, send some content.
Turn off input device/trigger black screen timeout
Turn input device back on
What is expected?
Hyperion should resume updating Hue Entertainment lights
What is actually happening?
Hyperion no longer updates the Hue Entertainment lights
System
Hyperion Server:

Build:       (HEAD detached at ffa2fd45) (Paulchen-Panther-69e9fa6d/ffa2fd45-1595517126)
Build time:  Jul 24 2020 15:55:19
Git Remote:  https://github.com/hyperion-project/hyperion.ng
Version:     2.0.0-alpha.7
UI Lang:     auto (BrowserLang: en-GB)
UI Access:   advanced
Avail Capt:  dispmanx,v4l2,framebuffer,qt

Hyperion Server OS:

Distribution: Raspbian GNU/Linux 10 (buster)
Arch:         arm
Kernel:       linux (5.4.51-v7l+ (WS: 32))
Browser:      Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36

I've also noticed a couple times I've had to go back into the Wizard & reselect the Entertainment Group for it to restart

@jaffacake Thanks for reporting.
It is a known issue.

I can see a PR mentioned this issue & has been merged? Does it fix this issue? I can help test if required. I've had my setup off as I'm waiting for this to be fixed.

@jaffacake The current issue that the Hue-Device does not resume after itself detected a black light scenario has not been fixed.
This is currently due to the fact that a proper, generic design would be that the input device detects missing input and then signals that scenario and lights are turned of. Not that every individual device would do such a checks.
With #960 some groundwork was done that in case there is no input stream in the priority list, the configured LED device will go off or on (if a new stream continues).
You might want testing it by disabling the "Platform capture" via the Remote Control. Take case that there is no background effect configured, plus disable switch off on black at your Hue device.
The Source selection list should be empty:

Note the LED device still shows "Enabled",as it is working. Only the state changed which is off.
Running in Debug mode, you should see the following log-line:
2020-10-17T14:55:33.274 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:541:handlPriorityChangedLedDevice() | No source left -> switch LED-Device off
Would be be good to better understand what is your scenario/setup when describing"Turn off input device/trigger black screen timeout"  in steps to reproduce.


checkSSLCert: 2.77.0 -> 2.78.0

Diff: https://github.com/matteocorti/check_ssl_cert/compare/refs/tags/v2.77.0...v2.78.0
Changelog: https://github.com/matteocorti/check_ssl_cert/releases/tag/v2.78.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 272891 run on x86_64-linux 1

1 package built:

checkSSLCert


Data Annotations

I cannot get default values to show up in the json output.

I EnableAnnotations() in the SwaggerGen but it did not affect the output.
I added the new annotations lib thinking that might help but it also did not affect the output.

Is https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/412 related?

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

ID: 14fce65f-1337-58cb-2193-8d8e0e62792d
Version Independent ID: 59222460-a971-e76e-4fe9-23d4d7d768ee
Content: Get started with Swashbuckle and ASP.NET Core
Content Source: aspnetcore/tutorials/getting-started-with-swashbuckle.md
Product: aspnet-core
GitHub Login: @zuckerthoben
Microsoft Alias: scaddie

https://github.com/aspnet/Mvc/issues/7563

@steveoh  looks like aspnet/Mvc#7563 was fixed in PR https://github.com/aspnet/Mvc/pull/7957
You could open an issue in  https://github.com/aspnet/Mvc
Create the simplest possible app the reproduces the problem and share on a repo.


Script changes

Overview
Changes to existing scripts, and adding gm-ci.sh script so we can work off of this repo.

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

Closing in favor of moving Rollkit scripts to Rollkit docs.


Toolbar is collapsed all the time, why ?

Hi i have a Problem with the Editors Toolbar and i can't figure it out how to solve it.
The Toolbar is always collapsed.

It should got enough width.  I don't know why it's happening.
It's putting everything in a class="toastui-editor-toolbar-group"

I use Editor in multiple Tabs and when i load the first Tab everything is ok, but when i go through the other Tabs the Toolbar is always collapsed. When i then open the console everything goes back to normal behaviour. We also forked your repo and edited  it so that it's still compatible with React: v16.
Summary
How can i solve my Problem ?
Version
3.0.0
Additional context
Here is my code maybe this helps:
`
import<EMAIL_ADDRESS>import { Editor, Viewer } from '@toast-ui/react-editor';
export interface MarkdownEditorProps {
onChange: (value: string) => void;
value: string;
}
export default function MarkdownEditor({onChange, value}: MarkdownEditorProps) {
const editorRef: any = useRef(null);
return (

<Editor
previewStyle="vertical"
height="400px"
initialEditType="wysiwyg"
initialValue={value || ''}
ref={editorRef}
onChange={(EditorType: 'wysiwyg' | 'markdown') => {
const markdownText = editorRef.current.getInstance().getMarkdown();
onChange(markdownText);
}}
usageStatistics={false}
toolbarItems={[
['heading', 'bold', 'italic', 'strike'],
['hr', 'quote'],
['ul', 'ol', 'task', 'indent', 'outdent'],
['table', 'image', 'link'],
['code', 'codeblock'],
['scrollSync']
]}
/>

);
}
`

@nku-bsw
The issue has been fixed in v3.0.3
Can you update to v3.0.3?

@js87zz  We updated the Version but there is still the same issue :/

@nku-bsw
Can you give me your example on the code sandbox?

@js87zz
If found the issue. After i installed "@toast-ui/editor": "^3.0.3" & "prosemirror-transform": "^1.3.2" is everything working. Before we had only "@toast-ui/react-editor": "^3.0.3" installed

@js87zz
https://stackblitz.com/edit/blue-react-app-stackblitz-xuxprf?file=pages%2FHomePage.tsx
I couldn't reproduce the Problem. But maybe i did something wrong while installing. I only installed "@toast-ui/react-editor": "3.0.3". Do i need to install something else too ?

@nku-bsw
There's nothing else to install. The problem has been solved?🧐

@js87zz
Yes it has been solved. Thanks for the help :)


Improve Auto unlock feature

There is an AUTO_UNLOCK_PASSWORD field which can be provided to automatically start the node on Alby Hub startup. However, this requires Umbrel and Start9 to allow the user to edit this env variable and is not enabled by default, which should be.
How can we improve this for self-hosted hubs?

Fundamentally, maybe Start9 and Umbrel should not even have unlock passwords. This needs more planning.
I still think this is an issue though e.g. with powercuts or restarts, it's harder for users to get Alby Hub back up and running.

After months of using Alby Hub on Start9 and Umbrel, I’ve rarely needed to enter the unlock password. Once the app is opened, the OS keeps it active, so re-entering the password is only required after a system reboot when I did restart Umbrel, logging in felt natural since all other apps also required re-authentication.
In summary, the unlock password hasn’t been a hassle, it’s only prompted after a reboot, which aligns with expected security behavior. This is based solely on my own experience, and I have not heard complains about this from umbrel or Start9 users so far

I personally have issues with this due to semi-frequent powercuts. But this can be fixed with a backup power supply.

Hi, I run Alby Hub with Docker on a home server that occasionally needs to reboot. I used this env variable to make Alby Hub come back online automatically, just like the other services, so I don’t have to worry about unlocking it manually.
In my specific setup this is a spending node with few sats in it, i don't need to protect it from being stolen or things like that, so this security feature (that is very important otherwise) is not needed for me.
I think this setup might be fairly common. I wouldn’t recommend enabling auto-unlock as the default, but it may be worth mentioning this thing and the related env variable in the Docker setup guide. It’s a bit unexpected behavior for a Docker container, and I only discovered it after receiving Alby’s email about unlocking the hub (by the way, thanks for doing these extra checks on our nodes :+1: )


WIP [vcpkg] Fix CMAKE_SYSTEM_PROCESSOR with UWP and Linux triplets

In case of UWP and Linux triplets, CMAKE_SYSTEM_PROCESSOR is not specified. It is empty.
For details this problems, Please refer to this comment https://github.com/Microsoft/vcpkg/pull/4635#issuecomment-435675204.
This pull request will set CMAKE_SYSTEM_PROCESSOR under UWP and Linux triplets.
If you want to explicitly specified CPU arcitecture, You can use VCPKG_CMAKE_SYSTEM_PROCESSOR in triplet files.

@alexkaratarakis @ras0219-msft Can I get your opinion?

Thanks for the investigation and the PR!
I tried to move as much "logic" as possible into the toolchains themselves and kept only the toolchain agnostic pieces in the main configure command. Note that Linux and Windows actually have different settings for CMAKE_SYSTEM_PROCESSOR (x86_64 vs AMD64).

Ok, this unfortunately resulted in some regressions after merging; I've temporarily reverted the PR but I'll investigate and let you know what I discover.


enable pbl

depends upon https://github.com/fastly/spidermonkey-wasi-embedding/pull/20

this landed in #628


Echos of past uc Shuttle's doors won't open

Echos of past uc Shuttle's doors won't open

Details
The door won't open with the community patch installed.
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Echos of past play

Fixed.   Seems to occur regardless of whether the community patch is applied or not.


Adding output with action result

I think having output variable with the check results would be useful to chain more actions, e.g. add a PR comment.
I could do a PR for it if you're open to having this feature.

Would this be a single Boolean? Or something like #30?

I was thinking about Boolean, I saw #30 and thought it might not be that easy to handle.
In the workflow I was doing, I wanted to add a comment with explanation on what titles are accepted.
Triggering of label change doesn't work when GITHUB_TOKEN is used, so a simple true/false result would help

Sure, if you could create a PR that'd be great. This should be backwards compatible right?

that's right, using outputs is optional and doesn't change how action is executed


treewide: use finalAttrs in packages maintained by @fgaz

Description of changes
Shouldn't change any hash.
I made this change in part to see if it can be automated easily. My findings:

The majority of packages were updated without problems with a vim macro
Most of the ones that failed could be fixed by extracting the undefined variables from the instantiation errors
Apply the change only to packages matching stdenv.mkDerivation, filtering out mkDerivations that don't support finalAttrs (qt5.mkDerivation, buildPythonApplication)
Sometimes rec is unused and finalAttrs isn't needed
Checking that the evaluation is the same catches eventual errors

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I fixed the conflicts, changed the commit messages, and will merge once CI is green. I applied what I learned in #293452


[API] Cannot create a pending review without body (but with a file comment)

Gitea version (or commit ref): 1.13.6
Git version: 2.25.1
Operating system: Ubuntu 20.04
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes :
https://try.gitea.io/fnetx/Documentation/pulls/126 / https://try.gitea.io/api/swagger#/repository/repoCreatePullReview (see screenshot for details)
[ ] No

Log gist: N/A

Description
Hello, while using the repo/CreatePullReview API it seems we cannot create a pending review with file comments only :
https://github.com/go-gitea/gitea/blob/ab77a24f18ae45248bd6c71778fe3bfacacf864f/routers/api/v1/repo/pull_review.go#L498

This also seems to mean that the review, event if "pending" is "published" and sends notifications and is visble in the history.
This behaviour is annoying and prevents a correct usage of file reviews via the API IMHO.
What I need to do is : be able to start pending reviews with file comments, and publish the review only when submitting the review with one of these statuses : Commented, Rejected, Approved.
Or is there something I'm doing wrong ?

Still relevant. Any new about this change?


[CICD] change workflow ip

@harborn thanks! I will fix in #97. close this.

@harborn I will fix this in #97


Menu only shows "Home" when opening a non-visible page

I used the one-page skeleton of Quark to create the page and made minimal adjustments.
I have the modular pages and its corresponding links to the sections in the top menu. I also created two non-visible pages for the new GDPR info and the German Impressum. These two pages can only be reached through hyperlinks in the footer. This does work well thus far. If I open one of these two pages, the menu in the header disappears and only the menu point "Home" is visible, which brings me back to the main page.
Is it possible to keep the main menu in the top, like it is on the main page, even if opening different non-visible pages?

The on-page menu is built as it loops over the modular sub-pages.  These sub-pages don't exist in the context of other pages, hence they are not visible.
You can modify the navigation twig and customize it to do whatever you want, even show static links.  Or you could get the collection for the home page's modular sub-pages in the navigation twig and iterate over it.
Really this is a more of a customization question rather than a feature that should be in the default theme which we're keeping intentionally minimal and clean.

Ah yes, totally makes sense. Thank you!


Gsoler dhc pserver relay agent

#assign: @robinharwood, @Xelu86
@robinharwood @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi, @gswashington. You're going to see a bunch of outdated comments from when I was directly commenting before we figured out the permissions issues for pulling your working branch to my local. There's only one comment that's currently relevant, and you should be able to see it in the Files tab.


config --shell adds errant \ characters

CLI version 3.30.3.
We have some config vars with + characters in them. heroku config returns the correct value of the variables to us, however heroku config --shell is adding extra \ characters to the front of + signs when it reports the values.
$ heroku version
heroku-toolbelt/3.30.3 (x86_64-darwin10.8.0) ruby/1.9.3
=== Installed Plugins
heroku-repo

$ heroku apps:create
Creating blueberry-crisp-4373... done, stack is cedar-14
https://blueberry-crisp-4373.herokuapp.com/ | https://git.heroku.com/blueberry-crisp-4373.git

$ heroku config:set TEST_VAR=+tQ405404230 --app blueberry-crisp-4373
Setting config vars and restarting blueberry-crisp-4373... done, v3
TEST_VAR: +tQ405404230

$ heroku config --app blueberry-crisp-4373
=== blueberry-crisp-4373 Config Vars
TEST_VAR: +tQ405404230

$ heroku config --shell --app blueberry-crisp-4373
TEST_VAR=\+tQ405404230

that is expected behavior since it escapes them with shellescape http://ruby-doc.org/stdlib-1.9.3/libdoc/shellwords/rdoc/Shellwords.html#method-c-shellescape

That's rather surprising, at least to me. What is the expect use-case for heroku config --shell with these escape markers? Is it only for scripting?
I have been using heroku config --shell as a convenient way to print config vars formatted for copy-pasting into a foreman .env file. But the way they are printed currently is incorrect for this workflow.

It's designed to be used as Unix shell code, so yeah, scripting. I'm a little surprised the .env file doesn't work in this case. @ddollar does the .env file work with escaped shell characters?

They seem to be interpreted literally:
$ cat .env
TEST_VAR=\+4050

$ foreman run irb

>> puts ENV.fetch("TEST_VAR")
\+4050
=> nil

>> ENV.fetch("TEST_VAR").chars
=> ["\\", "+", "4", "0", "5", "0"]

@csuhta I think I've resolved this issue for you but in a different way. These shouldn't have been escaped if you were creating these files by doing something like heroku config -s >> .env. This is resolved in #1518

I just tried with 3.33.0 and it works great for this. Thanks!

I'm not satisfied with this solution at all :( -- if you do it this way, there's no way to get the escaped versions programmatically, which kind of defeats the purpose of having them unless you are just going to copy/paste it from your terminal.
Furthermore, the unescaped output often contains characters (such as \n) which wreck .env files so you can't safely use the unescaped one either.

can I ask why you want to pipe the escaped version? You make a good point about \n. I just noticed that is kind of weird for most of the config commands.


π

This is issue #31415 and I wanted to claim it. Sorry for the noise.

Revisit after 282,744 other issues

You should have thought of this back when TS 3.1 was released.  You folks are not on the top of your game.

I know, I've failed you. 😢


I bought this vpn after buying it with crypto time was zero, 10 minutes passed, nothing happened, I closed the program, opened it again, the first page of the program appears again.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Logs
Attach logs (app, node, supervisor) to the issue. Where to find the logs: https://github.com/mysteriumnetwork/mysterium-vpn-desktop#logs
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 10]
App Version [e.g. 4.1.0]

Additional context
Add any other context about the problem here.

There was no error. It got stuck on this page while I had paid. I closed the program and opened it again, it comes back from the first page of the program. https://drive.google.com/file/d/113VTAPAfkokHHcFTjrhAuHfToFdDWrVW/view?usp=share_link

Could you please send us your payment receipt here? What was the payment method used? Please share this info with us so we can continue resolving the issue. Thanks!

Latest update from Coingate reveals refund was already processed. I will close this issue for now and in case user reports otherwise I will reopen the issue
Hi,

Thanks for contacting CoinGate!

I have checked this order and can confirm that refund was requested by the client and issued already.

Please check the confirmation here: https://pay.coingate.com/invoice/ad8d6ad4-0ac2-4336-9deb-609b75036f8e

Let me know if you have any other questions.

Regards,
Emilia D.

I can not connect to any connection(node)!!!!
this is the error:
Failed to connect .could not create p2p channel during connect.p2p dialer failed. could not dial p2p channel could not ping peer too few connections were built

this is the error:
Failed to connect .could not create p2p channel during connect.p2p dialer failed. could not dial p2p channel could not ping peer too few connections were built


Short solution needed: "Get affected rows with PHP PDO" (php-pdo)

Please help us write most modern and shortest code solution for this issue:
Get affected rows with PHP PDO (technology: php-pdo)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Get affected rows with PHP PDO


New version of Google Maps SDK for iOS available

Use case

When instantiating the GoogleMap widget, I see this warning message on my console:
Google Maps SDK for iOS version: 2.7.30514.0
New version of Google Maps SDK for iOS available: <IP_ADDRESS>

Proposal

Please update the dependencies.

I just found this article that explains Upgrading to Google Maps SDK for iOS 3.0:

https://medium.com/flutter-io/google-maps-and-flutter-cfb330f9a245

Adding this documentation to this package would be nice.

Do we have any updates on adding this to the documentation?

I have found solutions for this, I have some problems
with termial
->. pod repo remove trunk
-> pod install
-> pod update
here I have found
https://stackoverflow.com/questions/58409725/Сocoapods-trunk-url-couldnt-be-downloaded
It's worked for me

I see the message in the console. Verified using latest master and latest plugin version.
Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
Running Xcode build...
Xcode build done.                                           12.7s
Debug service listening on ws://<IP_ADDRESS>:53572/FoJuYaDZXBk=/ws
Syncing files to device iPhone 12 Pro Max...
Google Maps SDK for iOS version: <IP_ADDRESS>
New version of Google Maps SDK for iOS available: <IP_ADDRESS>

Closing as obsolete; the plugin currently doesn't pin a version, which means the newest version compatible with the app's minimum iOS version will be used.


MacFreeRDP/MRDPView.h' file not found

Releated pull request for master:
I have encountered a new problem. The MacFreeRDP build of the xcode project created by xcode.sh is successful but the archive fails with the error AppDelegate.h MacFreeRDP/MRDPView.h' file not found under MaFreeRDP

MAC OS version is 11.6.7 and Cmake version is 3.23.2
Freerdp source code is tag 2.7.0 ，xcode version 13.2.1
cmake command line
cmake -D "CMAKE_OSX_ARCHITECTURES:STRING=x86_64" . && make

Just tried a compile on an m1 and x86_64 mac, works.
Please check:

You start from a clean checkout (git clean -xdf)


ObjectEncoder and ObjectDecoder

java nettyserver used ObjectEncoder and ObjectDecoder
The client is developed using .net
how  impl in DotNetty support to send and receive objects.

The ObjectEncoder/ObjectDecoder in Netty has been deprecated. Therefore, it will not be implemented.


Print stacktraces to files, instead of stdout

I pushed a few commits to:

not mess with today's ScalaCli.scala much in the diff
try to use a sensible workspace value when possible (only with the run command, the other commands need to be updated too)
keep the exception causes in the log (quite important, many times, the relevant exception is in a cause)
take into account verbosity (keep throwing in the current console if verbosity >= 2, only with the run command too, the other commands need to be updated there too)

Feel to squash them / push force on this branch.

@alexarchambault so should I squash and merge it as is?

so should I squash and merge it as is?

Just pushed one more commit. I guess it can be squashed-and-merged, yes.

We need to report the changes in Run.scala (setting things in CurrentParams) to the other commands, prior to merging this.

I had to rebase due to conflicts

@tpasternak Just pushed a commit to factor -v out of LoggingOptions, so that it can be added to commands without adding all the other logging options (which would be unused).
Good to merge for me, if that's fine for you (and the CI is green).

Seems you discarded one of the commits I had pushed, factoring -v / --verbose, so that we don't add all the logging options when they're not needed.
I just pushed my version of this branch here, its last commit is missing in particular.

Right, I rebased and squashed, as the history became quite complex


RDKTV-12796:Move iarmmgrs oem patches

Reason for change: mfr changes as generic
Test Procedure: mfrmgr test cases
Risks: Create None
Signed-off-by: Rahamataunnisa shaik<EMAIL_ADDRESS>

 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.Rahamataunnisa shaik seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.Rahamataunnisa shaik seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing older PRs. Pls rebase and create new PR on latest sprint/main branch if still required.


Error handling

Right now my nicegist links takes a veeery long time to load before I'm redirected to the nicegist front page.
I'm guessing this is a github api issue. If not, you'd probably be cut off immediately with a 509 bandwidth exceeded or something similar. Though the github status page claims everything is ok. :-/
But the actual error handling could be better. You should probably render a friendly error-message like "Gist API did not respond" when the request times out.

Hey @fuzzy76, I can not reproduce the load time issue. But I hope this commit will help.
I set a timeout for XHR requests. If they take longer than one second, I'm checking the GitHub API status to render a more helpful error message to the user.
Since I can not reproduce the issue, could you please check if that works out for you?

Raised timeout to 1500 ms.

Oh... The old style /?id= type URL causes what looks like a timeout. If I change to the new style, it works.

Nope... Even that is wrong. I used the old address, https://eyecatchup.github.io/nicegist/GIST_ID so my old bookmarks stopped working. I'll update them accordingly. :)

Ok, closing it.


Allow to publish extensions that use proposedApi when using pre-release publication mode

Context
Proposed API
There is a way to allow extensions to use proposed API by using Insiders.
At first there was like a global opt-in for the extension and now it's a per-feature switch with enabledApiProposals product.json property that is now mapping dedicated API after https://github.com/microsoft/vscode/issues/131165
But we can't publish extensions (except Microsoft and some partners) on the marketplace that are using proposedApi
https://github.com/microsoft/vscode-vsce/blob/f4a82648f91c0667ec2c23d0250013ed20daeb57/src/publish.ts#L106-L108
Pre-Release extensions
https://code.visualstudio.com/updates/v1_63#_pre-release-extensions
With November/1.63 release there is now a way to publish prerelease of a given extension.
Feature wanted
Proposed API goal is to let developers experiment stuff that may or not come in upcoming versions of VSCode into the stable API.
And then developers can provide early feedback.
And pre-release allow to get users testing upcoming feature.
I think it's a perfect match and then I would like to be able to use proposedApi in pre-release builds.
Then, users are aware that some stuff can be broken anytime as they're using a pre-release and not a final version of an extension.

I do understand the desire but this is something we currently have not planned.
Proposed API is a way for extension authors to give feedback to us. I do see that there is (little) value in gathering that feedback through users of extensions that use proposed API but I don't believe it out-weights the downsides: There is no guarantee that a pre-release extension cannot be popular and widely successful (either because a proposal hasn't changed in a long time or simply because a popular extension goes pre-release for the sake of using a particular proposal). Having a popular extension that uses proposed API is a huge burden on us: proposed API will change and said extension will break. Such breakage is bad and users generally don't differentiate on why something broke - the extension doesn't work usually means that vscode doesn't work (that's like a bad display driver that crashes your OS). Now, the alternative to breakage is coordination on proposed API changes. This is the model that we use for our internal and MSFT extensions and it comes with massive overhead. Coordinating that with an even larger group isn't feasible.

A sad consequence of this (from an extension author's perspective) is that "blessed" MSFT extensions can benefit indefinitely from proposed API while other extensions are hamstrung. In some cases proposed APIs that IMO are essential have made absolutely no progress towards finalization for years. It is both frustrating and dispiriting.
Maybe the team could set a time limit on proposed APIs, after which they must either be finalized or else removed (and no longer available for "blessed" extensions either).


[Feature Request] Consider supporting option to fill files with specified data

Consider an option (e.g. --fill-byte) that would fill files with the specified byte vs. random bytes.  This would:

potentially make generating the files even faster
make the file content deterministic and compressible

I have zero issues with the speed of ftzz as is.  It's AMAZING!  I'm requesting this for #2, but definitely curious about #1
Thank you!

I have zero issues with the speed of ftzz as is. It's AMAZING!

Thanks! :)

So is the primary goal compressibility? To be clear the file content is deterministic in the same sense as everything else in this repo: the same command will generate the exact same bytes in the same file. This is verified here: https://github.com/SUPERCILEX/ftzz/blob/eb96336ad46592a488c26947d082709c1f073aa7/tests/generator.rs#L301-L305

You are spot on.  The repeatable nature of the generated data is awesome!  Compressibility is the primary goal.
Thank You!

Sounds good. Can you share a little bit more about your use case? Is the idea that you're zipping up the generated files and sending them somewhere? I just want to make sure I fully understand the motivation behind compressibility.

I appreciate you asking!  I want to be able to generate millions of files/directories consuming many (uncompressed) TB/PB, but its footprint is much smaller on a compressed filesystem and/or its compressed backup is much smaller.  So, I'm looking for a huge test dataset that doesn't consume huge amounts of storage.
Thanks much!

Alrighty, seems reasonable to me. :+1:
I should be able to get to this within a few weeks. Though if you want to take a stab at this, let me know and I'll try to clean up some shitty code + add a bit more docs.

I did tinker with this a bit, but the Rust learning curve is a bit steep for a primarily python guy that hasn't touched a statically typed language in many years :-).

No worries, I should be able to get to this soon. :)


add: iter method to iterate with params

Summary

Add an iter method that accepts arguments to allow iterating through results.
Currently, there is no way to iterate providing args to bind to.
Symbol[Iterator] works for ones without any args.
This PR exposes the method as iter that works both with and without bind values.

Why
Without this, there's no way to iterate on large results efficiently. The current all methods and other variants always have to return the full query, which is not an ideal way to scan through the DB.
Alternative approaches

The current Symbol[iterator] works for items without bind params, but any bind params will be reset on execution. Can just remove the resetting, but in that case, it breaks compatibility and older behavior, since it's the responsibility of the user of the prepared statement to ensure it's also reset and bound.

This also breaks backwards compatibility as bound statements are no longer iterable. This worked before
const [row] = db.prepare(`SELECT sqlite_version() AS ver WHERE ver > ?`).bind(0)

But now it throws with:
error: Uncaught (in promise) Error: Statement already bound to values
    if (this.#bound) throw new Error("Statement already bound to values");
                           ^
    at Statement.#bindAll (https://jsr.io/@db/sqlite/0.12.0/src/statement.ts:376:28)
    at Statement.iter (https://jsr.io/@db/sqlite/0.12.0/src/statement.ts:703:18)
    at iter.next (<anonymous>)
    at file:///<snipped>.ts:4:8
    at eventLoopTick (ext:core/01_core.js:175:7)

Ohh, there's a little detail I missed here - it's always resetting binding values. I'll push a fix and make a new release