Issues with set_peft_model_state_dict, dictionary not properly updating.

So in the previous peft version, before the recent adalora changes, set_peft_model_state_dict returned a wrapped model object.
Now, it appears to function as a mutator (returns None). So I changed my code appropriately.

I am trying to further fine-tune an existing lora adapter that I have. The problem appears to be that it's not actually updating the state_dict at all, because when I resume training, not only are all the training parameters off, but I also have a ton of dict keys that are mismatched.

and

Epoch should be 6, but thinks it's 1.3, etc
Retraining the adapter from scratch does nothing. Does anyone have any ideas?

@ElleLeonne
I am checking the set_peft_model_state_dict diffs and the AdaLora changes only added an if condition that should not have broken anything as far as llama lora training goes.  I'm getting more and more confused on all the peft/transformer changes recently that has broken llama code in multiple places at once.
def set_peft_model_state_dict(model, peft_model_state_dict):
    """
    Set the state dict of the Peft model.
    Args:
        model ([`PeftModel`]): The Peft model.
        peft_model_state_dict (`dict`): The state dict of the Peft model.
    """
    if model.peft_config.peft_type == PeftType.ADALORA:
        rank_pattern = model.peft_config.rank_pattern
        if rank_pattern:
            model.base_model.resize_modules_by_rank_pattern(rank_pattern)
    model.load_state_dict(peft_model_state_dict, strict=False)

    if model.peft_config.peft_type not in (PeftType.LORA, PeftType.ADALORA):
        model.prompt_encoder.embedding.load_state_dict(
            {"weight": peft_model_state_dict["prompt_embeddings"]}, strict=True
        )
    return model

https://github.com/huggingface/peft/blob/382b178911edff38c1ff619bbac2ba556bd2276b/src/peft/utils/save_and_load.py#L65

Wait, why does this function return a model object? That wasn't there this morning when I was trying to debug...
The plot thickens...

Hello @ElleLeonne,
We made recent changes to support multiple adapter inference and training. As such, there was a need to load the save adapters with their params in frozen mode without, that explains the  all the training parameters off. To have the trainable params of adapters when loading, either set inference_mode=False in the PeftConfig or use from_pretrained method with param is_trainable=True.
I'm unable to reproduce any errors. Below are the screenshots of the code snippets along with the outputs, everything is working as expected.

Please provide us with minimal reproducible scripts that we can execute to further deep dive and resolve the issues, if any.

@ElleLeonne, we have tried our best to not have any breaking changes, although it might be the case that some changes are breaking ones, e.g., the set_peft_model_state_dict  being a mutator.

@pacman100
Ah, I see. You're just loading the adapter. I can do that just fine.
My issue comes from attempting to load the checkpoint weights, and continue training from that point.
I'll work on trying to get something reproducible together, but maybe that sparks a thought in the meantime.

@pacman100
Alright, I've managed to reproduce it in slim form. Code is here

I trained a generic adapter just to produce something, then attempted to load the weights of the checkpoint file to resume training.
And here's your PeftModel version.
Both result in the weights issue.

I'm going to work on trying to find a way to merge the weights, but if I don't provide an update, assume I haven't figured anything out yet.

Also gonna rope in @AngainorDev who made the original continue from checkpoint script.
I realize you said to ignore a "missing keys" error, but the unexpected keys thing seems to be a product of the recent update, and the weights don't appear to be merging right as a result.

@ElleLeonne
Did you try with  set inference_mode=False in the PeftConfig ?
line 25 of your minimal code, try adding add peft_config.inference_mode=False

I just got home and tried it, same issue with unexpected keys. Both on my minimal script, and my live implementation

I just got home and tried it, same issue with unexpected keys. Both on my minimal script, and my live implementation

The "def get_peft_model_state_dict" is not updating as well, because the last line
"to_return = {k.replace(f".{adapter_name}", ""): v for k, v in to_return.items()}"  in /peft/utils/save_and_load.py
overwrites our adapter_model.bin. Comment it, then it works fine.

Let me know if this PR fixes the issues: https://github.com/tloen/alpaca-lora/pull/359

Let me know if this PR fixes the issues: tloen/alpaca-lora#359

It's fixed now. Just test it.

https://github.com/tloen/alpaca-lora/pull/359#issuecomment-1517859182
@lywinged
I don't think so. My impression is that my use-case was misinterpreted. This allows us to load an adapter, and then train a new second adapter, rather than continuing from an old adapter. My use-case was continuing training from an old adapter, so that I didn't need to retrain a new adapter every single time I acquired new data.

Code is here

how to work? i mean how to predict with the new lora model.
i trained a new lora model, from llama-7b and tloen/alpaca-lora-7b, and i get a new lora model, how to add tloen/alpaca-lora-7b and my own lora model.


docs: generate C# models

Description

Add the generate C# model example
Updated relevant docs
Add relevant test and it's respective snapshot

Related issue(s)
Fixes #412

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.575%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2368

Relevant Lines:
2414

💛  - Coveralls


vscode crashes so frequently with vscode-go extension enabled and editing a go file

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

VS Code Version: 1.67.0
OS Version: PoP OS 22.04 5.17.5

Steps to Reproduce:

Open a go project in vscode
Try saving the go file with a change, vscode exits/crashes

Disabling the go-extension and cannot reproduce.

/extGo

@gjsjohnmurray Is there any guidance on how to capture the crash logs of vscode?

@hyangah maybe this?
https://github.com/microsoft/vscode/wiki/Native-Crash-Issues


Allow for nested editing of models

Hi! I have read a few discussions on nested editing of models and I needed it for my project, so I put together a solution
Proposed solution

This is what it looks like. It requires a new form field (inline-relationship), some new UI for deciding which columns to show, a new Trait (basically HasFillableRelations with some changes), some changes to the VoyagerBaseController insertUpdate method and a small change to all formfield templates. How much interest would there be in me making a pull request and would anyone be willing to help me with testing and completing this?

We won't be adding this to the v1.x stream, since it's a fairly major change.  v2.0 will already include a rewrite of the BREAD system, and I believe includes some functionality similar to this.  @emptynick was working on it, so he should be able to provide a better answer


Programmatic install uses top-level bower.json instead

I have a project folder structure like this:
root/
    bower.json
    src/
        stuffs that depends on bower.json above
    test-runner/
        index.js
        package.json

In my index.js I run this:
var bower = require('bower');
var packages = ['angular', 'angular-animate']; // etc
bower.commands
            .install(packages, {}, { /* custom config */ })
            .on('end', function() {
                console.log('DONE!');
            });

where packages is an array of packages different  from those in root/bower.json (for the sake of the bug report let's say they're hard-coded).
As I updated bower to 1.5.1 the code in index.json has started using root/bower.json instead of the packages provided by the packages variable. Downgrading to 1.4.1 makes everything work as expected again.
Expected result: that bower.commands.install uses the packages provided in the parameter, and only fallback to bower.json if no parameters are provided.
Possibly related to 7acafc26d6207e44794b02402cdf6b9f66c53f01 ?

Yes, thank you. It's a bug. I'll either fix it or rollback very soon.

In 1.5.2 I've reverted auto-running in directory containing bower.json, so it should be fine now..

Thanks for the quick fix!


Adding status information in crbirding_observations

We asked to SOVON about the possibility to introduce the official Euring column status in order to translate our action code broedend.
SOVON:

“Het is geen enkel probleem om extra kolom in te voegen."

Question for Eric, Marc:
Now that we have the column status, do you think can we link other action codes to other status values?
here below all information about status I found in Euring Exchange Code 2000+:

All full-grown birds must have a Status code, even if it is the unknown/not recorded code, U. Birds ringed as pulli must be coded with a hyphen.

code
description

-
bird a pullus (one ‘hyphen’)

U
Unknown or unrecorded.

N
Nesting or Breeding.

R
Roosting assemblage.

K
In Colony (not necessarily breeding but not pullus).

M
Moulting assemblage (whether bird moulting or not).

T
MoulTing.

L
Apparently a Local bird, but not breeding.

W
Apparently a bird Wintering in the locality.

P
On Passage - certainly not a local breeding nor wintering bird (includes birds attracted to lighthouses).

S
At Sea - birds on boats, lightships or oil rigs.

Code U (unknown or unrecorded) must be used unless there is complete certainty about the status. Do not make conclusions based on “I do come here often and the birds always behave in that way”.

I think we can add status - to pulli, this for sure, I think. Do you think are there other situations where we can assign a status code (complete certainty needed)? otherwise I will add U to all other observations as demanded by Euring.

I forgot to mention that we agree also on mapping action code gevangen op nest as condition 8 and status N (Nesting or Breeding).

Eric's answer:

Inderdaad kan er in twee gevallen status worden toegekend (namelijk - voor pullus en N voor broedend) en dan U in alle andere gevallen.

