text:
Associating labels with BigQuery queries

It seems that through the BigQuery command line, it's possible to add labels to jobs / queries: https://cloud.google.com/bigquery/docs/adding-labels#adding_a_label_to_a_job
What I didn't find yet is how to set those labels through the PEP 249 DBAPI using Google's BigQuery Python library as the driver: https://cloud.google.com/python/docs/reference/bigquery/latest/dbapi
Ideally it would be possible in the creation of the DBAPI connecttion somehow
            self.client = bigquery.Client(
                project=self.project_id,
                credentials=self.credentials,
                default_query_job_config=bigquery.QueryJobConfig(
                    default_dataset=f"{self.project_id}.{self.dataset}",
                ),
                location=self.location,
                client_info=self.client_info,
                client_options=self.client_options,
            )
            self.connection = dbapi.Connection(self.client)

But I didn't find that yet.  Or alternatively it could possible to add the labels when executing the queries,
but that would be harder to implement i think.
Any suggestions?

Hi @tombaeyens,
this is a great idea to add. Labels for queries are actually quite useful !
Could you not just pass the labels attribute to the QueryJobConfig?
See https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.job.QueryJobConfig#google_cloud_bigquery_job_QueryJobConfig_labels
e.g:
self.client = bigquery.Client(
project=self.project_id,
credentials=self.credentials,
default_query_job_config=bigquery.QueryJobConfig(
default_dataset=f"{self.project_id}.{self.dataset}",
labels={"environemnt": "testing"}
),
location=self.location,
client_info=self.client_info,
client_options=self.client_options,
)

authors: tombaeyens tooobsias

repo: sodadata/soda-core


text:
cluster sequence identities falling below --min-seq-id threshold

Context
seqs.txt
I created a DB and ran the mmseqs cluster command with an alignment coverage and minimum sequence identity of 0.8. I then added sequence identity information to my clustering result by using the align command.
mmseqs createdb seqs.faa seqs_db
mmseqs cluster -c 0.8 --min-seq-id 0.8 seqs_db mmseqs80_clustered_db /tmp
mmseqs align seqs_db seqs_db mmseqs80_clustered_db alignment_db -a
mmseqs convertalis seqs_db seqs_db alignment_db align.m8
Expected Behavior
I expected all the sequence identities contained in align.m8 to be above or equal to 0.8 because of the --min-seq-id flag.
Current Behavior
I see sequence identities that fall below 0.8. These intra-cluster sequence identities fall as low as 0.55 when I cluster millions of sequences together.
align_m8.txt
Does this mean that the --min-seq-id flag is being violated or do I misunderstand how sequence identity is being computed and reported?
Your Environment
Running mmseqs2 on a cluster in a Unix terminal.
MMseqs2 Version: bc080d753c826a3f9153310f9e12b66976fba905

It is possible that the sequence identity is violated. Reason for this is the cascaded clustering. Sequences can diverge further with each iteration. However, we build a mode to correct this mistakes --cluster-reassign 1. It removes member that do not fulfill clustering criteria and tries to assign them to the remaining representative sequences.
mmseqs cluster seqs_db mmseqs80_clustered_db /tmp  --cluster-reassign 1  -c 0.8 --min-seq-id 0.8

This works great for my test case! Currently reclustering my larger dataset with the --cluster-reassign flag and hopeful that this will fix my problem. Thank you, marking this issue closed.

If you want a set of stickers (see https://twitter.com/thesteinegger/status/1201076220957315074), send me your address to milot at mirdita de.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
print statement

print statement implementation

Previously this interpreter was printing all evaluated results to stdout, whether it was in REPL or or not.
This PR introduced similar behaviour to the python -c API.
Examples of print statements and no output programs:
Evaluated program with no output:
$ cargo run '2+2'

Evaluated program with output:
$ cargo run 'print(2+2)'
4

Please squash.

swashed :point_right: f94a7c26fb72f74a262be3eb7dac837a37354643

looks like bors job crashed?
https://app.bors.tech/repositories/61986/log#batch-306900

bors r-

bors ping

source: gharchive/pull-request


text:
Enforce conventional commits

Implement pull-request and committing standards.  Utilize husky and commitizen to enforce conventional commit messages.  Create pull-request template for future commits.

Closed with f14b5b2

repo: softrams/bulwark


text:
Animation with ClipPath?

I'm trying to create an animation but nothing is happening when I put my AnimatedRect component inside of the ClipPath. The AnimatedRect does work if I move it outside of the ClipPath. Am I doing something wrong?
import React, { useEffect, useRef } from 'react';
import { View, Animated } from 'react-native';
import { Svg, Path, Rect, Defs, ClipPath } from 'react-native-svg';

const AnimatedRect = Animated.createAnimatedComponent(Rect);

function LiquidTank() {
  const liquidValue = 50;

  const factor = 1.54; // 154 / 100
  const height = factor * -liquidValue;

  const heightAnim = useRef(new Animated.Value(0)).current;

  useEffect(() => {
    heightAnim.setValue(0);
    const fillAnimation = Animated.loop(
      Animated.sequence([
        Animated.timing(heightAnim, {
          toValue: height,
          duration: 500,
          useNativeDriver: true,
        }),
        Animated.timing(heightAnim, {
          toValue: 0,
          duration: 500,
          useNativeDriver: true,
        }),
      ]),
    );
    fillAnimation.start();
  }, [height]);

  return (
    <View>
      <Svg width={250} height={100} viewBox="0 0 375 154">
        <Defs>
          <ClipPath id={`clip-${height}`}>
            <AnimatedRect x={0} y={154} width={400} height={heightAnim} />
          </ClipPath>
        </Defs>

        <Path
          fill="blue"
          clipPath={`url(#clip-${height})`}
          d="M375 77c0-26.515-13.353-50.48-33.922-67.641C335.034 4.316 327.339 2 318.606 2v150c8.733 0 17.362-2.311 23.376-7.377C362.353 127.462 375 103.506 375 77zm-56.394 75V2H56.394v150h262.212zM33.018 9.377C12.647 26.537 0 50.494 0 77c0 26.505 12.647 50.462 33.018 67.623C39.032 149.689 47.66 152 56.394 152V2C47.66 2 39.032 4.311 33.018 9.377z"
        />
        <Path
          fill="blue"
          clipPath={`url(#clip-${height})`}
          d="M86.333 0h17.334C104.955 0 105 .43 105 2.04v2.04H85V2.04C85 .43 85.045 0 86.333 0zM85 149.921v2.039c0 1.61.045 2.04 1.333 2.04h17.334c1.288 0 1.333-.43 1.333-2.04v-2.039H85z"
        />
        <Path
          fill="blue"
          clipPath={`url(#clip-${height})`}
          d="M85 4.08v145.84h20V4.079H85zM271.333 0h17.334C289.955 0 290 .43 290 2.04v2.04h-20V2.04c0-1.61.045-2.04 1.333-2.04zM270 149.921v2.039c0 1.61.045 2.04 1.333 2.04h17.334c1.288 0 1.333-.43 1.333-2.04v-2.039h-20z"
        />
        <Path fill="blue" clipPath={`url(#clip-${height})`} d="M270 4.08v145.84h20V4.079h-20z" />

        {/* It works if I move the AnimatedRect here */}
        {/* <AnimatedRect fill="#00AFEA" x={0} y={154} width={400} height={heightAnim} /> */}
      </Svg>
    </View>
  );
}

export default LiquidTank;

Which version are you using?
I didn't test the newer versions, but had similar problems on Android with v12.1.1.
Try downgrading to v12.1.0.
If this solves the issue, maybe I should reopen #1661.

Which react-native-svg version are you using?
I didn't test the newer versions, but had similar problems on Android with v12.1.1. Try downgrading to v12.1.0.
If this solves the issue, maybe I should reopen #1661.

I was using v12.1.1, but I tried downgrading to v12.1.0, and still having the same issue.
I noticed you are using reanimated in that post, but I'm using the Animated from RN itself, maybe that's the issue?
Let me try with reanimated instead.

I have the same issue!

For me, with the latest Version 14.1.0 it works fine on iOS but not on Android.

authors: ShouShou92410 aklemen buschco ghorbani-m

repo: software-mansion/react-native-svg


text:
content is not center if the viewbox origin is not (0,0)

Bug
When the viewbox's origin is not (0, 0),  and the shape of the svg width/height is not the same as viewbox. The content of the svg is not center (even explictly set preserveAspectRatio='xMidYMid meet')
  <Svg width="300" height="700" viewBox="50 50 100 100" preserveAspectRatio='xMidYMid meet'>
    <Rect x="50" y="50" width="100" height="100" fill="yellow"></Rect>
  </Svg>

Unexpected behavior
the svg content is not centered
Note, this bug seems exists only for native (iOS and Android), if I am using Expo react-native-svg in web platform, it works perfectly.

Did anyone find a workaround for this?

Did anyone find a workaround for this?

I'm just repositioning the svg by containing it in a View component then using transform.

authors: kinfkong rooksFX speedhawk21


text:
[minor] SBT complains about missing bintray credentials on startup

It's a minor thing, but SBT complains about missing bintray credentials when running tasks, that do not require those credentials, like test
[warn] Credentials file /Users/maciejb/.bintray/.artifactory does not exist

Any update on this warning?

Getting a similar error. Did you get a solution?

Should be gone now :)

authors: UtkarshaS adamw maciej pranjut

repo: softwaremill/supler

license_source: bigquery


text:
added vhost option & configs to target env

vhost is not always / for instance in cloudamqp.com the vhost is always same as the user but never / and there is no way for the developers to specify that in this package so I added that and its working.

Thank you. 🙏

authors: devsrv mhfereydouni

repo: sokanacademy/Laravel-Fluent-RabbitMQ


text:
edición de la entrada

Usar el editor ace para mejorar la edición de la entrada

Estaba pensando que ya que no queremos introducir texto tipo codigo como ace, seria mejor barajar otra opcion como quill http://quilljs.com/examples/

Uhmmm....
No estoy seguro.
quilljs me parece espartano.
ace puede ser usado para todo y lo usa c9.
Sospecho que los usuarios de tu plugin serán gente como yo, del mundo de la programación (cualquiera no se atreve a escribir  una regexp) y que muchas de las preguntas que se escriban serán relacionadas con la programación.

Ya se está usando ace y lo cambié por el input actual.

Quítale los números de línea por defecto (luego lo podrá configurar el autor):
editor.renderer.setShowGutter(false);