Thanks to this answer I can closes this issue.


Update constraints imports and dependencies

Update constraints package since it was moved to golang.org/x/exp/constraints from stdlib.
Invoke go mod tidy to update dependencies. Some of them were unused.

@s0xzwasd Thank you! :)


Export/Import all/selected types to a .h file

It would be nice to be able to export all/selected types to a .h file, so I can 1). reuse them in a C program; 2).  reuse it in another .bndb.
For exporting selected types, do not forget to walk the dependencies and export all related ones.
And for usage case 2) mentioned above, we might develop a better way to reuse types, but it is good for now.

"Import all types from an h file" is now implemented and will be in dev 3.2.3853, closing this and making a new issue dedicated to "export all types"


Allow/Fix bink sound volume control

The game uses bink video, which also supports audio data.
However, this audio is uneffected by the sound control sliders in the options menu. A good indicator for this would be selecting the woodcutter hut with active sound but with all sound sliders set to 0.
It would be awesome if the bink volume setting could be bound to, for example, the sfx slider. This would fix the issue of unintended sound playing and would also make bink-videos with sound more valueable to content creators.
Findings at the time of writing:

The game itself at least imports the function "_BinkSetVolume@12".
@gynt found out that the game uses a multiplication of 250 for the bink volume. An address to modify it would be 00408F6D.
(I assume game version 1.41?)

Little Note:
To create a valid .bik video with sound for Crusader, one must use the old audio codec in the RAD Video Tools. This is achieved by using an audio compress level of 100+. 104 for example is likely the old default setting (4 also in the old codec):

Some other findings regarding the bink-audio (addresses all for Crusader 1.41):

Setting the audio volume:

The function where the 250 multiplication ("Stronghold Crusader.exe" + 0x8F6D, from now on called "multNum") resides is called once for every bink-video that should play. Changing the value will change the volume of the next playout, but not the current. (That would likely require a whole new function.)
The "SetVolume"-call seems to take (ID/Address, 0, volume) as input.

The ID/address changed after restarts, but was consistent during the games lifetime (during my tests).
I am not sure about the 0.

The sound volume seems to be computed using "volume = someNumber * multNum".

someNumber comes from the function here Stronghold Crusader.exe+4A240. This function is also called in other places and returns either a value or 100. In my tests, these value was consistent per bink-video (I did not follow the other calls.) It also contains a loop that seems to search for something. My assumptions are:

It searches for some file (not only bink video) specific sound volume. Maybe some hardcoded values between ? and 100 they set to fine tune the audio.
The first part, but additionally, it also consideres the position of SFX. Since I only tested the "static" bink stuff, I do not know.
If only the first one would be true, you could theoretically modify the volume of specific sounds. (But I assume changing the wav volume might be easier for creators anyway.)

The maximal volume bink accepts seems to be 0x7FFF, otherwise the send value is replaced with this maxima, as far as I could tell. In numbers, this would mean:

If the maximal someNumber is 0x64 (100) then the maximal allowed multNum should be 0x147 (327).

Since I think binding it to the SFX slider is a good idea, I searched for some value addresses (current SFX value):

"Stronghold Crusader.exe"+D2AF40:

DefaultSFX? (Arrows, for example)
Read: 00479D1E - 8B 8E 70310000  - mov ecx,[esi+00003170]
Write: 00479E81 - 89 99 70310000  - mov [ecx+00003170],ebx

"Stronghold Crusader.exe"+D27E44:

AmbientWind?
Read: 0047B1F3 - 8B 4C BE 70  - mov ecx,[esi+edi*4+70]
Write: 00479ECA - 89 44 B1 70  - mov [ecx+esi*4+70],eax

"Stronghold Crusader.exe"+D27E48:

AmbientBird?
Read: 0047B1F3 - 8B 4C BE 70  - mov ecx,[esi+edi*4+70]
Write: 00479ECA - 89 44 B1 70  - mov [ecx+esi*4+70],eax

These two values seem to be menu drawing related:

"Stronghold Crusader.exe"+20102C
"Stronghold Crusader.exe"+D265F0

I have no clue how hard it might be to create a reliable value access.

Regarding perceived loudness
How loud something is perceived is pretty complicated. Wikipedia can help.
In general, a lineary progression does not work. The issue is that I have no clue what the volume that bink needs actually is. If it is some physical value and I am not twisting it, steps between higher values will not increase the loudness as much as steps in lower ones. My tests feeled mixed.
Regardless of this, I still think starting with something like multNum = SFXvalue * 327 should be the way to go, before more complicated stuff is tried (this would need to work first). Maybe, even if binks volume does not expect some lineary rising value, it might still be enough to use multNum = SFXvalue * 250 (with the default value), or even only * 200, to move the progression more towards the "stronger" steps (if this is even the case).

I like how much effort you put into your documentation, ver nice to read :)
Haven't touched sounds so far, so no clue how to change volume during playout. Regarding your proposal i made a little CE script:

starting with something like multNum = SFXvalue * 3.27 should be the way to go

sound.CT.zip

sound.CT.zip

Sadly, your script didn't work out of the box for me. I needed to change the memory protection of multNum manually, but then it worked.
So far the bink volume seems to behave like the volume of the other SFX sounds if it is changed through the script, but this likely requires more tests... and more ears... but the direction is good.
I also created a list of the bink videos with sound (and added if they are stereo or mono, because why not? 🙃):
action_mad_cows.bik             stereo
action_plague.bik               mono
action_rabbits.bik              stereo
action_steal_bread.bik          mono
pg_vict1.bik                    stereo
pg_vict2.bik                    stereo
pg_vict3.bik                    stereo
richard_swordswing.bik          stereo
rt_anger1.bik                   stereo
rt_plead1.bik                   stereo
rt_plead2.bik                   stereo
rt_plead3.bik                   stereo
rt_taunt1.bik                   stereo
rt_taunt2.bik                   stereo
rt_vict1.bik                    stereo
rt_vict2.bik                    stereo
st03_woodcutters_hut.bik        stereo
st07_hunters_hut.bik            stereo
st12_fletchers_workshop.bik     stereo
st13_blacksmiths_workshop.bik   stereo
st14_poleturners_workshop.bik   stereo
st15_armourers_workshop.bik     mono
st16_tanners_workshop.bik       mono
st17_bakers_workshop.bik        stereo
wf_anger1.bik                   stereo
wf_plead1.bik                   stereo
wf_plead2.bik                   stereo
wf_taunt1.bik                   stereo
wf_taunt2.bik                   stereo
wf_vict1.bik                    stereo
wf_vict2.bik                    stereo


Fix bug (#13554)

Describe the pull request

What does your PR fix? Fixes #13554

Which triplets are supported/not supported? Have you updated the CI baseline? Supports x64-windows, x86-windows

Does your PR follow the maintainer guide? Yes

looks like the problem will be solved after the PR #13450 is merged, I'm closing this PR


Use case example

Update readme file elaborating use cases and show an use case example.

Thanks for your response. I will do it as soon as possible.


Remove line from slide 2

Line #5 needs to be removed from slide 2 because is no longer needed.

created branch referencing main: slide2-remove-line5


CPU Temperature Always Reporting 0

sensors.txt
Expected Behaviour
CPU Temperature reports the temperature recorded from the sensor.
Actual Behaviour
CPU Temperature always reports 0degrees.
Reproduction steps

Create a Percent (Gradient) Layer
Set the Current Value to LocalPCInfo/CPU/Temperature
Set the Maximum Value to 90 (or another non-zero number)
Set the Effect Type to "All at once"

Blink Threshold is a non-factor

The CPU in question is a Ryzen 7 5800x.
Frequency
This happens every time.
Aurora Version:
Aurora v198
Previously an Issue?
Yes, I have tried it in v194 and v129 and it did not work in either of them.

Thanks, fixed in last version
https://github.com/Aurora-RGB/Aurora/releases


feat(headless): add timezone to engine config, deprecate useLocalTime

https://coveord.atlassian.net/browse/KIT-837
Should I also add it to the service APIs and the recommendations ?

@olamothe
Looked it up & timezone is an available parameter for the following requests:

/ (search & recommendations)
/querySuggest
/plan

Not available for:

/facet (facet search)
/html
/classify (case assist)
/documents/suggest (case assist)


How to make example_apps work

Hello
I have tried to pull the whole project from git. I have put navigation_autocomplete in its own project. I have taken the db.sqlite but now it also needs the url auth_user_change. I don't know where is the urls.py defining it.  Well, basically I can't make the example app "navigation_autocomplete" work.
What files must I gather in a projet in order to see it work ?
Thanks a lot.
BG

There is a topic about it in the docs have you seen it ? It drives you
through the needed files etc
Le 2 sept. 2015 16:47, "proph73"<EMAIL_ADDRESS>a écrit :

Hello
I have tried to pull the whole project from git. I have put
navigation_autocomplete in its own project. I have taken the db.sqlite but
now it also needs the url auth_user_change. I don't know where is the
urls.py defining it. Well, basically I can't make the example app
"navigation_autocomplete" work.
What files must I gather in a projet in order to see it work ?
Thanks a lot.
BG
—
Reply to this email directly or view it on GitHub
https://github.com/yourlabs/django-autocomplete-light/issues/487.

Yes, in two parts, I've seen it. Thanks. I wanted to compare my implementation with yours to understand it finely. I discovered that I was not using the javascript like I should. But thanks to the working live demo hosted by PythonAnywhere and the project code, I succeeded.
There are a tiny error in the doc in "{{ artist }}", there is a '}' missing.

Sorry :
in {{ artist }}

Cool, could you please make a PR ?
Thanks !


Keep alive

https://www.loxone.com/enen/wp-content/uploads/sites/3/2016/10/1000_Communicating-with-the-Miniserver.pdf page 21.
TODO: Implement header async send

byte[] arrOutput = { 0x03, 0x06, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 }
Will cause websocket closing

Send text over ws: "keepalive" and receive keepalive header.
there is a special command called “keepalive”. Whenever a client sends this command to the Miniserver, it will respond with a message header


[BUG] Send Single MMS is deprecated

Describe the bug
When sending an MMS message I am getting an error that I believe is related to the MMS send single message endpoint being deprecated. According to the infobip documentation I believe this should be updated to work similarly to the SMS endpoint. Send MMS documentation for reference
To Reproduce
Steps to reproduce the behavior:

Attempt to send an MMS message

Expected behavior
MMS message is sent
Screenshots
N/A
Desktop (please complete the following information):

OS: Arch
Browser N/A
Version N/A

Smartphone (please complete the following information):
N/A
Additional context
Add any other context about the problem here.

Another option is potentially adding support for the unified endpoint https://www.infobip.com/docs/api/platform/messages-api/sending-message/send-messages-api-message


Don't add unset fields to message

Tests the PR here: https://github.com/ga4gh/ga4gh-client/pull/42 and change JSON serializing to NOT add unset values to the resulting JSON.

Current coverage is 84.90% (diff: 100%)

Merging #1530 into master will decrease coverage by 0.83%

@@             master      #1530   diff @@
==========================================
  Files            30         32     +2
  Lines          7023       7087    +64
  Methods           0          0
  Messages          0          0
  Branches        888        897     +9
==========================================
- Hits           6021       6017     -4
- Misses          843        909    +66
- Partials        159        161     +2

Powered by Codecov. Last update 22fc2d9...2b8429a


"flockerctl list-nodes" doesn't shows all the nodes

Hello,
The Flocker Control Service node don't show all nodes.
I have 3 nodes
node1: All Flocker Agent Services are up. flocker-dataset-agent, flocker-container-agent and flocker-docker-plugin are running well. Ip address is <IP_ADDRESS>
node2: All Flocker Agent Services are up. flocker-dataset-agent, flocker-container-agent and flocker-docker-plugin are running well. Ip address is <IP_ADDRESS>
node-control (node control only): The Flocker Control Service is Up. flocker-control is running well. Ip address is <IP_ADDRESS>
flockerctl list-nodes command shows:
[root@machine flocker]# flockerctl list-nodes
SERVER        ADDRESS
56618826     <IP_ADDRESS>
I restarted both services, then I run flockerctl list-nodes command, still I don't see node2
[root@machine flocker]# flockerctl list-nodes
SERVER       ADDRESS
56618826     <IP_ADDRESS>
I verified the certificates (node.crt and node.key) on both nodes  whether they are different.
Any ideas?
Why I can not see another the node?
This question concerns Flocker Services?

Usually we see this when the same node.crt/key is used on every node. Make sure each not has a different crt and key create separately.
e.g. 2 nodes
flocker-ca create-node-certificate node1
flocker-ca create-node-certificate node2

Can you verify this is the case?
Also, please run and send the output from the command flocker-diagnostics from the two nodes not showing up to<EMAIL_ADDRESS>

@akshaycalsoft : as @wallnerryan pointed out, can you please confirm if the node certificates are unique, and if so, can you please share output of flocker-diagnostics ? Thanks!

Hi,
I verified that the node certificates on both the nodes are different.
I executed the flocker-diagnostic, but it is giving some error.
`[root@flocker-vm2 ~]# flocker-diagnostics
Failed to get data: Cannot assign requested address
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
fdisk: cannot open /dev/sdz: Input/output error
`

@wallnerryan Please find attached zip file created by "flocker-diagnostics" command.
clusterhq_flocker_logs_1a42f148-3f8d-11e6-9eba-000c29bcba7c.zip


*autoload: Silence pushd output

Hides printed directory stack when using pushd

Hi,
I'm afraid this would also prevent user's chpwd_functions hooks (for me, chpwd_recent_dirs) so it might be better to use pushd_silent option for that purpose.
Or, if it's fine to remove -R from the emulate call, perhaps the behavior can be controlled by user's side?

I switched it to use pushd_silent over -q. I am unsure if we left out the -R option if there are any cases that would alter the expected behavior of the function, so I decided to just enforce pushd_silent here.


Add doManifest function

Request from here

Done: https://github.com/Petschko/dhl-php-sdk/commit/9ce81e7cb2cbf491f5817887e659bf26a6e03ca9


⚠ Bofrost.lu has degraded performance

In 403181e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1675 ms

Resolved: Bofrost.lu performance has improved in 121ef80 after 6 minutes.


Improve documentation and add advisory_xact_lock

You can not protect database operations inside the advisory_lock context if you are running under Django transaction Middleware. The advisory_lock context is still good if you want to protect concurrent access to other resources (we use it to avoid stampede on some external resources)
For example, this code is as good as not locked:
with advisory_lock(42):
    obj = MyObject.get(id=42)
    obj.accessed +=1
    obj.save()

If you do not commit inside the context, then with two workers you can get the following behavior:

A takes lock
B wait on lock
A read obj, accessed = 0
A write accessed = 1 (change not committed)
A release lock
B takes lock (this goes very fast since B was waiting for it)
B read obj, accessed = 0 (A change still not committed : it takes time to build the response)
A commits
B writes accessed = 1
B commits

We had a very ugly bug in production because we were on the wrong impression our databases transactions were protected inside the advisory_lock context.
We had to write own py2/3 compatible version of this, that I share with you here under MIT license https://gist.github.com/lionel-panhaleux/bd62ade43afe57e6f365 .

Thank you! I'll update the documentation to indicate that the locks are not compatible with the standard transaction middleware. In general, I don't advise the use of this module outside of explicit transactions.


Database migration: PHP Fatal error:  Cannot use 'Object' as class name as it is reserved in vendor\yiisoft\yii2\base\Object.php on line 28

What steps will reproduce the problem?
install php 7.2.2
composer create-project --prefer-dist yiisoft/yii2-app-advanced yii2-app
php init (choose development mode = 0)
composer require mdmsoft/yii2-admin "~2.0"
define admin module in common/config/main.php: 'class' => 'mdm\admin\Module'
define authManager component in common/config/main.php: 'class' => 'yii\rbac\DbManager'
create a database in MySql and configure it in common/config/main-local.php
yii migrate --migrationPath=@mdm/admin/migrations in CMD
What is the expected result?
creating a proper user table for the user management
What do you get instead?
PHP Fatal error:  Cannot use 'Object' as class name as it is reserved in vendor\yiisoft\yii2\base\Object.php on line 28
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.2.2 (using XAMPP)

Operating system
Windows 10 (x64)

It's mdmsoft/yii2-admin issue. Please report there.


Google Assistant and Homekit sending wrong target temp values

Home Assistant release with the issue:

0.82.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on Docker on CentOS 7
Component/platform:

Description of problem:
If I choose a temperature of 73°F in Google Assistant, the value of 72.99999122619629 is sent to my thermostat. My thermostat rounds this down to 72°F so I can not actually set a target temp of 73.
If I choose a temperature of 75°F in HomeKit, the value of 74.7 is sent to my thermostat. My thermostat rounds this down to 74°F so I can not actually set a target temp of 75.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
cloud:

homekit:
  auto_start: false

climate:
  - platform: mqtt
    name: Thermostat
    modes:
      - "off"
      - "heat"
      - "cool"
    fan_modes:
      - "Auto"
      - "On"
    current_temperature_topic: "hvac/current_temperature"
    mode_command_topic: "hvac/mode/set"
    mode_state_topic: "hvac/mode/get"
    temperature_command_topic: "hvac/temperature/set"
    temperature_state_topic: "hvac/temperature/get"
    fan_mode_command_topic: "hvac/fan/set"
    fan_mode_state_topic: "hvac/fan/get"
    availability_topic: "hvac/availability"
    min_temp: 45
    max_temp: 95

Traceback (if applicable):

Additional information:
It looks like both components are working in Celsius and then converting to Fahrenheit. Ideally the components should work in the user's native unit measurement system (from configuration.yaml), but a possible short term fix would be to send a rounded integer to the thermostat.

I only know the situation with HomeKit: The Home App uses Celsius internally, but only rounded to the nearest 0 or .5 value. That's the one which is then send to Home Assistant where it's converted back to Fahrenheit also with another rounding to the nearest 0 or .5 value. Unfortunately that's the way it has to be done with unit conversions.
I tried setting the temperature to 75°F in the Home App myself. However it all worked fine for me. The temp target from HomeKit was 24.0°C (75.2°F) which was converted to 75°F by Home Assistant and used for the service call.

Need to add rounding to the execute() function for all commands.
https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/google_assistant/trait.py#L583


Odd bug with selections.

When the first note of the song is selected, it ignores just that note.
Example: https://edude.xyz/downloads/other/OpenNoteBlockStudio_Odd_Bug.mp4
Had to use my own host because YouTube wasn't working.

That's been an issue since the older version of note block studio. You just have to deselect the part. As it's minor, I don't think we will fix it anytime soon, but i'll take a look anyway.


Change default X-Frame-Options

Change "DENY" to "SAMEORIGIN"
X-Frame-Options' default value is "SAMEORIGIN", not "DENY".
X-Frame-Options: DENY header affects the Article Preview feature of Grav.

Good point!

@rhukster I thought the default was SAMEORIGIN when there was no X-Frame-Options header, but I just realized it allows all iframes regardless origin.
For now, the problem of Grav itself is solved by this PR, but X-Frame-Options: SAMEORIGIN can also lead to unintended problems.
However, it seems impossible to allow all frames with the X-Frame-Options header. (Unfortunately, allow-from option deprecated)
I suggest you that delete X-Frame-Options from default example.


Implement Transactions Tab

We currently can't get the status of the transaction but we do have the rest of the information in the design.
Design:
https://zpl.io/a74dyPj

@yanivkalfa I am updating this ticket with new designs that include operations:
https://app.zeplin.io/project/5b1752dd44fc7a0363cd9dc8/dashboard?seid=5b401f4576f3ae2f2fec46b6
Please let me know if you have any questions. Dominika was working on a branch called "Transactions" so you can take it over from there.

@developer0623
Is it possible to show the 'Delegation operations' in the transactions tab?
For example; when I change the address I am delegating to, nothing gets logged in the transaction tab. Can we track the delegation change operations?

Merged with #266


[v2024.4.0] Error importing plugin "vscode_pytest": cannot import name 'Literal' from 'typing' [Py3.7]

Behaviour
Cant load / run any pytests tests in v2024.4.0
Can see the breaking change coming in here:
https://github.com/microsoft/vscode-python/compare/v2024.2.1...v2024.4.0#diff-9a28b4b19fbb6331c15c76b4752852162785c0d521038cb637d8432901ebead2R13
should be importing from typing_extensions
Steps to reproduce:

Try to run / load any pytest tests

Diagnostic data

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Traceback (most recent call last):
  File "c:\python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pytest\__main__.py", line 5, in <module>
    raise SystemExit(pytest.console_main())
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 192, in console_main
    code = main()
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 150, in main
    config = _prepareconfig(args, plugins)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 332, in _prepareconfig
    pluginmanager=pluginmanager, args=args
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pluggy\_hooks.py", line 433, in __call__
    return self._hookexec(self.name, self._hookimpls, kwargs, firstresult)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pluggy\_manager.py", line 112, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pluggy\_callers.py", line 133, in _multicall
    teardown[0].send(outcome)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\helpconfig.py", line 104, in pytest_cmdline_parse
    config: Config = outcome.get_result()
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pluggy\_result.py", line 108, in get_result
    raise exc.with_traceback(exc.__traceback__)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\pluggy\_callers.py", line 80, in _multicall
    res = hook_impl.function(*args)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 1075, in pytest_cmdline_parse
    self.parse(args)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 1425, in parse
    self._preparse(args, addopts=addopts)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 1301, in _preparse
    self.pluginmanager.consider_preparse(args, exclude_only=False)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 709, in consider_preparse
    self.consider_pluginarg(parg)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 735, in consider_pluginarg
    self.import_plugin(arg, consider_entry_points=True)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 785, in import_plugin
    ).with_traceback(e.__traceback__) from e
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\config\__init__.py", line 781, in import_plugin
    __import__(importspec)
  File "C:\Users\mhuisman\envs\3.7\lib\site-packages\_pytest\assertion\rewrite.py", line 178, in exec_module
    exec(co, module.__dict__)
  File "c:\Users\mhuisman\.vscode\extensions\ms-python.python-2024.4.0\python_files\vscode_pytest\__init__.py", line 13, in <module>
    from typing import Any, Dict, List, Optional, Union, Literal, TypedDict  # noqa: E402