authors: crguezl sokartema

repo: sokartema/gitbook-plugin-jazer


text:
Extending pc integral trick to non-uniform op costs

There seems to be the likelihood that certain ops, especially memory ops (i.e. reg load, jmp which requires a random instruction seek), might need to be charged higher amount of compute units, for the reason that they can be several times slower than an alu op (100ns RAM seek is ~300x slower than an i32 add).
This is a good explanation for Serum's bad CU/us ratio, with a median of 7. That's because Serum's critbit tree data structure does a lot of random reads from a 1MB+memory region, which maybe it lives in L3 cache or even loaded cold from RAM - so dominated by opcodes 30-300x slower than ALU opcode.
In the model we consider, the majority of opcodes have a cost of 1, and they dominate.
For every expensive opcode, during emission, we increase the compute_meter by the opcode cost minus 1. Opcode extra costs are stored in an array, so one can index directly into it during instruction emission via the u8 insn.opc. The load and add instruction is not emitted when the extra cost is 0 (obviously).
At the very least, the cost of adding a constant value to the compute meter during execution, being an ALU operation, is at least comparable to the cost of an expensive operation. For instance, a memory operation will probably always have to be at least 30x CUs of an ALU, so the cost of loading the compute meter, probably living in the L1 cache, and adding a constant to it will consume far fewer cycles by comparison.
Another option is if the bpf can be analysed and segmented into basic blocks, thus reducing the need to deal with arbitrary jumps. (Edit: I guess this is ongoing work with static analysis).
For every ordinary opcode, we do nothing as per the constant 1 integral.

Thankfully, static analysis is always possible as there are no arbitrary code jumps in eBPF - jumps are always to an inlined offset.

For the reason that static analysis may be expensive in the malicious or even non-malicious scenario, I think this approach may be a good way to perform "intermediate JIT" in the non-uniform opcode cost case.
The static analysis could then only be applied to programs that live for a long time in the executor cache, as a one-time cost.

Even if the static analysis is expensive, it would probably be possible to compile asynchronously in a background thread, and silently replace the JITed binary by acquiring a write lock to the cache.

Thankfully, static analysis is always possible as there are no arbitrary code jumps in eBPF - jumps are always to an inlined offset.

Unfortunately, we have ebpf::CALL_REG (callx instruction) which is a dynamic (unpredictable) jump.

May I know if a non-uniform opcode compute unit cost table is on the horizon?

Yes, I don't see why not. In fact it is a lot simpler than you think and works with the current approach out-of-the-box.
We only have to add an explicit cumulative cost table instead of using the pc directly. There is no need to emit any extra x86 instructions for more expensive BPF instructions.

Here, I sketched a small python prototype to illustrate how it works:
import random

def generate_randomized_trace(cost_limit, cost_of):
    cumulative_cost = reduce(lambda c, x: c + [c[-1] + x], cost_of, [0])
    program_length = len(cost_of)
    interpreter_instruction_meter = 0
    jit_instruction_meter = cost_limit
    cost_limit_reached = False
    ip_pc = 0
    while True:
        if ip_pc + 1 >= program_length:
            print("Program reached the end")
            return
        interpreter_instruction_meter += cost_of[ip_pc]
        print("ip/pc={} interpreter={}/{} jit={}/{}".format(ip_pc,
            interpreter_instruction_meter, cost_limit,
            cumulative_cost[ip_pc + 1], jit_instruction_meter,
        ))
        interpreter_limit_reached = cost_limit <= interpreter_instruction_meter
        jit_limit_reached = jit_instruction_meter <= cumulative_cost[ip_pc + 1]
        if (interpreter_limit_reached or jit_limit_reached) and not cost_limit_reached:
            cost_limit_reached = True
            print("Cost limit reached by interpeter={} jit={}".format(
                interpreter_limit_reached, jit_limit_reached))
        if random.randint(0, 100) < 20:
            target_ip_pc = random.randint(0, program_length - 1)
            jit_instruction_meter -= cumulative_cost[ip_pc + 1]
            jit_instruction_meter += cumulative_cost[target_ip_pc]
            print("Jump to ip/pc={}".format(target_ip_pc))
            if cost_limit_reached:
                print("JIT aborted branch")
                return
            else:
                ip_pc = target_ip_pc
        else:
            ip_pc += 1

generate_randomized_trace(64, [random.randint(1, 3) for _ in range(0, 100)])

Which, for example generates the following trace:
ip/pc=0 interpreter=1/64 jit=1/64
ip/pc=1 interpreter=4/64 jit=4/64
ip/pc=2 interpreter=6/64 jit=6/64
ip/pc=3 interpreter=9/64 jit=9/64
ip/pc=4 interpreter=11/64 jit=11/64
Jump to ip/pc=8
ip/pc=8 interpreter=12/64 jit=17/69
Jump to ip/pc=63
ip/pc=63 interpreter=14/64 jit=128/178
ip/pc=64 interpreter=17/64 jit=131/178
Jump to ip/pc=89
ip/pc=89 interpreter=18/64 jit=177/223
ip/pc=90 interpreter=19/64 jit=178/223
ip/pc=91 interpreter=20/64 jit=179/223
ip/pc=92 interpreter=22/64 jit=181/223
Jump to ip/pc=45
ip/pc=45 interpreter=23/64 jit=90/131
ip/pc=46 interpreter=25/64 jit=92/131
ip/pc=47 interpreter=26/64 jit=93/131
ip/pc=48 interpreter=28/64 jit=95/131
Jump to ip/pc=69
ip/pc=69 interpreter=29/64 jit=142/177
ip/pc=70 interpreter=30/64 jit=143/177
ip/pc=71 interpreter=32/64 jit=145/177
ip/pc=72 interpreter=33/64 jit=146/177
Jump to ip/pc=29
ip/pc=29 interpreter=34/64 jit=59/89
ip/pc=30 interpreter=36/64 jit=61/89
ip/pc=31 interpreter=37/64 jit=62/89
ip/pc=32 interpreter=38/64 jit=63/89
ip/pc=33 interpreter=39/64 jit=64/89
ip/pc=34 interpreter=40/64 jit=65/89
ip/pc=35 interpreter=43/64 jit=68/89
ip/pc=36 interpreter=46/64 jit=71/89
ip/pc=37 interpreter=49/64 jit=74/89
ip/pc=38 interpreter=50/64 jit=75/89
ip/pc=39 interpreter=53/64 jit=78/89
ip/pc=40 interpreter=54/64 jit=79/89
ip/pc=41 interpreter=57/64 jit=82/89
Jump to ip/pc=47
ip/pc=47 interpreter=58/64 jit=93/99
ip/pc=48 interpreter=60/64 jit=95/99
ip/pc=49 interpreter=63/64 jit=98/99
ip/pc=50 interpreter=64/64 jit=99/99
Cost limit reached by interpeter=True jit=True
ip/pc=51 interpreter=67/64 jit=102/99
ip/pc=52 interpreter=68/64 jit=103/99
ip/pc=53 interpreter=71/64 jit=106/99
ip/pc=54 interpreter=73/64 jit=108/99
ip/pc=55 interpreter=76/64 jit=111/99
Jump to ip/pc=75
JIT aborted branch

So the only difference to how it currently is, is that cumulative_cost is not the identity function anymore, but the lookup can happen at compile time.

Yep, that integral trick is very elegant. Still makes me worried about long straight-line programs.

Still makes me worried about long straight-line programs.

We could emit phony branches if we detect long linear runs, but these are not particularly useful anyway.
And, yes I am aware that these programs are still turing complete and things like the movfuscator exist, but they also prove how limited this approach is as it bloats the program size tremendously.

@Lichtso my worry is not the detection per-se but rather to catch such programs in the act so they don't run for say 100ms rather than say a target 10ms.
There's actually a separate issue involved, which is that if the program throws an error or panics after it was supposed to have run out of budget, then it may return a different return type. I guess this wouldn't be a problem if every error or branch into an error also first checks the compute meter (perhaps already subsumed under the conditions for returning)

There's actually a separate issue involved, which is that if the program throws an error or panics after it was supposed to have run out of budget, then it may return a different return type

Interesting idea, might not be covered so far, but would have to write a test case for that.
This is what we currently have:
https://github.com/solana-labs/rbpf/blob/42ca251fdb77ce106a57b37f1ad353a0b0207209/src/jit.rs#L436

authors: Lichtso jon-chuang

repo: solana-labs/rbpf


text:
Specify and implement Solana Pay Transaction Requests

Rationale is covered in https://github.com/solana-labs/solana-pay/issues/26 (Note: the format described in that issue is superseded by this spec).
This PR specifies and implements Transaction Requests as a new format. Read the new spec.
This PR also substantially refactors the Transfer Request implementation (but the spec is compatible).
Todo

[ ] Fix any FIXME / TODO comments
[ ] Add tests
[ ] More docs
[ ] Document using a local HTTPS proxy
[ ] Update point-of-sale app

@PaulFidika

What is the rationale behind URI-encoding any URL query-parameters?

label and message are query params that are part of the spec. If a link used those, there would be no way to tell if they were intended for the wallet to render or intended for the link to receive.
Other query parameters may be added to the spec in the future. Therefore URL encoding a link with query parameters future proofs the link.

In general, merchants/service providers should prefer links without query parameters since they will encode in fewer characters.

Also does this specification allow for requesting signatures for the purpose of authentication? As in window.solana.signMessage()

No, this isn't a design goal. Transaction request URLs are to request a transaction that can be broadcast on Solana.
Transfer request URLs work similarly. One way or another, a transaction needs to happen on chain for the merchant to find out about it.
This could be added by future specification though! Please open an issue that describes how you see the interaction between the point of sale, merchant, wallet, and user working.

@jordansexton
Okay got it--the URL-encoding avoids query-param name collisions. It makes sense to separate the two (params meant for the wallet and params meant for the application).
Was the primary motivation for using URLs in the first place for Solana Pay compactness? I played with the idea of passing transactions as base64 encoded JSON, but the URLs were more compact every time.
I was thinking message-signing would be useful for authentication; for example, a desktop app might prompt me to scan a QR code with my Phantom-Wallet app on my phone, prompting me to sign a message which proves ownership of my Pubkey, then logging me into the desktop app.
I'll think that through a little more and then open an issue detailing my thoughts.

Was the primary motivation for using URLs in the first place for Solana Pay compactness?