ImportError: Error importing plugin "vscode_pytest": cannot import name 'Literal' from 'typing' (c:\python37\lib\typing.py)

looks like PR: https://github.com/microsoft/vscode-python/pull/22741/ brought in these breaking changes

ive opened a PR to fix https://github.com/microsoft/vscode-python/pull/23180/files

Closing this.
Python 3.7 has been out of support for about 6 months. Underlying packages have moved out of 3.7 support. We will be migrating any remaining packages out of python 3.7 as well. You can pin the extension to 2024.2.1 or older for python 3.7 support.

@matthuisman, I am running into a similar issue on VScode. It seems like your PR was not accepted due to Python 3.7 reaching EOL. Do you have a way to get around this error? Thanks a bunch!

revert / pin to old Python Extension version is the only solution it seems


Find solution for the elevation offset problem

Currently the hard wired elevation data is essentially false. See:

https://github.com/RecyclingTrashCans/recycling-trashcan-armap/commit/9979dfdb226b601e6aa061f2f2e1048a0bd7b5f0
Ref https://github.com/RecyclingTrashCans/RecyclingTrashCans.github.io/issues/10

Darryl Bartlett reminded me about this problem. I featured the issue in my slide deck: https://docs.google.com/presentation/d/1cowOSK3b9H_9q4ot0ouONJopnp9Hf6do8sbB0SDln-g/edit?usp=sharing

Darryl Bartlett drew my attention to terrain anchors which could be the solution to this: https://developers.google.com/ar/develop/java/geospatial/terrain-anchors

Haven't tested any corner cases yet like pins half under trees


This build could not be used for external testing because the build is not approved MANY TIMES