No, compactness helps, but by far the most important thing for UX is that they work as deep links. A user scanning with a camera app on their phone or using an NFC tag will be prompted to launch the link in a wallet that registers itself as a handler of solana: links.

I was thinking message-signing would be useful for authentication.

I agree, this could be useful. You'd need define a way for wallets to send that signed message somewhere and for the merchant to receive it.
One way to think about Solana Pay is that it allows an application and a mobile wallet to use the chain itself to talk to each other. Transaction requests augment that, using an intermediate request to a remote server.
We could potentially add another type that makes a signing/encryption request, and the wallet would send a request to a remote server with the signed/encrypted message.
It would be important to make sure that the message being signed couldn't be a transaction message, but I think that's on the wallet to handle.

Thanks for the clarification and suggestions! That was really helpful.

We could potentially add another type that makes a signing/encryption request, and the wallet would send a request to a remote server with the signed/encrypted message.

Yes--exactly this. I'm calling this proposal 'Solana Auth' for now. Although it's not unique to Solana--this authentication method could be done with any app that controls a user's private key.
How long do you think it will take Phantom Wallet to integrate your new Transaction-Request spec and release it into production? Are we talking like weeks or months from now? I'll get in contact with their dev team this week.

~2-3 weeks. Already working on it.

Spec suggestion: what about allowing an updated message param to be returned optionally alongside the transaction in response to a transaction request?
The interaction model I'm thinking of is something like:

A QR code embeds the transaction request to solana:https://api.callumscookies.com...?label=callums cookies&message=6 cookies ($5)
The wallet displays the label + message, user confirms to initiate the API request
The API sees that the account is a loyal customer and returns:

{
   "transaction": "...", // some transaction with amount $4.50
   "message": "6 cookies (10% off)"
}

The wallet displays the previous label + new message + asks user to confirm the transaction

This would allow a vendor to give an indication of what's special about the transaction since it's account-aware, eg. a discount that has been applied or maybe "You'll receive an NFT of your new  shoes" or whatever specific features they're using for their transaction. It'd also make it less confusing if you indicated a price in the initial message (since it doesn't have an amount that might be nice to do), and then the account-aware transaction was a different price, having eg. the discount in the updated message would make it a bit clearer.

Is there a reason why I can't see the confirmation  after making the payment on screen ? I have downloaded the code from github and using solana sale-of-point as instructed..

Spec suggestion: what about allowing an updated message param to be returned optionally alongside the transaction in response to a transaction request?

Yes exactly; displaying a message in the user's wallet (along with the origin of the request) could be helpful. Although the message could be used by malicious sites to confuse the user about what they're buying or what the transaction does. Ideally by the time the user gets to the payment screen in their wallet they should already understand what they're doing.
I included a 'message' param in my spec here:
https://github.com/solana-labs/solana-pay/issues/100
let me know your thoughts, thanks.

@Ajayneueworld please ask developer support questions on Discord. We don't use Github for this, especially not on unrelated pull requests.

I think we shouldn't use HEAD as described in the new spec:

HEAD is a non standard API request that is not supported by many API clients and frameworks
HEAD is useful for browsers since it's built into the browser spec but it's not commonly used for APIs outside of html

Instead, we can define a GET request:

the path of the request will default to the same link parameter
the route will return a JSON object rather than requiring the requester to inspect the Headers

authors: Ajayneueworld PaulFidika jordansexton mcintyre94 vpontis

repo: solana-labs/solana-pay


text:
token-2022: Consider prohibiting creating non-transferable accounts without immutable ownership

Problem
It's possible to create a token account on a mint with the non-transferable extension without immutable ownership enabled. Immutable ownership is enforced during minting, so it's impossible to mint a non-transferable token to an account without immutable ownership.
This can be confusing, because it seems like it might be possible to have non-transferable tokens in an account with transferable ownership.
Solution
Consider throwing an error when trying to initialize a token account on a non-transferable mint without immutable ownership.

So, if I'm understanding this correctly:

In order to mint tokens to a non-transferable account, that destination must have an immutable owner
In order to transfer tokens from a non-transferable account, you can't

What would be the reason to allow creating a non-immutable owner token account on a non-transferable mint? I would say this only makes sense if the non-transferable extension can be removed, which at the moment it does not appear is the case.

What would be the reason to allow creating a non-immutable owner token account on a non-transferable mint?

I can't remember why we did it that way. It looks like it was just done like that in https://github.com/solana-labs/solana-program-library/pull/2912 without any other questions.

In order to transfer tokens from a non-transferable account, you can't

Also, lol

Can I try this issue? I'm going to

Can I have a try on this issue,
I will return the NonTransferableNeedsImmutableOwnership error when trying to initialize an account on a non-transferable mint without immutable ownership.

Yep that's the idea, and no need to ask for permission, go for it! We'll review your PR when it comes in

Fixed in #6206

authors: buffalojoec joncinque quminghaonanya

repo: solana-labs/solana-program-library


text:
js: Add option to skipPreflight for token and token-swap clients - MLH

Solves #1653

Looks great, thanks for your patience!


text:
Add scarce logo and

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Failed format

repo: solana-labs/token-list


text:
add Trick token

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: TrickCA8nD77Y6iHHEQBAaBFDjFa5zohSThmSVfz2X9
Token Name: SolTricks token
Token Symbol: Trick
Logo: http://static.soltricks.io/icon.png
Link to the official homepage of token: https://soltricks.io
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_): null

Hi, I'm trying to add SolaLambo token but I'm receiving error message talking about deletions without deleting any of the file, can you please put me through on how to added trick token or possibly help add sob token. See the necessary details below:
{
"chainId": 101,
"address": "EkDf4Nt89x4Usnxkj4sGHX7sWxkmmpiBzA4qdDkgEN6b",
"symbol": "SOB",
"name": "SolaLambo",
"decimals": 9,
"logoURI": "https://i.postimg.cc/Wz2q6C0j/SOLA-LAMBO-2.png",
"tags": [community-token],
"extensions": {
"website": "https://sob.finance",
"discord": "https://discord.gg/sy2xymyc7J",
"twitter": "https://twitter.com/SolaLambo"
}
},

@SolaLambo  Contact me on telegram : @wei1769


text:
Update solana.tokenlist.json

[ ] I will not ping the Discord about this pull request.

Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

no website

authors: DanBzl bartosz-lipinski


text:
Add Komo

[x] I will not ping the Discord about this pull request.

Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR
At minimum each entry should have

Token Address: HHgh3QC7FQEC5HM1bvRKgP6MbQ851pxWaerULqe4YYHN
Token Name: Komo Network
Token Symbol: KOMO
Logo https://cdn.jsdelivr.net/gh/mesowea/afsgfdhg/Komo.png
Twitter: https://twitter.com/Komo_net
Link to the official homepage of token: we don't plan to make a website in the first place

Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Hi @mvines. Everything is dont, is it possible to solve this? We are trying to issue our token on mainnet.
Thanks a lot

fixed (missed coma XD)

@mvines Hello! Please, help us


text:
Port to FreeRTOS

FreeRTOS is an operating system that supports many IoT boards. It would be nice to port Soletta to that operating system.
Likely the port will be based on the one for other small OS such as RIOT.

Any plans on this issue?

@ronaldotd started but never had time to finish the basics. You can check with him for his early stage code and continue if you want to do it.

@barbieri Thanks for the prompt reply
I just wanted to check if Soletta would work in a esp8266 running FreeRTOS. Unfortunately I don't have time nor experience on this kind of porting at the moment. I'll keep an eye on it though

authors: barbieri thiagogcm

repo: solettaproject/soletta


text:
Visually differentiate between enabled and disabled schedules

Currently, enabled and disabled schedules look the same on the calendar. It would be preferable if one could at a glance know which ones are enabled and which ones are not (when all schedules are shown).
Ideally, the color coding would also preserve the type of schedule. Maybe use a darker shade for enabled scheduled, and a light shade of the same schedule type, to indicate it's disabled?
Alternatively, instead of messing with the fill color, we could use some type of icon, strike-through text, greyed out text, etc, to indicate the schedule is disabled.
Or we could just use a dedicated color for any disabled scheduled, regardless of schedule type.
Whatever is easiest now, we can refactor into a more visually appealing solution later on.

Was just going to suggest the same feature and found this. I have a number of disabled schedules which all appeared on the calendar and looked like they were active - I had to go and double check in the Admin Console to make sure these were still disabled. Would be great if we could toggle these on/off or have them differentiated in some way as per the above suggestions.

authors: databuzz jeremiahsmall

repo: soliantconsulting/fms-ace


text:
WebIDs MUST use a secure protocol

All resources used in the context of Solid Authentication and Authorization MUST use a secure protocol.
Namely, a WebID used for Authentication MUST use the https protocol. That is true of both client and user WebIDs.
Currently, the specification states: "a WebID is a HTTP URI". I couldn't find any specific requirements about security in transit.
I appreciate that it seems a bit like stating the obvious, but I reckon it is fundamentally important enough to require an extension of section 3, probably with a 3.2 Encryption of WebIDs in transit.
See also: https://www.ncsc.gov.uk/collection/cloud-security/implementing-the-cloud-security-principles/data-in-transit-protection

If the WebID is supposed to be public why does it need to be transmitted in a secure manner? What is it hiding? What does the secure transmission of a public document add?

How do you tamper with the integrity of a HTTP request?

How do you tamper with the integrity of a HTTP request?

Any MITM attack would allow one to tamper with an HTTP exchange. The specific details depend on the specific target of the attack and the resources available to the attacker.

authors: acoburn awhillas matthieubosquet

repo: solid/solid-oidc


text:
loadParsedGraphs uses response.url

fixes #5

Good catch, thanks!

authors: dmitrizagidulin elf-pavlik

repo: solid/solid-web-client

license: mit


text:
Implement Transition and TransitionGroup using solid-primitives

Continues on changes in #30 (vite playground was replaced with astro one to test hydration/ssr)
This reimplements the Transition and TransitionGroup components using the @solid-primitives/transition-group and @solid-primitives/refs packages. So that the low-level and likely-to-change implementation details — such as resolving JSX structure, diffing it in a pure computation, and updating a signal with a list of elements to display — can be maintained in a single place and reused in different solid transition libraries (solid-transiotion-group, solid-flip, motionone/solid, etc.).
It's fairly tested with unit tests as well so some of the edge-cases got eliminated:
Fixes https://github.com/solidjs/solid-transition-group/issues/20 - covered by unit tests
Fixes https://github.com/solidjs/solid-transition-group/issues/15 - appear works well with all transition modes
Fixes https://github.com/solidjs/solid-transition-group/issues/7 - initial elements always get rendered on the server. Then on the client, the transition will run only if appear is enabled. (SSRd elements do not have the enter classes - those need to be applied by the user)
Additionally, it adds appear option to TransitionGroup - previously it wasn't supported.
The logic of applying CSS classes / scheduling animations / moving elements to the new positions is left unchanged.
Similar PR to motionone: https://github.com/motiondivision/motionone/pull/176

@thetarnav core has decided to accept the PR and also download the responsibility of solid-transition-group to SolidJS Community. I'll transfer it tomorrow and setup a team to manage the package.
Seriously, thank you for putting the effort into this. You're contributions are so appreciated in this community. You are definitely the backbone of the ecosystem. :)

authors: davedbase thetarnav

repo: solidjs/solid-transition-group


text:
Added default ERC 1155 receiver

Added a default implementation of ERC 1155 receiver to solve this open issues
https://github.com/solidstate-network/solidstate-solidity/issues/98

This won't work, because it would require us to add OpenZeppelin as a dependency in package.json.  We can't do this because Hardhat doesn't support nested Solidity dependencies in combination with all common package managers - I believe pnpm, for example, uses a directory structure Hardhat doesn't recognize.
What we need for issue #98 is a custom contract (or a port of the OZ version) included directly within the SolidState package.

authors: ItsNickBarry nonfungibleayo-eth

repo: solidstate-network/solidstate-solidity


text:
Wrong Java import

In the docs it says:
import com.solinor.RNBluetoothManagerPackage;

but in fact, it's:
import com.reactlibrary.RNBluetoothManagerPackage;

There is now 1.1 published in npm, which should fix this.

I have same problem with RNBluetoothManagerPackage
import com.reactlibrary.RNBluetoothManagerPackage;

Hmm yeah, it is actually com.solinor.bluetoothstatus.RNBluetoothManagerPackage now, fixing documentation to match.

authors: MBach eduplus smartdevdom

repo: solinor/react-native-bluetooth-status


text:
Strange Boolean behaviour

irb(main):016:0> Virtus::Attribute.build(true).is_a?(Virtus::Attribute::Boolean)
=> true
irb(main):017:0> Virtus::Attribute.build(false).is_a?(Virtus::Attribute::Boolean)
=> false

Found it out while investigating a bug in grape.

Yeah, looks like FalseClass isn't listed as a primitive for it: https://github.com/solnic/virtus/blob/master/lib/virtus/attribute/boolean.rb#L18

It also looks like only one primitive type can be set.
(Oh, Ruby, TrueClass and FalseClass, seriously? =))

Ruby has no primitive types.

I meant primitive attribute of Virtus::Attribute class.

@envygeeks Virtus::Attribute has a primitive accessor: https://github.com/solnic/virtus/blob/master/lib/virtus/attribute.rb#L51

authors: acook envygeeks ktimothy

repo: solnic/virtus


text:
🛑 zakazbiletov.kz is down