I've got this stack trace yesterday after pushing update to TestFlight:
Update using 'sudo gem update fastlane'
/Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.1/lib/spaceship/tunes/tunes_client.rb:163:in `handle_itc_response': This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. (Spaceship::TunesClient::ITunesConnectError)
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.1/lib/spaceship/tunes/tunes_client.rb:474:in `update_build_trains!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.1/lib/spaceship/tunes/build_train.rb:100:in `update_testing_status!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/pilot-1.0.1/lib/pilot/build_manager.rb:109:in `distribute_build'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/pilot-1.0.1/lib/pilot/build_manager.rb:22:in `upload'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/actions/pilot.rb:15:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:142:in `block (2 levels) in execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/actions/actions_helper.rb:37:in `execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:128:in `block in execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:127:in `chdir'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:127:in `execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/fast_file.rb:149:in `method_missing'
    from Fastfile:54:in `block (2 levels) in parsing_binding'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/lane.rb:36:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/lane.rb:36:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:51:in `block in execute'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:46:in `chdir'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/runner.rb:46:in `execute'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/lane_manager.rb:43:in `cruise_lane'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/lib/fastlane/command_line_handler.rb:31:in `handle'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/bin/fastlane:35:in `block (2 levels) in run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/bin/fastlane:152:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.39.0/bin/fastlane:158:in `<top (required)>'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in `load'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in `<main>'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'

I was on 1.39.0. I did not notice any useful release notes on this so probably this issue is still exists. It killed 'slack' command so nobody received release notes from me :( We use internal testing only.

log from today:
[18:49:32]: Waiting for iTunes Connect to finish processing the new build (1.0 - 82)
[18:50:02]: Successfully finished processing the build
[18:50:02]: You can now tweet:
[18:50:02]: iTunes Connect #iosprocessingtime 77 minutes
[18:50:02]: Distributing new build to testers
[18:50:09]: Variable Dump:
[18:50:09]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :IPA_OUTPUT_PATH=>"/Users/pronebird/dev/AppName/AppName.ipa", :DSYM_OUTPUT_PATH=>"/Users/pronebird/dev/AppName/AppName.app.dSYM.zip", :SIGH_PROFILE_PATH=>"/Users/pronebird/dev/AppName/AppStore_com.doman.AppName.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/pronebird/dev/AppName/AppStore_com.doman.AppName.mobileprovision"], :SIGH_UDID=>"37a2e3d0-1a2d-4b18-8483-4359d2c969ef", :SIGH_PROFILE_TYPE=>"app-store"}
[18:50:09]: This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved.

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | cocoapods                           | 16          |
| 5    | gym                                 | 49          |
| 6    | sigh                                | 14          |
| 7    | pilot                               | 4717        |
+------+-------------------------------------+-------------+

[18:50:09]: fastlane finished with errors
-------------------------------------------------------------------------------------------
😨  An error occured. Please enable crash reports using `fastlane enable_crash_reporting`.
👍  This makes resolving issues much easier and helps improve fastlane.
🔒  The reports will be stored securely on getsentry.com.
✨  Once crash reporting is enabled, you get a clean output when something goes wrong.
🙊  More information about privacy: https://github.com/KrauseFx/fastlane/releases/tag/1.33.3
-------------------------------------------------------------------------------------------
/Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.2/lib/spaceship/tunes/tunes_client.rb:163:in `handle_itc_response': This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. (Spaceship::TunesClient::ITunesConnectError)
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.2/lib/spaceship/tunes/tunes_client.rb:476:in `update_build_trains!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/spaceship-0.14.2/lib/spaceship/tunes/build_train.rb:100:in `update_testing_status!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/pilot-1.0.1/lib/pilot/build_manager.rb:109:in `distribute_build'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/pilot-1.0.1/lib/pilot/build_manager.rb:22:in `upload'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/actions/pilot.rb:15:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:142:in `block (2 levels) in execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/actions/actions_helper.rb:37:in `execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:128:in `block in execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:127:in `chdir'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:127:in `execute_action'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/fast_file.rb:149:in `method_missing'
    from Fastfile:54:in `block (2 levels) in parsing_binding'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/lane.rb:36:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/lane.rb:36:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:51:in `block in execute'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:46:in `chdir'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/runner.rb:46:in `execute'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/lane_manager.rb:43:in `cruise_lane'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/lib/fastlane/command_line_handler.rb:31:in `handle'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/bin/fastlane:35:in `block (2 levels) in run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/bin/fastlane:152:in `run'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/gems/fastlane-1.42.0/bin/fastlane:158:in `<top (required)>'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in `load'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in `<main>'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
    from /Users/pronebird/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'

Fastlane should not DIE if build is already published.

Ran into the same problem. Would consider this a bug. It's hardcoded to submit it for external beta testing... https://github.com/fastlane/pilot/blob/66a68c78e8eb0191b25de0b152dc9edc4afabfa4/lib/pilot/build_manager.rb#L109-L109

Same error.

Same issue here

Same issue too

Same issue here.

Same here too

Same here

same issue here too

same here.

everybody, I wanna  know,this bug is the spacship's bug or the iTunes‘ bug.about one mouth ago, i used spaceship 0.13.1,and it works OK,but since i upload an error ipa to ITC ,it always raise this issue.

@self-creative @MartinRogalla pointed out that this is pilot's bug.

@pronebird Thanks,Hope it will  be resolved.You konw,every day now, I need manully update build versions for tester.What a bad story,,,,Oh no ,,,heros I need help

@pronebird, I'm not so sure. My ruby skills have much to be desired, but switching the string at https://github.com/fastlane/pilot/blob/66a68c78e8eb0191b25de0b152dc9edc4afabfa4/lib/pilot/build_manager.rb#L109-L109 from external to internal didn't help for me. So maybe Apple's API has changed and Spaceship needs some modifications.