In 7b1131d, zakazbiletov.kz (https://zakazbiletov.kz/) was down:

HTTP code: 500
Response time: 4420 ms

Resolved: zakazbiletov.kz is back up in b11def0 after 246 days, 16 hours, 41 minutes.


text:
problems with ng build --prod

when i try to run the command ng build --prod
the terminal shows messages like Property 'SearchText' doesn't exist on Type Component...
this is my html
<input   [(ngModel)]="searchText">

...

sorry, i had not declared searchText in Component.


text:
field report

Win10, 1809

Solo Hacker 2.5.1, wants to update, goes to Solo Bootloader 2.2.2. Error: ReferenceError: CTAP1_ERR_INVALID_COMMAND is not defined
Solo 2.5.2, manually to Solo Bootloader 2.5.2: Same error

App crashes sometimes (not sure how to debug reason on Windows 😁)
Competition gets listed with interesting serial:

using 8.1 here, looks fine with my hackersolo and Yubi 4 Nano (post ROCA)

That fixed the CTAP1_ERR_INVALID_COMMAND for me on 1903.

Can you run it from cmd prompt and past the output when it hangs?

Running in production
list
Error getting CTAP2 info. 11
reply to  list
list

@aseigler what FIDO devices do you have plugged in?

@aseigler what FIDO devices do you have plugged in?

Good call, by trial and error the problem device is Feitian BioPASSFIDO2.  Both K27 and K33 cause the command line error to be logged, the K27 causes a hang about 50% of the time, if I unplug that device it unblocks.

authors: My1 aseigler conorpp nickray

repo: solokeys/solo-desktop


text:
fail to compile from repo

Tried to compile solo2 from the repo in order to get rid of the need to have a smartcard in my reader (which is built into ma laptop). But build fails.
Here's what I did:
git clone https://github.com/solokeys/solo2-cli.git solo2
cd solo2/
cargo build

Build runs fine for quite a while, but finally fails with this error message:
   Compiling solo2 v0.1.2 (/home/user/temp/solo2)
   Compiling serde_yaml v0.8.23
   Compiling serde-big-array v0.3.2
   Compiling toml v0.5.8
   Compiling ureq v2.4.0
error: there is no argument named `uuid`
   --> src/bin/solo2/main.rs:336:61
    |
336 |                     let url = format!("https://s2pki.net/s2/{uuid}/x255.txt");
    |                                                             ^^^^^^

error: could not compile `solo2` due to previous error

LinuxMint 20.3 (underlying Ubuntu 20.04) running here, rustc 1.57.0+dfsg1+llvm-0ubuntu1~20.04.1, cargo 0.58.0-0ubuntu1~20.04.1, gcc 9.3.0
I'd be happy to provide more info, pls feel free to ask.

You need to update to Rust 1.58 for the "format strings": https://blog.rust-lang.org/2022/01/13/Rust-1.58.0.html#captured-identifiers-in-format-strings.
I'll bump the rust-version entry in Cargo.toml.


text:
Default octodns_ref is v0.9.12

Description

Default octodns_ref is v0.9.12, which is not the most recent release of octodns/octodns.
Expected Behavior

I'd expect it to be v0.9.14 currently, or master.
Actual Behavior

Default octodns_ref is v0.9.12
Possible Fix

Automatically update it to the latest release; Pin it to master; Or explain why it'll stay v0.9.12.
Steps to Reproduce

Run solvaholic/octodns-sync without specifying octodns_ref
Context

Troubleshooting issues in solvahol/dns, I want to run the latest octodns/octodns.
Your Environment

Version used: main
Link to your project: solvahol/dns

The notion of "a version of octodns/octodns" is changing (see #86). So, for this issue, I'll just bump the default octodns/octodns to v0.9.14 for now.

repo: solvaholic/octodns-sync


text:
chore: remove chart from the main repository

Description
This PR removes the helm chart from the core repository in favours of our helm-chart repo
Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Thanks!

We should update the documentation first: https://github.com/someengineering/resoto.com/blob/main/docs/getting-started/install-resoto/kubernetes.md
Please also remove the helm chart workflow.

authors: aquamatthias kushthedude

repo: someengineering/resoto


text:
Fix #38: Don't update patient if the selected node is not a patient one

Also allow other node selection use cases.

The logic may have unintended side effects, as I'm using the group attribute for the node in the Graph visualization library you're using. Although it is used to segregate styles, I feel it works well in distinguishing node types. This will help in filtering node selection events later on.

Looks good, merging. Great work!

authors: SahajR someshkar


text:
Refactor version support

The version handler was not able to support npm/yarn semantic ranges sufficiently, resulting in exceptions. A hack was added to work around the exceptions, but the version handling code should be upgraded to properly handle semantic ranges.
In addition, in cases where there is a lock file, it is best that DevAudit check both the first version in the range, as well as the version specified in the lock file, in order to have a better chance at detecting vulnerable packages in use. This solution is not perfect, but is significantly better.

Closing old tickets. We can recreate it on the internal system.

repo: sonatype-nexus-community/DevAudit


text:
[Thinkit] Add first version of test verifying DSCP-to-queue mapping for packets to CPU.

Keyword Check:
sdivya@eonms6vm1:~/sonic_sep6/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/keyword_check.sh .
Keyword check Passed.
Build and Test Results:
sdivya@6177511caa2d:/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 572 targets (0 packages loaded, 342 targets configured).
INFO: Found 386 targets and 186 test targets...
INFO: Elapsed time: 183.814s, Critical Path: 122.27s
INFO: 240 processes: 283 linux-sandbox, 18 local.
INFO: Build completed successfully, 240 total actions
//gutil:collections_test                                                 PASSED in 0.7s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 1.1s
//gutil:proto_ordering_test                                              PASSED in 0.6s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.5s
//gutil:test_artifact_writer_test                                        PASSED in 0.6s
//gutil:testing_test                                                     PASSED in 0.6s
//gutil:timer_test                                                       PASSED in 5.1s
//gutil:version_test                                                     PASSED in 0.9s
//lib:basic_switch_test                                                  PASSED in 0.9s
//lib:ixia_helper_test                                                   PASSED in 1.3s
//lib/basic_traffic:basic_p4rt_util_test                                 PASSED in 0.9s
//lib/basic_traffic:basic_traffic_test                                   PASSED in 15.0s
//lib/gnmi:gnmi_helper_test                                              PASSED in 3.0s
//lib/gnoi:gnoi_helper_test                                              PASSED in 0.5s
//lib/p4rt:p4rt_port_test                                                PASSED in 0.5s
//lib/p4rt:p4rt_programming_context_test                                 PASSED in 0.8s
//lib/utils:generic_testbed_utils_test                                   PASSED in 1.3s
//lib/utils:json_utils_test                                              PASSED in 0.5s
//lib/validator:validator_backend_test                                   PASSED in 0.5s
//lib/validator:validator_lib_test                                       PASSED in 25.9s
//p4_fuzzer:constraints_test                                             PASSED in 3.3s
//p4_fuzzer:fuzz_util_test                                               PASSED in 122.2s
//p4_fuzzer:fuzzer_config_test                                           PASSED in 0.7s
//p4_fuzzer:oracle_util_test                                             PASSED in 2.6s
//p4_fuzzer:switch_state_assert_entry_equality_test                      PASSED in 2.1s
//p4_fuzzer:switch_state_assert_entry_equality_test_runner               PASSED in 2.5s
//p4_fuzzer:switch_state_test                                            PASSED in 0.9s
//p4_pdpi:built_ins_test                                                 PASSED in 0.6s
//p4_pdpi:entity_keys_test                                               PASSED in 0.6s
//p4_pdpi:ir_properties_test                                             PASSED in 0.8s
//p4_pdpi:ir_to_ir_test                                                  PASSED in 0.6s
//p4_pdpi:ir_tools_test                                                  PASSED in 0.7s
//p4_pdpi:names_test                                                     PASSED in 0.7s
//p4_pdpi:p4_runtime_matchers_test                                       PASSED in 0.6s
//p4_pdpi:reference_annotations_test                                     PASSED in 0.7s
//p4_pdpi:references_test                                                PASSED in 0.6s
//p4_pdpi:sequencing_util_test                                           PASSED in 0.6s
//p4_pdpi/netaddr:ipv4_address_and_network_address_test                  PASSED in 0.6s
//p4_pdpi/netaddr:ipv6_address_test                                      PASSED in 0.5s
//p4_pdpi/netaddr:mac_address_test                                       PASSED in 0.7s
//p4_pdpi/packetlib:packetlib_fuzzer_test                                PASSED in 17.3s
//p4_pdpi/packetlib:packetlib_matchers_test                              PASSED in 0.5s
//p4_pdpi/packetlib:packetlib_test                                       PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_test_runner                                PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_unit_test                                  PASSED in 1.7s
//p4_pdpi/string_encodings:bit_string_test                               PASSED in 0.5s
//p4_pdpi/string_encodings:byte_string_test                              PASSED in 0.5s
//p4_pdpi/string_encodings:decimal_string_test                           PASSED in 0.0s
//p4_pdpi/string_encodings:decimal_string_test_runner                    PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test                               PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test_runner                        PASSED in 0.1s
//p4_pdpi/string_encodings:readable_byte_string_test                     PASSED in 0.5s
//p4_pdpi/testing:helper_function_test                                   PASSED in 0.7s
//p4_pdpi/testing:info_test                                              PASSED in 0.1s
//p4_pdpi/testing:info_test_runner                                       PASSED in 0.1s
//p4_pdpi/testing:main_pd_test                                           PASSED in 0.0s
//p4_pdpi/testing:mock_p4_runtime_server_test                            PASSED in 1.0s
//p4_pdpi/testing:old_get_entries_unreachable_from_roots_with_matchfield_reference_test PASSED in 0.1s
//p4_pdpi/testing:old_get_entries_unreachable_from_roots_with_matchfield_reference_test_runner PASSED in 0.1s
//p4_pdpi/testing:packet_io_test                                         PASSED in 0.1s
//p4_pdpi/testing:packet_io_test_runner                                  PASSED in 0.1s
//p4_pdpi/testing:references_test                                        PASSED in 0.1s
//p4_pdpi/testing:references_test_runner                                 PASSED in 0.1s
//p4_pdpi/testing:rpc_test                                               PASSED in 0.1s
//p4_pdpi/testing:rpc_test_runner                                        PASSED in 0.2s
//p4_pdpi/testing:sequencing_test                                        PASSED in 0.1s
//p4_pdpi/testing:sequencing_test_runner                                 PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test                                   PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test_runner                            PASSED in 0.0s
//p4_pdpi/testing:table_entry_gunit_test                                 PASSED in 0.8s
//p4_pdpi/testing:table_entry_test                                       PASSED in 0.1s
//p4_pdpi/testing:table_entry_test_runner                                PASSED in 0.2s
//p4_pdpi/utils:annotation_parser_test                                   PASSED in 0.5s
//p4_pdpi/utils:ir_test                                                  PASSED in 0.6s
//p4_symbolic:z3_util_test                                               PASSED in 0.5s
//p4_symbolic/bmv2:ipv4_routing_exact_test                               PASSED in 0.1s
//p4_symbolic/bmv2:ipv4_routing_subset_test                              PASSED in 0.1s
//p4_symbolic/bmv2:port_hardcoded_exact_test                             PASSED in 0.0s
//p4_symbolic/bmv2:port_hardcoded_subset_test                            PASSED in 0.1s
//p4_symbolic/bmv2:port_table_exact_test                                 PASSED in 0.0s
//p4_symbolic/bmv2:port_table_subset_test                                PASSED in 0.1s
//p4_symbolic/bmv2:reflector_exact_test                                  PASSED in 0.0s
//p4_symbolic/bmv2:reflector_subset_test                                 PASSED in 0.1s
//p4_symbolic/bmv2:set_invalid_exact_test                                PASSED in 0.0s
//p4_symbolic/bmv2:set_invalid_subset_test                               PASSED in 0.1s
//p4_symbolic/bmv2:table_hit_1_exact_test                                PASSED in 0.0s
//p4_symbolic/bmv2:table_hit_1_subset_test                               PASSED in 0.1s
//p4_symbolic/bmv2:table_hit_2_exact_test                                PASSED in 0.0s
//p4_symbolic/bmv2:table_hit_2_subset_test                               PASSED in 0.1s
//p4_symbolic/ir:cfg_test                                                PASSED in 0.5s
//p4_symbolic/ir:complex_conditional_test                                PASSED in 0.0s
//p4_symbolic/ir:conditional_sequence_test                               PASSED in 0.0s
//p4_symbolic/ir:ipv4_routing_test                                       PASSED in 0.0s
//p4_symbolic/ir:port_hardcoded_test                                     PASSED in 0.0s
//p4_symbolic/ir:port_table_test                                         PASSED in 0.1s
//p4_symbolic/ir:reflector_test                                          PASSED in 0.0s
//p4_symbolic/ir:set_invalid_test                                        PASSED in 0.1s
//p4_symbolic/ir:table_hit_1_test                                        PASSED in 0.0s
//p4_symbolic/ir:table_hit_2_test                                        PASSED in 0.0s
//p4_symbolic/symbolic:conditional_sequence_test_output                  PASSED in 0.1s
//p4_symbolic/symbolic:condtional_test_output                            PASSED in 0.1s
//p4_symbolic/symbolic:ipv4_routing_test_output                          PASSED in 0.0s
//p4_symbolic/symbolic:port_hardcoded_test_output                        PASSED in 0.0s
//p4_symbolic/symbolic:port_table_test_output                            PASSED in 0.0s
//p4_symbolic/symbolic:reflector_test_output                             PASSED in 0.1s
//p4_symbolic/symbolic:string_optional_test_output                       PASSED in 0.0s
//p4_symbolic/symbolic:values_test                                       PASSED in 0.6s
//p4_symbolic/tests:sai_p4_component_test                                PASSED in 1.4s
//p4rt_app/event_monitoring:app_state_db_port_table_event_test           PASSED in 1.0s
//p4rt_app/event_monitoring:app_state_db_send_to_ingress_port_table_event_test PASSED in 1.0s
//p4rt_app/event_monitoring:config_db_cpu_queue_table_event_test         PASSED in 1.4s
//p4rt_app/event_monitoring:config_db_node_cfg_table_event_test          PASSED in 1.1s
//p4rt_app/event_monitoring:config_db_port_table_event_test              PASSED in 1.1s
//p4rt_app/event_monitoring:debug_data_dump_events_test                  PASSED in 1.1s
//p4rt_app/event_monitoring:state_verification_events_test               PASSED in 1.0s
//p4rt_app/p4runtime:cpu_queue_translator_test                           PASSED in 0.8s
//p4rt_app/p4runtime:ir_translation_test                                 PASSED in 0.8s
//p4rt_app/p4runtime:p4info_verification_schema_test                     PASSED in 0.8s
//p4rt_app/p4runtime:p4info_verification_test                            PASSED in 1.1s
//p4rt_app/p4runtime:packetio_helpers_test                               PASSED in 1.0s
//p4rt_app/p4runtime:resource_utilization_test                           PASSED in 1.0s
//p4rt_app/sonic:app_db_acl_def_table_manager_test                       PASSED in 0.8s
//p4rt_app/sonic:app_db_manager_test                                     PASSED in 0.8s
//p4rt_app/sonic:app_db_to_pdpi_ir_translator_test                       PASSED in 0.9s
//p4rt_app/sonic:hashing_test                                            PASSED in 0.9s
//p4rt_app/sonic:packet_replication_entry_translation_test               PASSED in 0.8s
//p4rt_app/sonic:packetio_impl_test                                      PASSED in 0.7s
//p4rt_app/sonic:packetio_port_test                                      PASSED in 0.6s
//p4rt_app/sonic:response_handler_test                                   PASSED in 1.0s
//p4rt_app/sonic:state_verification_test                                 PASSED in 0.8s
//p4rt_app/sonic:vrf_entry_translation_test                              PASSED in 0.7s
//p4rt_app/sonic/adapters:fake_sonic_db_table_test                       PASSED in 0.1s
//p4rt_app/sonic/adapters:fake_warm_boot_state_adapter_test              PASSED in 0.0s
//p4rt_app/tests:acl_table_test                                          PASSED in 2.2s
//p4rt_app/tests:action_set_test                                         PASSED in 1.5s
//p4rt_app/tests:api_access_test                                         PASSED in 1.2s
//p4rt_app/tests:arbitration_test                                        PASSED in 1.6s
//p4rt_app/tests:cpu_queue_name_and_id_test                              PASSED in 2.9s
//p4rt_app/tests:debug_data_dump_test                                    PASSED in 1.3s
//p4rt_app/tests:fixed_l3_tables_test                                    PASSED in 4.6s
//p4rt_app/tests:forwarding_pipeline_config_test                         PASSED in 9.1s
//p4rt_app/tests:grpc_behavior_test                                      PASSED in 5.5s
//p4rt_app/tests:p4_constraints_test                                     PASSED in 0.3s
//p4rt_app/tests:p4_constraints_test_runner                              PASSED in 0.5s
//p4rt_app/tests:p4_programs_test                                        PASSED in 2.6s
//p4rt_app/tests:packet_replication_table_test                           PASSED in 2.6s
//p4rt_app/tests:packetio_test                                           PASSED in 4.9s
//p4rt_app/tests:port_name_and_id_test                                   PASSED in 4.7s
//p4rt_app/tests:resource_limits_test                                    PASSED in 5.7s
//p4rt_app/tests:response_path_test                                      PASSED in 5.6s
//p4rt_app/tests:role_test                                               PASSED in 1.5s
//p4rt_app/tests:state_verification_test                                 PASSED in 2.7s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.6s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.1s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.7s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.1s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.8s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.9s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.1s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.7s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.2s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 1.3s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 1.0s
//sai_p4/instantiations/google/tests:p4_fuzzer_integration_test          PASSED in 3.6s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.7s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.9s
//thinkit:bazel_test_environment_test                                    PASSED in 0.6s
//thinkit:generic_testbed_test                                           PASSED in 0.9s
//thinkit:mock_control_device_test                                       PASSED in 0.9s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.7s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.6s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.9s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.8s
Stats over 5 runs: max = 0.8s, min = 0.7s, avg = 0.8s, dev = 0.1s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 45.0s
Stats over 50 runs: max = 45.0s, min = 0.8s, avg = 2.1s, dev = 6.3s
Executed 186 out of 186 tests: 186 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these a
INFO: Build completed successfully, 240 total actions
sdivya@6177511caa2d:/sonic/src/sonic-p4rt/sonic-pins$

Co-authored-by: Steffen Smolka smolkaj@google.com

repo: sonic-net/sonic-pins


text:
Resolve asset spec as path if a file exists with that path

Fixed the issue described here: https://github.com/sontek/pyramid_webassets/issues/57
For file paths on windows, the path was treated as a package due to having a colon in it.
With the fix, any asset spec will first be checked to see if it is a local file path before being treated as a package.

Excellent! It's been a while since I looked at this repo, but this looks good. It would be nice to make sure it's covered by the test suite. If you can add a test, that'd be great. I'll take a look over the weekend and see if I can recommend any way to test it if it's not obvious to you.

Can you fix a couple things before I merge this, please?

We should return (None, item) rather than (__name__, item) because that's the signal that this string is not an asset spec and has no package part. When this happens, depending on why we were checking, we do things that this PR might break, such as calling the parent class to check relative paths in all the configured asset directories.

Sometimes, the file may not exist but it's still meant to be treated as a file. I'm not positive, but this could be the case if, for example, an absolute Windows file path is used as an output path. Instead of checking "isfile", I think we should check whether the start of the path ismount().

The first change you request results in a type error, which is why I went with name in the first place, as a hack-y workaround. I'm not sure how to avoid this.
The second change is implemented and pushed.

Coverage decreased (-0.4%) to 91.284% when pulling 03fcc1a31e42d7363d5d61fd6f80a9d18311f3c3 on viningM:master into 060b5320dd646faf89893b70a7c26e11b5133ba9 on sontek:master.

Hmm, there should be no type error. Other code paths return None as the first of that tuple, but I'll look into it.
Looking at your patch now, it's still not quite right. The ismount has to be called on the mount point, I think. I'm not on a windows machine right now, but I think ismount would only succeed for something like "C:" or "C:" or UNC mounts. The whole item is string, such as "package:path/to/asset" or "C:\static\path\to\asset", will not return True for ismount.

Unfortunately I'm out of time to poke at it, I'll leave to you to fix or ignore.
Best of luck

authors: coveralls tilgovi viningM


text:
How to get or use network from nnp

Hi.
Neural Network Console of Windows provides h5 file and Python code. And Cloud version provides just nnp file. I know the nnp file has h5 and network of protocol buffers. But I don't know how to use network in nnp file.
Usally we can get the python code like below.
import nnabla as nn
import nnabla.functions as F
import nnabla.parametric_functions as PF

def network(x, y, test=False):
    # Input:x -> 1,28,28
    # MaxPooling -> 1,14,14
    h = F.max_pooling(x, (2,2), (2,2))
    # Affine -> 100
    h = PF.affine(h, (100,), name='Affine')
    # ReLU
    h = F.relu(h, True)
    # Affine_2 -> 1
    h = PF.affine(h, (1,), name='Affine_2')
    # Sigmoid
    h = F.sigmoid(h)
    # BinaryCrossEntropy
    h = F.binary_cross_entropy(h, y)
    return h

And we don't neet BinaryCrossEntropy, so delete it. The nnp file's network has it.
import nnabla as nn
import nnabla.functions as F
import nnabla.parametric_functions as PF
from nnabla.utils import nnp_graph

nnp = nnp_graph.NnpLoader('./result.nnp')
graph = nnp.get_network('MainValidation')
y = graph.outputs
print(y)

This code outputs below.
{'BinaryCrossEntropy': <Variable((64, 1), need_grad=True) at 0x114f926d8>}

I hope use the nnp in Python like below.
import nnabla as nn

nn.load_parameters('./result.nnp')
graph = nn.get_network('MainValidation')
x = graph.inputs['x']
y = graph.outputs['y']
y.forward(x, test=True)
y.d

How to use network in the nnp file?
I know nnabla_cli can do it. But I don't know how to do it.
Thanks

I can use the nnp file like below.
def image():
     :
    x = nn.Variable((1,1,28,28))
    x.d = np.array(img) * (1.0 / 255.0)
    y = network(x, test=True)
    y.forward()
     :

def network(x, test=False):
    # Input:x -> 1,28,28
    # MaxPooling -> 1,14,14
    h = F.max_pooling(x, (2,2), (2,2))
    # Affine -> 100
    h = PF.affine(h, (100,), name='Affine')
    # ReLU
    h = F.relu(h, True)
    # Affine_2
    h = PF.affine(h, (1,), name='Affine_2')
    # Sigmoid
    h = F.sigmoid(h)
    return h

But I think I don't need to write network method if I'm using nnp file. 'cause it is contained network by protocol buffer.

This is NOT completely code.
import nnabla as nn
import nnabla.functions as F
import nnabla.parametric_functions as PF
from nnabla.utils import nnp_graph

nnp = nnp_graph.NnpLoader('./result.nnp')
print(nnp.get_network_names())
graph = nnp.get_network('MainRuntime', batch_size=1)
x = graph.inputs['Input'][0]
print(x)
y = graph.outputs
print(y)

Output:
# print(nnp.get_network_names())
['Main', 'MainValidation', 'MainRuntime']
# print(x)
<Variable((1, 28, 28), need_grad=False) at 0x11e7a6728>
# print(y)
{'Sigmoid': <Variable((1, 1), need_grad=True) at 0x11e7a6638>}

If I'm using Main or MainValidation network, output is below.
# print(x)
<Variable((1, 28, 28), need_grad=False) at 0x11a08c818>
# print(y)
{'BinaryCrossEntropy': <Variable((1, 1), need_grad=True) at 0x11a08c728>}

I can't find out variable x and y from graph.inputs and graph.outputs looks like sample code. And I don't know what is Nnp method.
# Read a .nnp file.
nnp = Nnp('/path/to/nnp.nnp')
# Assume a graph `graph_a` is in the nnp file.
net = nnp.get_network(network_name, batch_size=1)
# `x` is an input of the graph.
x = net.inputs['x']
# 'y' is an outputs of the graph.
y = net.outputs['y']
# Set random data as input and perform forward prop.
x.d = np.random.randn(x.shape)
y.forward(clear_buffer=True)
print('output:', y.d)

https://nnabla.readthedocs.io/en/latest/_modules/nnabla/utils/nnp_graph.html
I have attached my nnp file.
Thanks.
result.nnp.zip

I did it.
from nnabla.utils import nnp_graph
import numpy as np
from PIL import Image

nnp = nnp_graph.NnpLoader('./result.nnp')
graph = nnp.get_network('MainRuntime', batch_size=1)
# Input variable name
input = list(graph.inputs.keys())[0]
# Output variable name
output = list(graph.outputs.keys())[0]
# Get input and output
x = graph.inputs[input]
y = graph.outputs[output]
# Open image
img = Image.open('001.png')
# Transform
x.d = np.array(img) * (1.0 / 255.0)
# Forward
y.forward(clear_buffer=True)
print(y.d)

repo: sony/nnabla


text:
COM-1504 max-length demo for title-text

[x] J'ai verifié la fonctionnalite sur mobile

Périmetre interface : ROF

Périmetre roles : vendeur

Cas d'usage : limite à 150 caractères pour les questions d'une carte

Dans updateCorrectAnswer de MultipleChoiceQuestion.vue il faut ajouter une condition sur le fait que le label est correct (en plus du fait qu'il existe). Sinon si on met un label de + de 50 caracteres et qu'on appuie sur la checkbox, le back nous renvoie une erreur.

done!

repo: sophiemoustard/alenvi-webapp


text:
인수인계를 위한 위키 작성

요약
다음 개발할 사람들을 위한 문서 준비를 지금부터 천천히 하면 좋을 것 같아요.
일단은 위키에 작성할 내용들을 항목화해서 작성했는데, 서영이도 같이 추가해 주면 좋을 듯. 링크는 밑에 댓글에 첨부할게

Wiki 여기 읽어보고 나중에 추가하고 싶은거 있으면 지금 보고 있는 이슈에 댓글로 계속 추가해줘!
@leeseooo


text:
Use parent class type members' variance in glb

Motivation

This allows the result.rb test to typecheck, and fixes one of our List
tests.
Explanation
The intuition is that the result ret of Types::all(gs, t1, t2) must be a
subtype of both t1 and t2 (this is ENFORCE'd in the code).
Consider
T.all(Result::Ok[T.untyped], Result[Integer, TypeError])

Intuitively, we would like this to be Result::Ok[Integer]. This intuition is
confirmed by the fact that it's the variance of the parent's type members that
are used when checking subtyping: since OkType and ErrType are covariant,
subtyping should be allowed, so since T.noreturn <: TypeError holds,
Result::Ok[Integer, T.noreturn] <: Result[Integer, TypeError] holds.
Due to what looks to me like an accident, glb was using the variance of the
child to determine whether it could collapse a type argument to a subtype, which
is now changed.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_M6FFJWD1dCRhsN
→ https://go/builds/bui_M6FFyWRycHUUKR

repo: sorbet/sorbet


text:
prompt pure 1.0.0 requires async

Hi,
sindresorhus/pure was updated to 1.0.0 with the commit https://github.com/sorin-ionescu/prezto/commit/f7ea78078f81d2d6fbe71d73274926a3f756a586. Problem is that there was a breaking change, and pure now depends on two files, not just one. async.zsh is now a dependency.
Any thoughts on how to solve the problem? Would adding the mafredri/zsh-async plugin be a plausible solution?

ln -s modules/prompt/external/pure/async.zsh modules/prompt/functions/async fixes it.
I would rather add zsh-async as an external module since it's useful in other places. It will have to be loaded like all other modules by adding it in zpreztorc since pure does not know to use pmodload async.

Your async is quite a lot of code. If I were to add it as another module, why should I change https://github.com/sorin-ionescu/prezto/blob/master/modules/prompt/functions/prompt_sorin_setup#L62-L92 to use it, my theme would know to pmodload 'async'?
Can you comment on #796's rendering issues and #888's freezing issues? Thank you.

If this can help u, I've solved the problem installing the pure-prompt with npm. But I think the best solution is to add zsh-async as an external module.

Is there a good way of detecting that pure is being used within prezto? If so, I could add that check to pure, and instead of doing autoload -Uz async && async, it would do pmodload 'async'. Does this sound reasonable?
@sorin-ionescu if you were to use it, one benefit of my async library is that it does not rely on files for communication, it all happens within the shell. So no race-conditions should happen and there is nothing that needs to be cleaned up. Other than that it can manage unique jobs (no multiple jobs) and you can tell it to kill of all current jobs if they are no longer relevant. The notifying via WINCH is also optional, you can resort to polling for results if you please.

@mafredri maybe, instead of add that check to pure, we can use a conditional prompt -c inside .zpreztorc to check if the selected theme is pure?

@Stelgard mm, I agree that it would be preferable to keep framework specific stuff out of pure, I guess your idea would work just fine as long as the async module get's initialized before the pure precmd.

A check could be added to modules/prompt/init.zsh. It would have to keep track of all a sync themes in an array that will require manual updating. It's dirty and error prone.

Cheers :beers:!

Woohoo! :tada: Thanks!

I would still like async as an external module though.

You could replace the symlink to prompt_pure_setup with a file, with this contents:
local current_dir
current_dir="$(dirname "${(%):-%x}")"

prompt_pure_setup() {
    pmodload 'async'
    source "$current_dir/../external/pure/pure.zsh"
    prompt_pure_setup "$@"
}

prompt_pure_setup "$@"

Why didn't I think of that?
pmodload 'async'
source "${0:h}/../external/pure/pure.zsh" || return 1

Wouldn't your example get evaluated at run time, even if pure is selected
or not? I wrote mine like I did because I thought it would get initialized
by the command prompt pure. I could be wrong and in that case go ahead
with your terser version :-).
On May 31, 2015 7:25 PM, "Sorin Ionescu" notifications@github.com wrote:

Why didn't I think of that?
pmodload 'async'source "${0:h}/../external/pure/pure.zsh" || return 1
—
Reply to this email directly or view it on GitHub
https://github.com/sorin-ionescu/prezto/issues/892#issuecomment-107217224
.

It should not. The contents of the file is wrapped in an auto-loadable function with the name of the file whose body is loaded on first run. You execute it manually with prompt_pure_setup "$@" because you are redefining it.

authors: Stelgard arthurvr mafredri sorin-ionescu

repo: sorin-ionescu/prezto


text:
[python] Detect availability of virtualenv pyenv plugins as well as pyenv

Just having 'pyenv' available doesn't imply availability of virtualenv pyenv plugins. Check for availability of virtualenv plugins as well before attempting to use pyenv wrapper for virtualenv.
Fixes #1413

@indrajitr the solution worked perfectly! =)
I just have one question. If one have pyenv and pyenv-virtualenv but does not have pyenv-virtualenvwrapper, is there any problem to run pyenv-virtualenv init and then run virtualenvwrapper (not the pyenv one)?
Last night I worked on a different solution (but wasn't able to do the commit and the PR until now, sorry for that). I don't know if it follow zsh style guidelines. Its diff can be found on the following link:

https://github.com/sorin-ionescu/prezto/compare/master...diraol:fix-1413-virtualenv

But, if there is no problem to run pyenv-virtualenv init and then the standard virtualenvwrapper, then you PR is just ready to be merged.

@diraol, adjusted the conditions with your feedback. Does this work for you?

authors: diraol indrajitr


text:
Store history in browser storage

I would like to be able to store the query history in the History tab in browser storage instead of in the server memory. This would make it per-user and persist after restarting pgweb.

If you're concerned about history leaking across users, you can run pgweb in multi-session mode with --sessions flag.

Oh nice, I'll do that. It'd still be nice to save in browser history so it persists across restarts though.

Yea this kind of request has been on the radar for a while, but i dont have any ETA for when its going to be available.

Yeah, I understand. Also thanks for pgweb! It's exactly what I was looking for 😀

Oh, it looks like setting PGWEB_SESSIONS=1 is for multiple database connections, so it ignores the --url option...

repo: sosedoff/pgweb


text:
AWS Amplify api: The data couldn’t be read because it is missing.

Describe the bug
Tried to use a simple code
import Foundation
import SotoAmplify

class AWSAmplifyClient {
    var logger = Logger(label: "foo")

    let awsClient: AWSClient
    let amplifyClient: Amplify

    init() {
        logger.logLevel = .trace
        awsClient = AWSClient(
            credentialProvider: .static(accessKeyId: "XXX", secretAccessKey: "XXX"),
            httpClientProvider: .createNew
        )

        amplifyClient = Amplify(client: awsClient, region: .uswest2)
    }

    func getApps() {
        do {
            let result =  try amplifyClient.listApps(Amplify.ListAppsRequest(), logger: logger).wait()
            for app in result.apps {
                print(app.appId)
            }
        } catch  {
            print("error \(error.localizedDescription)")
        }
    }
}

Getting error
error The data couldn’t be read because it is missing.

The trace from log is not really helpful
2021-02-13T21:01:35-0700 info foo : aws-request-id=0 aws-service=amplify aws-operation=ListApps AWS Request
2021-02-13T21:01:35-0700 trace foo : ahc-request-id=0 ahc-el-preference=delegate(on: NIOTransportServices.NIOTSEventLoop) aws-operation=ListApps ahc-eventloop=NIOTransportServices.NIOTSEventLoop aws-service=amplify aws-request-id=0 selected EventLoop for task given the preference
2021-02-13T21:01:35-0700 trace foo : ahc-request-id=0 aws-operation=ListApps aws-service=amplify aws-request-id=0 opening fresh connection (no connections to reuse available)
2021-02-13T21:01:35-0700 trace foo : ahc-request-id=0 aws-operation=ListApps ahc-connection=NIOTransportServices.NIOTSConnectionChannel aws-service=amplify aws-request-id=0 successfully created connection
2021-02-13T21:01:35-0700 debug foo : ahc-request=GET https://amplify.us-west-2.amazonaws.com/apps aws-operation=ListApps aws-service=amplify ahc-channel-el=NIOTransportServices.NIOTSEventLoop ahc-connection=NIOTransportServices.NIOTSConnectionChannel ahc-task-el=NIOTransportServices.NIOTSEventLoop ahc-request-id=0 aws-request-id=0 got connection for request
2021-02-13T21:01:35-0700 debug foo : ahc-request-id=0 aws-operation=ListApps ahc-closing=false aws-service=amplify aws-request-id=0 releasing connection, request complete
2021-02-13T21:01:35-0700 trace foo : ahc-request-id=0 aws-operation=ListApps ahc-connection=NIOTransportServices.NIOTSConnectionChannel aws-service=amplify aws-request-id=0 parking connection
2021-02-13T21:01:35-0700 error foo : aws-request-id=0 aws-error-message=valueNotFound(Swift.String, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "apps", intValue: nil), _DictionaryKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "description", intValue: nil)], debugDescription: "Expected String value but found null instead.", underlyingError: nil)) aws-operation=ListApps aws-service=amplify AWSClient error
error The data couldn’t be read because it is missing.