I just verified that app.build_trains["...."].update_testing_status!(true, 'internal') does work. So it is indeed a problem with pilot and not with spaceship. (haha I'm loving these names...)

I just checked, pilot is calling this line by default
uploaded_build.build_train.update_testing_status!(true, 'external')

How about I add an option to choose between internal and external testing?

Please update to https://github.com/fastlane/pilot/releases/tag/1.2.0 and try the new option. Let me know if that fixes the problem.
Sorry for not replying earlier, I was swamped with the release of match

@KrauseFx hi,I only use spaceship and raise this issue,it will also solved in this update ?

@KrauseFx  hi,I only use spaceship and raise this issue,it will also solved in this update ?

This patch works for me. Thanks @KrauseFx!

my code :
train = app.build_trains["1.1.0"]
train.builds[0].submit_for_beta_review!(parameters)
But,it also raise following issue:
/Library/Ruby/Gems/2.0.0/gems/spaceship-0.18.0/lib/spaceship/tunes/tunes_client.rb:207:in handle_itc_response': This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. This build could not be used for external testing because the build is not approved. (Spaceship::TunesClient::ITunesConnectError) 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.18.0/lib/spaceship/tunes/tunes_client.rb:520:in update_build_trains!'
from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.18.0/lib/spaceship/tunes/build_train.rb:105:in update_testing_status!' 	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.18.0/lib/spaceship/tunes/build.rb:152:in submit_for_beta_review!'

@self-creative I am also getting this error :( @KrauseFx Is pilot not able to submit builds to external testers if it has already gone through beta app review?


Pathfinders bugfix - guard against duplicate outputs and outcomes within tables and across tables

This is a fix for a pre-existing problem with the code that basically meant that if a user entered the same output name more than once, even across both the "Standard outputs" and "Bespoke outputs" tables (as in, the user enters the same output in both tables), AND there is no matching output name in the database table output_dim, we get an uncaught database integrity error causing a 500 response, because of a lack of unique validation in the application and a unique constraint on output_dim.output_name. The same thing applies for outcomes.
Although it appears that at least one LA entered a duplicate output name for Pathfinders R1 (based on the fact that the test spreadsheet that Craig sent to me a couple days ago, which I believe contained the actual data as it was entered by one of the LAs, contained a duplicate output name), my theory is that we didn't see any error then because the submission containing the duplicated output name was by chance submitted after a submission containing the same output name, but not duplicated across tables, which meant that the output name was inserted into output_dim okay. And then when the submission with duplicated output names was submitted afterwards, and funding-service-design-post-award-data-store/data_store/controllers/load_functions.py::get_outcomes_outputs_to_insert was run to filter out existing outputs, the duplicated output name was filtered out and the application never attempted to insert it into output_dim, so no error was thrown. Again, the same thing applies for outcomes.
The code in this PR applies in-table and cross-table checks to ensure all outputs and outcomes entered are unique. It ensures that we never reach a stage where a database integrity error is possible.
This branch was checked out from RFP-453_pathfinders-round-2 as it contains R2-specific code. It is not essential to merge this - as I mention above, we got lucky in R1 and we now likely have most (if not all, I haven't checked) of the available output and outcome names already in the output_dim and outcome_dim tables, which means an error is even less likely this time around. Merging this may also have unintended consequences in terms of preventing users from submitting data in the way they expect (i.e., do we actually know that having the same output name in both standard and bespoke outputs is wrong?). However, I wanted to leave this PR here to give the option if we do decide this problem needs fixing, and wanted to avoid database load changes / migrations.

Manual validation of the 10 spreadsheets sent out to LAs for PF R2 showed no duplicate outputs or outcomes with locked cells, so no urgency on this fix going out and can think of a longer-term solution based on stronger understanding of outputs / outcomes / intervention themes and their relationships.

Thought I already closed this but apparently not - this has been superseded by this PR.


Rename #[rec] to #[nested]

https://github.com/taiki-e/auto_enums/issues/21#issuecomment-485796062

@taiki-e I would like to take this up.


Handle Mutex creation exceptions

https://github.com/aspnet/Razor/issues/2226
Handling Mutex creation exceptions the same way roslyn handles them. We log the exception and fallback to in process cli execution instead of blowing up.
Suggest reviewing this with ?w=1

🆙 📅 . Accidentally amended the commit.


Add Hop Limit Test For EKS metric_value_benchmark Test

Description of the issue
There is no way to test what happens when hop limit is 1 for EKS
Description of changes
Add hop limit 1 EKS test
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
https://github.com/aws/amazon-cloudwatch-agent/actions/runs/8635667138/job/23673984312

Do not merge until @jefchien finishes the eks get metadata w/o imds changes are done


Closing chats after opening

There's a method to visually open a chat in the WhatsappWeb instance:
https://github.com/wppconnect-team/wppconnect/blob/135805324b04479f2ea7811620525d8a750ca05a/src/api/layers/ui.layer.ts#L34
Now, since there's no closeChat() method, I wonder if there is any argument we can pass in to close the opened chat again.

I Already implemented by commit https://github.com/wppconnect-team/wa-js/commit/192e4162d468e188ab55d9d7894fcbbcbaf70c75
Now is necessary implement in lib and server, i will transfer this issue for LIB


fix(repo): Incorrect path format for public paths in nextjs playground

Description
Fixing the format of public paths array for authMiddleware in nexjts playground

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

@panteliselef Did we change those paths in a previous PR and broke the playground or is this a change in NextJS?
If it's a change in the NextJS we should probably check our docs and our nextjs starter repo to verify that there are no incorrect paths examples.

@panteliselef Did we change those paths in a previous PR and broke the playground or is this a change in NextJS? If it's a change in the NextJS we should probably check our docs and our nextjs starter repo to verify that there are no incorrect paths examples.

I had kept the same paths as before, but we were using a custom regex to validate those. Now with authMiddleware we need a follow specific format.
The introduced changed comes from a project of mine, which uses authMiddleware since it was launched. So nothing that affects developers has been introduced.


Separated init and loading in the Configurator

The configurator constructor was initializing the Configurator but also loading all the necessary data from the dataset configuration.
This PR separates the construction and loading the the Configurator to allow users to load the Configurator object to look at options,metadata, parameters, without having to load the actual datasets to begin the processing.
This allows law to inspect the Configurator before the dataset files are defined.
@felixzinn

Some law tasks need access to the config parameters without loading, potentially non existent, dataset configuration files.
The separation allows exactly that without raising errors.
👍🏼


Add grafana.spec.config.annotations.dashboard.max_age on grafana resource config

[Feature Request]
Description
We have millions of dashboard annotations and most of them are very old. This annotations will continue to grow as it is automatically added everytime someone make a change on applications. We decided to keep only 1 week worth of annotations and this feature i believe is supported in grafana mainstream by setting max_age on [annotations.dashboard] ref
On the API reference documentation for configuring the operator objects , i can see there's no configuration option for grafana.spec.config.annotations.dashboard. And this might be useful to being added to ensure old unused annotations is removed to save some space.
Suggested change:
An option grafana.spec.config.annotations.dashboards.max_age to define the retention policy for annotations.

Hi @Dizzudin2 , so this feature is solved in v5 since we allow you to configure any values that you want in the grafana ini file.
We are trying to keep the amount of changes that we do to v4 to a minimum, would it be an option if you can give v5 a try?
You can set any configuration you want using https://grafana-operator.github.io/grafana-operator/docs/api/#grafanaspec config.


Manifest not found for cypress/included:13.9.0 image

Running locally the following command
docker pull cypress/included:13.9.0
Results in :
Unable to find image 'cypress/included:13.9.0' locally docker: Error response from daemon: manifest for cypress/included:13.9.0 not found: manifest unknown: manifest unknown.
Request:

Fix the latest tag on cypress/included:13.9.0

@RajuTanchak
It looks like there was an issue publishing cypress/included:13.9.0.
The latest tag is still 13.8.1.
https://jsonplaceholder.cypress.io
has a problem with Status: 502 - Bad Gateway and caused the pre-release tests to fail.
Same for
https://example.cypress.io
It also looks like @AtofStryker is trying to re-publish

Sorry about that @RajuTanchak. Those images are publishing now https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images.

Working on this again since the tag isn't out still.

OK included image should now be published https://hub.docker.com/layers/cypress/included/13.9.0/images/sha256-9f46c625b16405c8aea05ccd950cb491e53e5afc585f34acd9ae2c1d755ea54a?context=explore. going to close as this is resolved


Bot works but commands don't work

I tried filling in your bot's .env file and config.json file and running it. There is a problem: When the bot starts, it does not print the running commands to the console. No commands of the bot are used and its state does not change. I couldn't find the problem, I tried a few times, I deleted and installed the current version, but I couldn't solve it. Can you help me please?

Delete index.js file and rename bot.js to index.js.
You can also have a look at this repo https://github.com/muralianand12345/Simple-Ticket-Bot in case you want only the Ticket Bot.

I did what you said, the problem is that I still cannot use the commands of the same bot and its status does not change. This bot was designed exactly the way I wanted, thank you.

Delete index.js file and rename bot.js to index.js. You can also have a look at this repo https://github.com/muralianand12345/Simple-Ticket-Bot in case you want only the Ticket Bot.

?

Please ensure that you have filled all the configuration files, i.e., JSON files inside both the 'extras' and 'main' folders. Since no errors are appearing in the console, as you mentioned, there might be an issue with your internet connection.

If it's possible, please send the complete error message so I can assist you further.

I filled in all the extras, but it's still the same, there is no error, nothing opens, the bot command is not used, the status does not change.

Let's say I have bad internet, I run it on my Ubuntu server, it has the same 1 Gbit line there.

I have an old version of the bot and it works, but when I click on the create ticket button it says the interaction failed. So I wanted to try the new version, I need it.

I ran the exact same code without any modifications or development code. I can confirm that the code works perfectly, and there are no errors in it. Please ensure that you have enabled all three Privileged Gateway Intents for the bots. To further identify the issue, consider using 'console.log' in 'index.js' for debugging.

I have already added a catch block, but there is no error. As for the bot's intents, all three of them are open.

I'm not making any mistakes, I can post a video from the beginning.

I ran the exact same code without any modifications or development code. I can confirm that the code works perfectly, and there are no errors in it. Please ensure that you have enabled all three Privileged Gateway Intents for the bots. To further identify the issue, consider using 'console.log' in 'index.js' for debugging.

?

@muralianand12345 I was able to run the bot! I create a ticket, but no message is sent to the opened ticket channel. It does not give any errors either on the console or in the error channels. Please help me pleaseee

I'm not active on GitHub, can you join this server and raise a ticket for queries or any help? https://discord.gg/mzPys5G8vf


[5.7][CursorInfo] Report values shadowed using shorthand syntax as secondary results

Explanation: When a variable is re-declared using shorthand syntax ([foo] closure capture or if let foo {), the user doesn’t perceive this as a new variable declaration. Thus, we should return the original declaration as a secondary result.
Scope: Cursor info of variables that are declared using the shorthand notations if let foo { or [foo]
Risk: Low
Testing: Added regression tests
Issue: rdar://75455650, rdar://91311033
Reviewer: @bnbarham on https://github.com/apple/swift/pull/58787

@swift-ci Please test

@swift-ci Please test


New WaveCell subclasses for different physics

Different elementary RNN cells for different wave physics.

With the refactoring in v0.2, this should be much easier to do by subclassing WaveCell.


Powershell variable assignment needs a $ sign else it throws error

I am using Powershell to execute this tutorial. The following commands threw error:
CLIENT_ID=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query "servicePrincipalProfile.clientId" --output tsv)
ACR_ID=$(az acr show --name  --resource-group myResourceGroup --query "id" --output tsv)
Error (Full error message not pasted for brevity):
CLIENT_ID : The term 'CLIENT_ID' is not recognized as the name of a cmdlet, function ...
I executed the same commands with a $ sign before the variables (CLIENT_ID and ACR_ID) and they ran fine.
$CLIENT_ID=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query "servicePrincipalProfile.clientId" --output tsv)
$ACR_ID=$(az acr show --name  --resource-group myResourceGroup --query "id" --output tsv)
Kindly update the document to update the relevant information

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

ID: d4af71a4-648e-580f-7e86-94ce05196de5
Version Independent ID: 134b8ba0-b085-076a-d2e1-16d0ddff5586
Content: Kubernetes on Azure tutorial  - Deploy Cluster
Content Source: articles/aks/tutorial-kubernetes-deploy-cluster.md
Service: container-service
Product: unspecified
GitHub Login: @neilpeterson
Microsoft Alias: nepeters

@amit133 Thanks for the feedback! We are currently investigating and will update you shortly.

@MicahMcKittrick-MSFT - you can assign this one to me. I have an update staged which will publish this afternoon.
@amit133 - thank for raising the issue. I have removed the variables from the doc. We need to address consumers working in Bash (larger population) and PowerShell. We have some platform tooling in the works that will allow switching between PowerShell and BASH, however it's not ready at this point. In the interim, I've removed the variables, which should mitigate.

I've updated the commands in this doc so that variables are not used. The doc now works in PowerShell and Bash (though some additional copy and paste is necessary). Updates will publish this afternoon.
Once we have the new tooling in place to allow 'code block context switching' I will update with both PowerShell and Bash commands.
#please-close


Full attachment url

Is there a helper to get the full attachment url with the host etc?
IE: http://somedomain.com/attachments/store/soi3jjria3fkajwfaj983htg/somefile.pdf

You can pass in :host to attachment_url:
attachment_url(@user, :avatar, host: request.url)

Since request doesn't have an method #host_with_scheme, you can pass a full URL, and internally Refile will replace the "path" part of the URL anyway. @jnicklas is it ok to rely on that behaviour?

Yes, that's an intentional feature. You're also encouraged to set Refile.host.

Oh, sorry, I read too fast. That's a neat way of solving this. I can't see us changing away from URI for this, so I doubt this will break, but there are no tests for it, so it's not an intended feature, sorry.

@jnicklas I'm trying print my photos in pdf generated by prawn, but it requires a full address. request doesn't exist on this context. What is your suggestion for this case?

Omg, it needs be the s3 url :/

@thiagogsr that doesn't really have anything to do with this issue. You can use Refile.file_url or Refile.attachment_url depending on which suits better. Check the docs.


support for disabling links when serializing (fixes #34)

This may not be the most elegant of ways to handle this, but it works. Open to suggestions.

This seems to work correctly.


services.httpd: Improve virtualHosts and subservices.

Currently services.httpd is complex and messy.  The biggest problem is that subservices are lazily added based on an attribute set which name which sub-services should be available.  This forbid the generation of any documentation for the subservices.  Users should be able to figure out their configuration from the manual without looking at the sources nor reading some wiki page (https://nixos.org/wiki/MediaWiki).
A long time ago, I already started to work on this issue (https://github.com/NixOS/nixos/compare/httpd-services), and failed at making a system which was easy enough to manipulate for somebody who does not know anything about NixOS module system.  I also failed at making it backward compatible, but I think this last idea is just a dead-end.
Now that more persons are looking at the multi-instances issues — which is the case of virtualHosts and subservices — I think I might have found a better way to address the user experience of module system users.
The idea is to remove the need for the per-server-options file, and automatically alias options which are useful inside the virtualHosts submodule (which was done manually in my previous attempt).  The second is to use mkAliasDefinitions to forward options definitions from the submodule into the parent module (while paying attention to keep the locations from the submodule).
To do so, we should duplicate services.httpd and create a new service, such as services.apache or services.httpd_v2, which would first be experimental, and then move as the only way to use it while we gradually get rid of current implementation.

I think we also need an abstraction that would not only work with apache
but maybe also with other webservers like nginx. I especially don't like
that PHP services are apache only, i use nginx most of the time.
On Mar 23, 2015 10:54 PM, "Nicolas B. Pierron"<EMAIL_ADDRESS>wrote:

Currently services.httpd is complex and messy. The biggest problem is
that subservices are lazily added based on an attribute set which name
which sub-services should be available. This forbid the generation of any
documentation for the subservices. Users should be able to figure out their
configuration from the manual without looking at the sources nor reading
some wiki page (https://nixos.org/wiki/MediaWiki).
A long time ago, I already started to work on this issue (
https://github.com/NixOS/nixos/compare/httpd-services), and failed at
making a system which was easy enough to manipulate for somebody who does
not know anything about NixOS module system. I also failed at making it
backward compatible, but I think this last idea is just a dead-end.
Now that more persons are looking at the multi-instances issues — which is
the case of virtualHosts and subservices — I think I might have found a
better way to address the user experience of module system users.
The idea is to remove the need for the per-server-options file, and
automatically alias options which are useful inside the virtualHosts
submodule (which was done manually in my previous attempt). The second is
to use mkAliasDefinitions to forward options definitions from the
submodule into the parent module (while paying attention to keep the
locations from the submodule).
To do so, we should duplicate services.httpd and create a new service,
such as services.apache or services.httpd_v2, which would first be
experimental, and then move as the only way to use it while we gradually
get rid of current implementation.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/6960.

Why should we get rid of per-server options?
We should get rid of subservices though. Those should be implemented as regular modules.

My biggest complain is the lack of documentation from options in the manual.

Yeah, if subservices were to use the regular module system, then then would show up in the manual.

@edolstra , per-server-option.nix is not a limitation, but it is in the way, and duplicating the documentation sounds like too much documentation.  I would prefer to alias the option declarations to the one define in the main config, such as the documentation is not duplicated, and the documentation reads  "Same as services.httpd_v2.adminAddr."

@offlinehacker , I don't know how nginx nor PHP subservice are working, but it seems that it might be easier to integrate as soon as PHP subservice becomes a module.

That's just a matter of hiding them from the documentation (e.g. using some flag).

ping

Closing because no reaction; please reopen if still relevant.


IPFS Q2 OKRs related to package management

Collecting all the OKRs that are closely related to package management from across the various IPFS working groups documented in https://docs.google.com/spreadsheets/d/1YSeyWqXh3ImanRrTkYQHHkCofiORn68bYqM_KTLBlsA/edit#gid=1681757723
project

[x] We have a prioritized roadmap for how IPFS will be used as a default distribution channel for 1000s of package manager users by EOY
[x] All IPFS working groups understand and actively address package manager needs, use cases, & pain points
[x] 5 package manager demos and/or deployments are proactively documented and shared with the wider community

go-ipfs:

[ ] It's possible to "rsync" to go-ipfs (initiative: Writable FUSE)
[ ] Implement provider strategy such that a user can add (and provide) npm or tr-wikipedia without turning off providing and without significantly impacting finding content (initiative: provider subsystem)
[ ] When connected to the global internet, IPNS record resolution takes less than 1s (initiative: IPNS over DNS, IPNS over pubsub, etc.)
[x] go-ipfs saturates a 100MiB link when downloading a sufficiently large dataset.
[x] go-ipfs has at most 10% overhead when downloading a large dataset (not including providing).
[ ] go-ipfs has experimental support for modification times and other metadata (initiative: UnixFSv2)

cluster:

[ ] Generate 3 step-by-step guides for standard ways of using Cluster
[ ] Sharding

GUI

[ ] ipfs.io updated with up to 6 specific use cases and analytics flows that tell us which are popular
[ ] npm-on-ipfs desktop app

infra:

[ ] Automate npm-on-ipfs deployment and upgrade running Infra

In Web Browsers:

[x] IPNS resolve time is less than 10 seconds in browser contexts
[ ] Built an IPFS-based Unpkg prototype

DDC:

[x] Go-IPNS is performant and supports offline persistence
[ ] JS-IPNS is performant and supports offline persistence
[x] Identify opportunity for IPNS usage by package managers WG
[ ] There is a system that allows a third party to persist IPNS data in a gossip-based system
[x] IPNS has documentation explaining how it will support multiple configurations as well as guidance for users on how to select a configuration

Package Managers:

[ ] Propose a solution to allow IPFS to mirror an rsync server or portion of a filesystem
[x] Example use cases relevant to package managers
[ ] Primer for registry maintainers that makes the case for IPFS simply & effectively
[ ] Howtos on handling massive data sets (e.g. repo types, optimisation flags, gotchas, etc)
[ ] We have a prioritised roadmap for how we will become the default distribution channel for several package manager ecosystems by EOY
[ ] Bootstrap the IPFS package manager community
[ ] There are some large usable deployments of IPFS-powered package mirrors/registries
[x] Design 2x elective sessions for IPFS Camp

Updated with what looks like was completed in Q2 across all the IPFS teams


docs: update prismjs

update prismjs dependency for docs
the older version had a security issue (https://nvd.nist.gov/vuln/detail/CVE-2022-23647)

/lgtm

/approve


Add customizable unauthorized page content

Signed-off-by: Emiliano Suñé<EMAIL_ADDRESS>

Still working on updating the OpenShift configurations to account for the latest changes, will update the PR once ready to merge (and I have updated the identity-kit deployments).
@swcurran as you can see I opted for adding extra content to the base unauthorized page displaying the warning sign and the unauthorized message. I think this will be more flexible for the use case, we can further tweak it later if necessary.

OpenShift configurations tested for bc profile in test environment.


Your example rocks!

We would love to feature it on brain.js.  Also, thinking of adding that handy softmax into the lib too.  Thanks again for the awesome work!

softmax I extract and refactor from https://github.com/feylikurds/webkid-nn-js-example/blob/master/nn.js :)
This project - part of the article https://habrahabr.ru/post/304414/ (in Russian, sorry)


added missing edge case

We're really getting into some dense biz logic here. Not sure how to avoid that, but seems like it will reach a fever pitch at some point.

We're really getting into some dense biz logic here. Not sure how to avoid that, but seems like it will reach a fever pitch at some point.


fix(*): remove the Summary field in RPCAction struct

What this PR does / why we need it:
Use the Name field instead of Summary directly
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @xpofei

Release note:

NONE

/cherrypick release-0.3

/lgtm

/approve


when i submit or test code,  i get error that http error  code=301

Sending code to judge [ERROR] http error [code=301]

This (https://github.com/LeetCode-OpenSource/vscode-leetcode/issues/799#issuecomment-1120721770) addressed the problem.

try 0.18.1, feel free reopen issue if it wont resolve your issue


Browsing by gene would be nice, clicking could open up top variant for that gene.

Collapsing the variants on the browse page to allow for a unique list of genes may be nice for people searching for a specific gene but not variant.

I'm not sure I understand - by collapsing the variants, do you mean adjusting the data grid so it doesn't show more than a single row for each gene, and to list the variants in a single cell?
Also, if the use case is someone searching for a Gene, couldn't they use the gene filter box?

I agree. Let’s punt on this. Revisit it when more important matters have been addressed.

On Feb 25, 2015, at 1:57 PM, Joshua McMichael<EMAIL_ADDRESS>wrote:
I'm not sure I understand - by collapsing the variants, do you mean adjusting the data grid so it doesn't show more than a single row for each gene, and to list the variants in a single cell?
Also, if the use case is someone searching for a Gene, couldn't they use the gene filter box?
—
Reply to this email directly or view it on GitHub https://github.com/genome/civic-client/issues/35#issuecomment-76042888.

I'll go ahead and close this. The datagrid supports grouping, so I can look into that later if the current grid layout warrants it.

Yes, the gene data grid would show all of the variants collapsed to a single row for each gene. Or it could simply report the number of variants for each gene (again one row per gene).
Yes, you can search for a gene of interest or filter down to a single gene on the existing table.  But currently there is no way in CIViC to get a sense of how many genes are covered by CIVIC overall.  And how many variants of these genes?  This is something that many will want to see to get a sense of the scope/size of data in CIVIC at the level of genes (the unit, many people will be thinking of).
In order to get a sense of this now, you need to enter every gene one by one and mentally keep track of the number of rows that come back for each.
Once implemented, if you click on one of the gene rows it could just take you to the existing variant/event summary view for an arbitrary variant of that gene (by default, the one with the most evidence statements perhaps could be initially selected).  Then the user can start browsing variants of that gene.
In terms of navigation we could have 'browse variants' and 'browse genes' that took you to the two versions of the browse data grid.

I agree that this is not a short term high priority, but I think the need is high enough that we should leave this issue open for further discussion.

Is this issue more about giving users a sense of the scale of the CIViC database, or addressing user navigation/search use cases that are not provided by the Browse datagrid? I agree that we should give users a sense of the size of the db, and that we have unmet needs regarding navigation/search, but we're kind of mixing up the two problems in this issue.
I would like to split this into two issues - one that addresses a different use case for the Browse grid (searching by gene w/ clear feedback on # of variants per gene) and another that addresses giving users a sense of scale of the db.
If we want to give users a sense of the scale of the CIViC database, we can just provide them with the gene/variant counts on the homepage or around the browse datagrid itself.
If we want to group variants by gene in the Browse view, I can also work with the datagrid to see how this might be possible (using the grouping features of the grid seem like a good start).

Its not about the number of genes (although those kind of summaries would be great), it is more about the identity of those genes.  Right now I can not tell what genes are covered in CIViC without searching one-by-one for every possible gene or flipping through pages of variants and mentally building a unique list of genes, how many variants were found for each, etc.

I agree these are two issues. Summary stats of the numbers of genes, variants, evidence statements, and sources are a no-brainer that we should definitely have on the front page, side, bar or somewhere. But, as Malachi says there is also a specific (desirable) functionality to being able to easily browse through the current list of covered genes. For many people that will be the primary entry point. But, I'm not certain what the right mechanism for it is. Two layers of browse table views. Start at gene list, then get to variant list?

Do you think that your use case would be covered by a browse datagrid that could be switched between a browse-by-gene and browse-by-variant versions?
Browse by variant would show one variant per line, as we do now, and browse by gene would show one gene per line with variants aggregated into a cell or something similar.

I think that is a good idea. It would be important to make the two options clear.
Nick

On Mar 2, 2015, at 12:05 PM, Joshua McMichael<EMAIL_ADDRESS>wrote:
Do you think that your use case would be covered by a browse datagrid that could be switched between a browse-by-gene and browse-by-variant versions?
Browse by variant would show one variant per line, as we do now, and browse by gene would show one gene per line with variants aggregated into a cell or something similar.
—
Reply to this email directly or view it on GitHub.

OK, a browse grid w/ two modes is relatively straightforward to implement.

Yes, I think the dual mode datagrid the way you describe it would fantastic.

Content of a gene level view that I think would be nice from a user perspective:

Gene Symbol
Gene aliases
Variants (and count)
Evidence statements

ERBB2
Her2, etc.
V12G, R123L, etc.
25

We don't currently have any gene alias information locally. We pretty much gave up tracking gene metadata beyond entrez id and symbol, and embeds the MyGene.info data into the page. Are gene aliases something we'll want to begin storing and curating in civic?

So this may be a hacky, band-aid type fix. But really the most common gene that would be referred to by its synonym is HER2/ERBB2. Could we support searching ERBB2 variants by typing "HER2"? Or should we pull in all the synonyms?

OK, I've implemented a browse page that supports both browsing by variant, and browsing by gene. The server endpoint for browsing currently doesn't provide aliases for the genes, but that probably wouldn't be an issue. (I've created an issue over in civic-server asking for gene aliases in the /variants endpoint.)
Adding in a variant list column seems a bit pointless since most genes have far more variants than will fit in a cell. But I can do it and provide a tooltip rollover. For now we just have a variant count.
I'll leave this issue open until we're all satisfied with the new modes. Please let me know how these work for you.

We don't want to curate gene synonyms and I'm not in favor of a Her2 only solution. But, it is a very common use case that someone wants to search for a gene and uses a synonym.

@nspies13 I think we should have all synonyms.  Entrez has already invested huge resources in curating these for us.  Any name that might be used by clinicians will in all likelihood already be covered by them.  Since we can get these easily from Entrez, we can immediately handle all the ambiguities in one shot.
@jmcmichael the 'Browse by Gene' tab looks fantastic!  This is pretty much exactly what I was imagining.  Once we get the synonyms in there I think this resolves several suggestions all at once.

This is done in b88e06c3b834a1abc77b4a76e1e0c36120bb5d56. You'll need to reimport to slurp in the new aliases. I've also added support server side for searching aliases in 818cce298269efd76c506accc9275e48ff3a2cbe and it appears to be working seamlessly in the quicksearch window.

I've added aliases to the browse by gene grid and quick search box in 5d46462ffd948180f33538eacf0093903ca1f3fb.

Done.


Render menu by {{foreach navigation}}

I cannot use {{foreach navigation}} at header.hbs because it rendered nothing. How could I handle this? I know about navigation.hbs but I cannot include it in header.hbs.

Oh! So simple! This what I did:

Create a /partials/navigation.hbs
Put new navigation template in above file
Call {{navigation}} at header.hbs
Sorry because I'm new to Ghost!


Contract Invocation Panel needs Witness Scope support

The signers of a N3 transaction can specify the scope of their signatures. By default, signatures are CalledByEntry meaning "The signature is only effective to the contract script called by Entry". For example, the signer of a contract invoking ContractManagement.Deploy would not be effective for the _deploy method in the contract being deployed.
Neo Express contract deploy and contract invoke commands support the --witness-scope argument to allow the user to specify None (i.e. signature is not effective, even for the contract being directly invoked), Global (i.e. the signature is effective for the contracts being directly invoked as well as any contract it invokes) or CalledByEntry (i.e. the default)
Contract Invocation Panel at a minimum needs a mechanism to allow user to specify None, Global and CalledByEntry witness scope.
Additionally, there are two other possible WitnessScopes: CustomContracts (i.e. the caller can specify which contracts the signature is effective for) and CustomGroups (used for identifying a set of mutually trusted contracts - for example, all the contracts of a single dApp published by a single party). We can open a separate issue for tracking CustomContracts and CustomGroups support, but it would be great if we added at least CustomContracts support as part of the work to add support for None, Global and CalledByEntry
More details on witness scope here: https://docs.neo.org/docs/en-us/basic/concept/transaction.html#signers

@djnicholson and @devhawk
Just to tell you that there's some demand from our side to get this feature implemented. 😄 👍


control points 4 or 11

Hi, thanks for open-sourcing the code!
I don't quite understand the meaning of the following paragraph in the paper.
LaneDetector. The lane query number is set to NL=300, and the number of control points is 4. Duringtraining, the control points are transformed into 11 lane points forcal culating loss.
Does the above sentence mean training by 11 points and inference by 4 points? If that's what it means, how do you do it?

Because our lane head is bezier-based, it outputs 4 control points and transforms them into 11 lane points using a transformation matrix. Both training and testing are the same.

Thank you for your answer, but I still have some questions.
Where does transforms refer to here?

Please refer to this line:
https://github.com/wudongming97/TopoMLP/blob/master/projects/topomlp/models/heads/lane_head.py#L731

Thank you for your answer.