Setup (please complete the following information):

OS: macos 11.2.1
Version of soto: 5.2
Authentication mechanism: hard-coded credentials

Additional context
Add any other context about the problem here. If this a bug related to a command not working can you run the same command on a client initialised with the logging middleware. eg S3(region: .useast1, middlewares:[AWSLoggingMiddleware()])

I ran your code and didn't have any issues.
You are getting the error because AWS is returning an unexpected response. It expects there to be an apps parameter in the returned json. Can you run your code with the LoggingMiddleware? Change
amplifyClient = Amplify(client: awsClient, region: .uswest2)

to
amplifyClient = Amplify(client: awsClient, region: .uswest2).with(middlewares: [AWSLoggingMiddleware()])

Also do you have any Amplify apps setup in your account?

With the AWSLoggingMiddleware I can see that the JSON is returned by AWS. I can see both of my apps in there.
I think I know why I am getting this error, it is because both of my apps have
"description" : null,

And in Soto package it is required
        ///  The description for the Amplify app.
        public let description: String

I actually created both of my apps via Web Console, and don't even see ability to add a description.
And now the error message makes sense
Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "apps", intValue: nil), _DictionaryKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "description", intValue: nil)], debugDescription: "Expected String value but found null instead.", underlyingError: nil))

Which is telling the codingPath apps->[0]->description raise the error "Expected String value but found null instead."
And that is crazy, because I see description is required in botocore https://github.com/boto/botocore/blob/develop/botocore/data/amplify/2017-07-25/service-2.json#L642
And it is required in the API definition https://docs.aws.amazon.com/amplify/latest/APIReference/API_App.html
description
The description for the Amplify app.
Type: String
Length Constraints: Maximum length of 1000.
Pattern: (?s).*
Required: Yes

But again, there is no way to add a description of the app in the AWS Console.
Not sure if you autogenerate code from the definition of the APIs, but seems like definitions can lie... Btw, aws-cli works for me no problem.

Soto uses the same json model files to auto-generate the swift code that all the other SDKs use. So yeah the service being required in boto will be reflected in Soto. I have a patching process for the models which is applied at code generation so I can remove the description from the required list.
The models are not always correct and unfortunately with over 200 services, I can't find all of them. I'll fixup this one.

#475

authors: adam-fowler outcoldman

repo: soto-project/soto


text:
[FEAT]: Preview doc deployment

Description
Currently, all of the doc improvements are made in the dev branch. But this is hard for people to contribute to various parts of the documentation together.
Let's use this Github Action to preview Github page deployment.
Additional Information
No response

oh I like this, could we do a similar thing for our sotopia website?

sotopia website is handled by vercel? If we use a similar way to the docs site, we should be able to use this for that as well.

Yeah, I am going to move it to github pages

Sadly, after some digging, I found that the action above doesn't support actions/deploy-page (deploy from github action).
And the preview feature of actions/deploy-page is still in alpha: https://github.com/actions/deploy-pages/issues/337.

authors: ProKil XuhuiZhou

repo: sotopia-lab/sotopia


text:
Move pre-commit hook to pre-push

You must delete the file ./.git/hooks/pre-commit that was previously generated by the package pre-commit.
Fixes #70
Features

Move the pre-commit hook to pre-push

Used package git_hooks instead of pre_commit

Fix a test that would fail if IVLE_KEY in .env was non-empty

By using regex in the custom cassette

Pull Request Test Coverage Report for Build 512

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 96.845%

Totals

Change from base Build 507:
0.0%

Covered Lines:
307

Relevant Lines:
317

💛  - Coveralls

Btw what elixir/mix version are you running? I'm getting a different mix.lock here using Elixir/Mix 1.6.5 OTP 20.
0 11:40:23 setiajij@MacBook-Pro-38:~/cadet
518  (pre-push2)$ elixir --version
Erlang/OTP 20 [erts-9.3.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.6.5 (compiled with OTP 20)
0 11:41:06 setiajij@MacBook-Pro-38:~/cadet
519  (pre-push2)$ mix --version
Erlang/OTP 20 [erts-9.3.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Mix 1.6.5 (compiled with OTP 20)

diff --git a/mix.lock b/mix.lock
index 7dbb4ca..d7f9fc3 100644
--- a/mix.lock
+++ b/mix.lock
@@ -27,9 +27,9 @@
   "git_hooks": {:hex, :git_hooks, "0.2.0", "3e437954b8dd8d63c723c25b6ae412766ad957a628d2c0aa3fd58cdf941c66c9", [:mix], [{:blankable, "~> 0.0.1", [hex: :blankable, repo: "hexpm", optional: false]}, {:recase, "~> 0.2", [hex: :recase, repo: "hexpm", optional: false]}], "hexpm"},
   "guardian": {:hex, :guardian, "1.1.0", "36c1ea356a1bac02bc120c3f91f4f0259c5aa0ee92cee0efe8def5d7401f1921", [:mix], [{:jose, "~> 1.8", [hex: :jose, repo: "hexpm", optional: false]}, {:phoenix, "~> 1.0 or ~> 1.2 or ~> 1.3", [hex: :phoenix, repo: "hexpm", optional: true]}, {:plug, "~> 1.3.3 or ~> 1.4", [hex: :plug, repo: "hexpm", optional: true]}, {:poison, "~> 2.2 or ~> 3.0", [hex: :poison, repo: "hexpm", optional: false]}, {:uuid, ">= 1.1.1", [hex: :uuid, repo: "hexpm", optional: false]}], "hexpm"},
   "guardian_db": {:hex, :guardian_db, "1.1.0", "45ab94206cce38f7443dc27de6dc52966ccbdeff65ca1b1f11a6d8f3daceb556", [:mix], [{:ecto, "~> 2.2", [hex: :ecto, repo: "hexpm", optional: false]}, {:guardian, "~> 1.0", [hex: :guardian, repo: "hexpm", optional: false]}, {:postgrex, "~> 0.13", [hex: :postgrex, repo: "hexpm", optional: true]}], "hexpm"},
-  "hackney": {:hex, :hackney, "1.13.0", "24edc8cd2b28e1c652593833862435c80661834f6c9344e84b6a2255e7aeef03", [], [{:certifi, "2.3.1", [hex: :certifi, repo: "hexpm", optional: false]}, {:idna, "5.1.2", [hex: :idna, repo: "hexpm", optional: false]}, {:metrics, "1.0.1", [hex: :metrics, repo: "hexpm", optional: false]}, {:mimerl, "1.0.2", [hex: :mimerl, repo: "hexpm", optional: false]}, {:ssl_verify_fun, "1.1.1", [hex: :ssl_verify_fun, repo: "hexpm", optional: false]}], "hexpm"},
+  "hackney": {:hex, :hackney, "1.13.0", "24edc8cd2b28e1c652593833862435c80661834f6c9344e84b6a2255e7aeef03", [:rebar3], [{:certifi, "2.3.1", [hex: :certifi, repo: "hexpm", optional: false]}, {:idna, "5.1.2", [hex: :idna, repo: "hexpm", optional: false]}, {:metrics, "1.0.1", [hex: :metrics, repo: "hexpm", optional: false]}, {:mimerl, "1.0.2", [hex: :mimerl, repo: "hexpm", optional: false]}, {:ssl_verify_fun, "1.1.1", [hex: :ssl_verify_fun, repo: "hexpm", optional: false]}], "hexpm"},
   "httpoison": {:hex, :httpoison, "1.2.0", "2702ed3da5fd7a8130fc34b11965c8cfa21ade2f232c00b42d96d4967c39a3a3", [:mix], [{:hackney, "~> 1.8", [hex: :hackney, repo: "hexpm", optional: false]}], "hexpm"},
-  "idna": {:hex, :idna, "5.1.2", "e21cb58a09f0228a9e0b95eaa1217f1bcfc31a1aaa6e1fdf2f53a33f7dbd9494", [], [{:unicode_util_compat, "0.3.1", [hex: :unicode_util_compat, repo: "hexpm", optional: false]}], "hexpm"},
+  "idna": {:hex, :idna, "5.1.2", "e21cb58a09f0228a9e0b95eaa1217f1bcfc31a1aaa6e1fdf2f53a33f7dbd9494", [:rebar3], [{:unicode_util_compat, "0.3.1", [hex: :unicode_util_compat, repo: "hexpm", optional: false]}], "hexpm"},
   "jason": {:hex, :jason, "1.0.0", "0f7cfa9bdb23fed721ec05419bcee2b2c21a77e926bce0deda029b5adc716fe2", [:mix], [{:decimal, "~> 1.0", [hex: :decimal, repo: "hexpm", optional: true]}], "hexpm"},
   "jose": {:hex, :jose, "1.8.4", "7946d1e5c03a76ac9ef42a6e6a20001d35987afd68c2107bcd8f01a84e75aa73", [:mix, :rebar3], [{:base64url, "~> 0.0.1", [hex: :base64url, repo: "hexpm", optional: false]}], "hexpm"},
   "jsx": {:hex, :jsx, "2.8.3", "a05252d381885240744d955fbe3cf810504eb2567164824e19303ea59eef62cf", [:mix, :rebar3], [], "hexpm"},

ning:~/github/cadet $ elixir --version
Erlang/OTP 19 [erts-8.2.1] [source] [64-bit] [smp:4:4] [async-threads:10] [kernel-poll:false]

Elixir 1.6.6 (compiled with OTP 19)
ning:~/github/cadet $ mix --version
Erlang/OTP 19 [erts-8.2.1] [source] [64-bit] [smp:4:4] [async-threads:10] [kernel-poll:false]

Mix 1.6.6 (compiled with OTP 19)

@indocomsoft Does d271eb1 fix the inconsistency with the lock file?

W.r.t. to the README, I don't think we should add the instructions in. It wouldn't be relevant in a few days time, anyways. This sounds more like a 'send-it-in-slack' kind of deal.

Yup, d271eb1 fixes the inconsistency

LGTM

authors: coveralls indocomsoft ningyuansg

repo: source-academy/cadet


text:
Game: Save game state for staff and admin

Currently the game data is saved only for students, not for staff or admin.
This should be changed so that staff and admin have the same game experience, keep up-to-date on the game development and spot issues.

The relevant code snippet is here - I am wondering if this was an oversight during development (and hence can be resolved by simply removing this check), or if this feature was specifically limited to students for a reason.
Currently, the game_states JSON object (the save file for the game, essentially) is stored under the course, so there shouldn't be any conflicts between save states for staff / admin users. We can investigate this further to see if there are any potential conflicts.

Embedding the snippet here for easy reference:
https://github.com/source-academy/frontend/blob/f1d3cba0a13c7459106a1f2801437c94c68f3d4a/src/features/game/save/GameSaveRequests.ts#L15-L17

...or if this feature was specifically limited to students for a reason.

Looking at the code, I don't think this is the case, at least not anymore. It should be safe to just remove this check – in the unlikely worst case, there might be some unknown bug with staff/admin (which we would not expect to play the game much anyway).

The system is now quite gracefully degrading on this example. Here is the link:
https://share.sourceacademy.org/htl4m
Of course with rediculously large settings, Source Academy brings the browser down to its knees.

repo: source-academy/frontend


text:
change basepath in bpmn-service

Describe the bug
change basePath in bpmn-service from '/workflow' to '/workflows'

@AnkurBansalSF


text:
Hope privode Keyboard Shortcuts for Actions，e.g. Commit ( Ctrl + Enter )

Hope privode Keyboard Shortcuts for Actions，e.g. Commit ( Ctrl + Enter )

Two hotkeys have been added:

For some reasons, the others are not in the plan.

It is difficult to find a suitable key combination that does not conflict with the existing shortcut keys of each platform (Windows/macOS/Linux)
Most of these features require the user to determine some parameters to run, while the entry of these features in UI is easy to find and interact with.

repo: sourcegit-scm/sourcegit


text:
bug:

Type: Bug
Extension Information

Cody Version: 1.14.0
VS Code Version: 1.88.1
Extension Host: desktop

Steps to Reproduce

Expected Behaviour
Logs
Extension version: 1.14.0
VS Code version: Code 1.88.1 (Universal) (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:42:52.765Z)
OS version: Darwin arm64 22.6.0
Modes:
System Info

Item
Value

CPUs
Apple M2 (8 x 24)

GPU Status
2d_canvas: enabled

canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled|
|Load (avg)|3, 3, 2|
|Memory (System)|8.00GB (0.03GB free)|
|Process Argv|. --crash-reporter-id 2af6736a-e33e-4ecb-96ed-483bd52a7378|
|Screen Reader|no|
|VM|0%|
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r6:30993542
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
showvideoc:31016891
dsvsc021:30996838
945dj816:31013170
pythoncenvpt:31022790

It's unclear what the problem is here. @chandrabuwana if you can add details, please reopen this issue and I'll take a look.

authors: chandrabuwana dominiccooney

repo: sourcegraph/cody


text:
[Chat]: Allow specifiying primary response language for Cody Chat

It seems like that by default Cody Chat seems to detect the display language of the system (or Visual Studio Code perhaps?) and response in that language (in my case it's zh_CN), but sometimes I may want to have Cody Chat defaults to using for example English for its response disregarding any display language sort of thing.
### Tasks

Hi @shanoaice. Thanks for bringing this to our attention. We have seen this issue with other languages (German).
@abeatrix do you want me to put together a list of other similar issues?

authors: jdorfman shanoaice