Input & Textarea crash on React Native

Current Behavior
As soon as I try to use a  (simple as that) the app crashes entirely with the following error:
Invariant Violation: [1189,"AndroidTextInput",11,{"allowFontScaling":true,".....
...ge":true,"text":""}] is not usable as a native method argument
This error is located at:
in AndroidTextInput (created by InternalTextInput)
in InternalTextInput (created by TextInput)
Expected Behavior
I just want to be able to use Input and textarea, simple
Tamagui Version
1.43.12 (latest)

Reproduction
the codesandbox link provided above crashes on the website

System Info
using latest RN version (0.72.3)

I think your issue is that your imports are incorrect?
You should be using the Input component, not the TextInput (which is a react-native out of the box) if im not mistaken

Thank you for the feedback, but no: I was using  and  as expected
I rolled back version until there is a fix for that.
In case that helps, I am using this tamagui.config file:
import { config } from '@tamagui/config'

import { createFont, createTamagui } from 'tamagui' // or '@tamagui/core'

const Nunito = createFont({
  family: 'Nunito-ExtraBold',
  size: {
    1: 11,
    2: 12,
    3: 13,
    4: 14,
    true: 14,
    5: 16,
    6: 18,
    7: 20,
    8: 23,
    9: 30,
    10: 46,
    11: 55,
    12: 62,
    13: 72,
    14: 92,
    15: 114,
    16: 134
  },
  weight: {
    100: 100,
    200: 200,
    300: 300,
    400: 400,
    true: 900,
    500: 500,
    600: 600,
    700: 700,
    800: 800,
    900: 900
  },
});

const NunitoSemi = createFont({
  family: 'Nunito-SemiBold',
  size: {
    1: 11,
    2: 12,
    3: 13,
    4: 14,
    true: 14,
    5: 16,
    6: 18,
    7: 20,
    8: 23,
    9: 30,
    10: 46,
    11: 55,
    12: 62,
    13: 72,
    14: 92,
    15: 114,
    16: 134
  },
  weight: {
    100: 100,
    200: 200,
    300: 300,
    400: 400,
    true: 900,
    500: 500,
    600: 600,
    700: 700,
    800: 800,
    900: 900
  },
});

const appConfig = createTamagui({
  ...config,
  fonts: {
    heading: Nunito, // overrides the default heading font
    body: NunitoSemi, // overrides the default body font
    nunito: Nunito // introduce a specific token for your new font
  },
})
export type AppConfig = typeof appConfig

declare module 'tamagui' {
  interface TamaguiCustomConfig extends AppConfig {}
}

export default appConfig

@pierro Can you share a snippet of how you're using it?

Just plain  and plain  from tamagui, nothing else, they just crash the app.

I had this happened when I created my own text input using RN text input. And it seems to relate to when I set fontFamily "$body" to it when i uses styled with it. When i removed it, the crash doesn't occur.

you may need this before you use your input, its how tamagui knows which components to treat as react native ones:

we did this so we could support tree shaking, its a bit confusing. if you import tamagui it does this for you automatically though so i doubt this is it, but just noting


Feature Request

Hello,
This library looks perfect.  I was looking for a library that basically works like the groovy Markup builder.
Is there any chance you would be willing to add export/import support so that it can be used like a normal package for Angular or other frameworks instead of requiring

Hi!
Sorry for the slow response time on my end.
This should be possible. I would have to make sure it is done in the expected way. If possible, could you provide a boilerplate project with a setup showing how you wish the package could be imported (Eg. in the "best practice" way for your use case), so that I can investigate if it's doable the way you suggest?

I will try to get you something this week.

Hi @Protocol-X : just following up. Were you able to make something?


kvm: solve certain routing issues by using the same default bridge as CNI

When the kvm stage1 and the coreos stage1 are used on the same machine with a
flannel CNI configuration (and likely other configurations) without a specified
bridge name, different bridges will be constructed by each stage1 for the same
subnet -- cni0 and kvm-cni0 -- causing traffic intended for the
later-constructed bridge to be lost, as it is routed to the earlier-constructed
bridge.
The normal workaround is to specify a bridge name in the CNI configuration, but
this fix avoids the issue altogether by making sure that cni0 is used in all
cases.
I can't find any records of a specific motivation for using kvm-cni0 instead of cni0, so it's possible that I'm missing the original reason behind it, but it seems like an arbitrarily-made decision from the original development of CNI support in the kvm stage1.

/cc @squeed

LGTM!


Update CNCF Community Code of Conduct v1.3

The current upstream CNCF Code of Conduct has been updated to version 1.3.
Therefore, in this pull request, we have incorporated the updates based on CNCF Community Code of Conduct v1.3.
Related PR: https://github.com/kubernetes/website/pull/42398

/assign @sftim @divya-mohan0209
I cordially extend an invitation for your esteemed presence to undertake a comprehensive review of the updated CNCF Community Code of Conduct v1.3 (COC) documentation for 'kubernetes/contributor-site'.

/hold
Thanks for noticing the changes, @ydFu !
The Kubernetes Code of Conduct Committee needs to sign off on this.
Tag: @kubernetes/code-of-conduct-committee @detiber @endocrimes @hlipsig @jeremyrickard @salaxander

This really isn't the right place to have the discussion on this.=/
K/community is our source of truth and it points to the CNCF CoC. It's been hosted hom the site as a convenience.  There was a long comment period open to the community at large to discuss their proposed changes with multiple announcements being sent to call for comments.

Instead of keeping a copy in the contributor-site and needing to update it once in a while, I think we should point to the source of truth.

Please bear in mind that we also have https://kubernetes.io/community/code-of-conduct/


0.9.999993 breaks

It looks like the latest GUN version breaks with this setup. Let's fix that

The issue I was experiencing in a different project luckily wasn't due to any of the libraries this project uses.


Replace pexpect with subprocess

my platform: macOS (Intel)
When I was running zamm and approving a terminal process, it stuck for several seconds then raised
│ /Users/markyfsun/.conda/envs/auto_weekly/lib/python3.10/site-packages/langchain_contrib/tools/te │
│ rminal/terminal.py:84 in _get_raw_shell_update_uncached                                          │
│                                                                                │
│    81 │   │   │   │   results += latest_output                                                   │
│    82 │   │   │   │   time.sleep(0.1)                                                            │
│    83 │   │   except pexpect.TIMEOUT as e:                                                       │
│ ❱  84 │   │   │   raise UnknownResult(                                                           │
│    85 │   │   │   │   "Terminal output does not have initial prompt of: "                        │
│    86 │   │   │   │   f"'{self.bash_prompt}':\n\n{results}"                                      │
│    87 │   │   │   ) from e                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
UnknownResult: Terminal output does not have initial prompt of: '
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
[1m[?1034hzamm$ ':

python3 hello.py
Hello world
Bye
zamm$

I assume that pexpect here expects $ as the start flag and the EOF flag, however my terminal wrote something else to the output, so the match could not be found.
I wonder if you can use subprocess.getoutput here to execute bash command, since you only need to get the output of the command?

I found another way to fix this: drop the output after spawning, enter an empty input, then use the output as bash_prompt. This could avoid noise from the initialization of bash.

Ooof, I am so sorry, I just saw this! It seems my Github notifications still aren't working right yet :(
I made some changes to get the fix to work on WSL Ubuntu. Can you check to see if it still works on the Mac?
Regarding using subprocess, it didn't seem like I could maintain shell state unless I started a shell as a subprocess, at which point doing a non-blocking read seems convoluted. I went with pexpect for that reason.


code displays strange behavior with line-wrapped text

Line wrapping in code causes indent guides to look incorrect and causes lines to be cut off.
#code(
  indent-guides: 1pt + black
)[
  ```py
  def floyd_warshall(G):
    # let G be an adjacency matrix
    dist = G

    for k in range(len(G)):
      for i in range(len(G)):
        for j in range(len(G)):
          if dist[i][j] > dist[i][k] + dist[k][j]:
            dist[i][j] = dist[i][k] + dist[k][j]
            blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah

    return dist
  ```
]

This issue occurs because there is no simple way to tell if content is line wrapped (calls to measure assume infinite available width). This issue could be resolved if Typst's layout function is updated to return the actual size of a table cell.
This issue could also be resolved if tables supported arbitrary cell borders, because then I wouldn't have to deal with measure to draw indent guides of the correct length. There is an experimental branch that uses tablex to achieve this: https://github.com/platformer/typst-algorithms/tree/tablex. However, there are various bugs that prevent this branch from being merged. I'll revisit this issue once tablex hits v0.1.0.

I was able to adapt the solution in the tablex branch to the existing code used on main. Fixed as of 5bc82eb4299b8360c29e602ad229f5ebbaf4bf78.


cri: write generated CNI config atomically

The 10-containerd-net.conflist file generated from the conf_template should be written atomically so that partial writes are not visible to CNI plugins. This is accomplished by writing a temporary file, syncing, and renaming over the destination file name.
Partial/inconsistent writes can occur due to:

A CNI plugin attempting to read the file while containerd is writing it (both in the case of a newly-generated file or in the case of a re-generated file via a subsequent call to UpdateRuntimeConfig).
Concurrent calls to UpdateRuntimeConfig leading to multiple active writers of the same file

The above mechanism explicitly protects against (1) as all writes are to a file with a temporary name.
There is no explicit protection against multiple, concurrent CRI calls to UpdateRuntimeConfig. However, atomically writing the generated file should mean only one writer will "win" and a consistent file will be visible.
Fixes https://github.com/containerd/containerd/issues/8607

Switching to draft; this will need to be conditioned off for Windows.

Truly impeccable timing from myself 🤣. Whenever this is un-drafted I'll take a peek again

@dcantah Comments are appreciated and useful too :smile:

Believe atomicity can be achieved on windows with a little wrapper around MoveFileEx (in place of os.Rename). You need the MOVEFILE_REPLACE_EXISTING|MOVEFILE_WRITE_THROUGH flags, which unfortunately os.Rename only provides the first of the two.

Mmm, my university wisdom might be misguided now (or perhaps always was LOL). This was a pretty common tactic in many "write files atomically" libraries, and even stdlibs:

https://github.com/untitaker/python-atomicwrites/blob/master/atomicwrites/__init__.py#L70-L79
https://github.com/untitaker/rust-atomicwrites/blob/master/src/lib.rs#L303-L313
https://github.com/natefinch/atomic/blob/master/file_windows.go#L29
https://bugs.python.org/msg146307

This area seems completely fraught with peril though. There's no clear picture or guarantee on docs of atomicity, but a recommended approach as recent as 2021 on an article from msft recommends  ReplaceFile now for files with "document-like" data. ReplaceFile at least has the advantage that it preserves the following as well:

Creation time
Short file name
Object identifier
DACLs
Security resource attributes
Encryption
Compression
Named streams not already in the replacement file

This is much deeper than my drive-by comment at 12 AM led on 🤣

I've refactored this a bit to encapsulate the rename-file logic out into its own package and keep the CRI code a bit cleaner.

Mmm, my university wisdom might be misguided now (or perhaps always was LOL).

My curriculum didn't cover Windows, so this is all a bit unfamiliar to me :rofl:
@dcantah, I didn't attempt to write a Windows codepath yet.  Do you think we should:

Use MoveFileEx with MOVEFILE_REPLACE_EXISTING|MOVEFILE_WRITE_THROUGH
Use RenameFile (not sure with which flags)
Punt for now and leave Windows as-is (we're at least not making it worse while we do end up improving Linux)

At the very least lets add a TODO to consistentfile's Windows impl to find the right approach

Done

MoveFileEx with MOVEFILE_REPLACE_EXISTING|MOVEFILE_WRITE_THROUGH is not guaranteed to be atomic on Windows. In particular, it has to first delete the existing file, which means the file contents on disk have to be deallocated (per my understanding). So for instance, if the machine crashes in the middle of this operation, you can have a partially-deallocated file.
The filesystem doesn't provide any way to guarantee atomicity for this kind of thing. I think the best you can do is something like MoveFileEx or ReplaceFile.

maybe we can align with https://github.com/containerd/continuity/blob/25762ef7c27a37645197ed6d1d708e55a230e35d/ioutils.go#L28 ?

maybe we can align with https://github.com/containerd/continuity/blob/25762ef7c27a37645197ed6d1d708e55a230e35d/ioutils.go#L28 ?

I hadn't seen that one either, but I was trying to avoid an interface with data []byte.  The io.ReadWriteCloser model here allows something like template.Execute to still work (since it accepts an io.Writer) without needing an additional in-memory buffer.  template.ParseFiles does already read the whole thing into a buffer, but other use-cases with large files might not, and the consistentfile/atomicfile package allows that pattern to work.  (Reading a large user-supplied file into memory could cause containerd to OOM.)

but other use-cases with large files might not, and the consistentfile/atomicfile package allows that pattern to work. (Reading a large user-supplied file into memory could cause containerd to OOM.)

Thanks for the comment. SGTM.

As part of replacing WritePidFile and WriteAddress I ported their (somewhat) platform-independent behavior to atomicfile.  atomicfile now does the same rename workflow on Windows and reorders the underlying file close ahead of the rename to avoid the restriction that Windows has on renaming open files.  If there's consensus on either MoveFileEx or RenameFile instead of Go's os.Rename (which does call MoveFileEx but not with the same flags), I'm happy to switch to that.


Example is not build!

Hi, I just downloaded the example file but couldn't build & run it.
here are the Xcode the errors:

Have you tried running pod install as the error suggests?

Yea you are right! It just needed a pod update!
Thank You.


vites js compatibility

Hi,
Did anyone try to run ts-arch within a vite js project?
I just tried to copy the test from the README file and setting test timeout globally to 60000 (https://vitest.dev/config/#testtimeout) but I get error "TypeError: message is not a function".

Hi,
I didn't try, yet. Would you mind creating a (more or less) minimal repo to reproduce the error?

Hi,
I tried again lately and it appears to work.
I created a template project anyway at https://github.com/jeje42/ts-arch-vitest, in case this might be useful to anyone.


Serialization fixes

Serialization fix for custom result types
Fix so that only types that are known to be serializable
are returned as their native type for result serialization.
Types that inherit from these primitive types (e.g. int)
may not necessarily also be serializable, so replace an
isintance() check with an explicit equality check of type().
Check if Task is being scheduled from the main module
Tasks shouldn't be scheduled to ProcessPools from the special
main module. main will be a different module for Process
workers (the child.py module to be exact) and so target from the
original main will not be found - or worse will be replaced
by an attribute from child.py.

Hmm there is some issue with the tests I need to look into before this can be merged.

This is superseded by #139


Fixes #75: Adapter for Firebase Remote Config

This is based on #59, which needs to be merged first.

Created #79 to track JWT decoding and will hold merging until this is closed.

This is now based on https://github.com/tweaselORG/TrackHAR/pull/87, which needs to be merged first.

The problem this still has is that there is one app that sometimes (but not always) sends an appInstanceIdToken that is not a JWT: eCKZbsz5Sde-1eY2P48xBZ:APA91bExD9TtElNISzzjwPLvFRAypKO89dpkU4SGHI4dZpu0thydzo7QqrVnE3gXg6qrb8nCay2F45__K2oL-PHTqy-VeN20yUdbDE7Eym5oFyyPqh_mykAyrnV4Y8eXl713Bg2GMK3r
This touches on a question that I have been toeing around for a while. Currently, we don't guard against exceptions in decode functions:
https://github.com/tweaselORG/TrackHAR/blob/9287bf182bf18badb8ac93f0e300eec0b4f011c1/src/index.ts#L258
But I am really not sure whether that is "correct". For one, this a problem from the perspective of writing the adapters (as in this case) because we don't have any mechanism to work around this from an adapter. But, and more importantly, I also don't think that this is the correct behaviour semantically. I do think that "try to parse this value as x and ignore it otherwise" makes more sense for the decode functions. This more eager way of writing/understanding adapters also matches how we handle things in other places. Notably, we already gracefully handle empty values without the adapter having to concern itself with them:
https://github.com/tweaselORG/TrackHAR/blob/9287bf182bf18badb8ac93f0e300eec0b4f011c1/src/index.ts#L249

Implemented. The commit history should now be kept when merging.

The last force push broke the ID grouping changes: 183a5a0cd9b33ac18a465b6046573e4c06ed959b..71769496afc63164b7398852f7dc746b083abefd#diff-6e40c2e22bL1632
I'm currently working on various Google adapters for web anyway, so I'll fix this through that PR.


Fix Pass through user-defined properties

bp: #35515
Previously, irrelevant properties passed by users when using TVF were directly ignored by Doris.
Now, we retain and pass these additional user-defined properties to the S3 SDK.

run buildall

run p0


seeking new maintainer/owner of this module

I don't have the bandwidth to maintain this module at all. Would someone like to take over maintenance or ownership of it? I'm happy to transfer it.
I would give maintainer access of https://pypi.org/project/which/ (and eventually "owner" access) and collaborator access to this GitHub repo (eventually we could move it to another GitHub owner/org account if that helps).  I'd just request that (a) it stay open source under MIT or Apache or MPL or similar licenses and (b) new releases start with a major version bump so those using the module (if any) have a better chance to notice the transfer.

I can't promise I'd be a super maintainer either (I don't normally use the module, just ran across it in Firefox's build script), but if you give me pypi & github access (I'm @moy on both sites), I can at least try to fix the pip install issue.

My mistake, https://pypi.org/project/which/ is owned/maintained by @srid. We used to work together and I recall a long while back he asked me permission to publish it to PyPI. We'll need to get @srid to provide maintainer access to the pypi project if he would like.
@srid, How are you doing? Would you be willing to add me (pypi username trentm) as a maintainer or admin on https://pypi.org/project/which/ and pypi username moy as a maintainer on it as well? Thanks.

Hey. It no longer have access to my PyPI account. Password reset does not work perhaps because that account it still using an old (now-deleted) email address. If any of you want to reach out to PyPI admins I'd be happy to help with any verification proof.

Given the permissions problems, what about blessing a Python 3 only which-ng and redirecting new users there? So long as it maintains the same license, etc., would that be a reasonable solution?


MAVSDK on Jetson Nano

Hi everyone,
I am currently trying to install mavsdk on Jetson Nano, i had some problems so this is how I fixed them.
The system is:

Jetpack 4.6
Ubuntu 18.04 LTS
Python 3.6.9

Because of other libraries (vpi, jetson-utils etc.) it is not possible to update python, so i am stuck with v3.6.9.
My first error was with pip, it didn't install the mavsdk because of a dependency

I kinda got around this problem with pip3 install protobuf==3.19.6 mavsdk this command, and now it can import mavsdk in python
Now the problem is the mavsdk-server,
I connected the Pixhawk Cube - Jetson Nano via UART, and connections are ok but there is no mavsdk-server on the Jetson.
When I run the python examples:

How can i install mavsdk-server on Jetson Nano ? Is it possible to just build it without mavsdk itself, (I am not familiar with ubuntu os)
Any help would be appreciated.

How can i install mavsdk-server on Jetson Nano ?

The Jetson Nano is arm64, isn't it? In that case you can try to just run mavsdk_server_linux-arm64-musl from the MAVSDK release page.

I am sorry for asking this dumb question but as i stated I am not familiar with ubuntu. I searched about it but couldn't find something about how to run such a file.
Could you please explain further or refer me to a source about how to do that?

I managed to run mavsdk @JonasVautherin, thanks to your response.
But it seems the mavsdk version is 0.12.0, how can I update to the latest version, pip seems to do nothing.
I already have lots of code but 0.12.0 version is not compatible.

What makes you say it's not compatible?

I heavily use offboard mode and PositionGlobalYaw was not in that version it gave import errors but I managed to do some more pip stuff and now it is updated to 1.4.1. Finally I can use it.
Thank you very much for your help.

Oh, did you do pip install -U mavsdk to upgrade it?

It didn't work at first. Turns out it was because of some other modules but I did some cleaning and pip install -U mavsdk did work so yes.


This types for all methods

Just an experiment to see how slow it is.

@typescript-bot perf test this

Would fix #44513 if it worked and weren't too slow.

Yeah. That seems expected.

Check time is 6-7% slower on class-heavy code bases.
It's possible that issuing bogus errors takes that much time — and this PR does issue bogus errors; the code isn't correct. But I doubt it.


Call onRequestPermissionsResult() of super class in AppIntro and AppIntro2

This fixes an issue where requestPermissions() called from a fragment will not deliver the correct result to the fragment.
More information here:
http://stackoverflow.com/a/33995827/2663152
http://stackoverflow.com/questions/10564474/wrong-requestcode-in-onactivityresult#comment13675437_10564488 (Works similarly for this)

I'm not sure why this is necessary...the library has a permission result listener but nothing happens in it on purpose. The UI of the app is not supposed to be locked up if someone chooses not to give an all access to their contacts.

If you request a permission in a fragment (not using the library's inbuilt functionality), for example on a button press, the result is not correctly delivered back to the fragment as the method does not call super.onRequestPermissionResult(). This happens because the activity changes the request code so that it can know which fragment to deliver the result to. (https://android.googlesource.com/platform/frameworks/support/+/refs/heads/master/v4/java/android/support/v4/app/FragmentActivity.java#820). If the super class method is not called, the result is not delivered to the requesting fragment properly.

Ok...but why is this needed if the library has inbuilt permissions support?

In my use case, for example, the app needs to request permission after a button click in one of the slides, and not when the next button is clicked.
Regardless of this, not being able to get the result reliably is a bug, in my opinion.

@NiharG15 alright...thanks for clarifying :) I can see that this PR doesn't affect the inbuilt permissions support, so I guess it's worthwhile. Thank you!
Also, about the getting permission result, it's not a reliability issue. The library is specifically designed to just introduce and request the permissions your app needs...not lock up the UI.


Sets duration of events when :end option is specified.

Fixed by https://github.com/bys-control/activeadmin-index_as_calendar/commit/f1310bcfc766403279df2615e99e59bd6be6111a


Remove delegation backend apps and script from repo

Removing obsolete delegation backend app from repo with accompanying dockers and debian setup

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Unquoted Numerical Default Parameter - TypeError expected string or bytes-like object

I have a parameter in my template that contains a string made up of numbers and dashes as below:
  TagReviewDate:
    Type: String
    Description: The review date - to be used by tags
    Default: 2021-03-25

This causes Taskcat to fail.
·[0;30;41m[ERROR  ]·[0m : TypeError expected string or bytes-like object
Traceback (most recent call last):
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_cli.py", line 70, in main
    cli.run()
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_cli_core.py", line 235, in run
    return getattr(command(), subcommand)(**args)
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_cli_modules/test.py", line 82, in run
    parameters = config.get_rendered_parameters(buckets, regions, templates)
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_config.py", line 355, in get_rendered_parameters
    parameters[test_name][region_name] = ParamGen(
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_template_params.py", line 62, in __init__
    self.transform_parameter()
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_template_params.py", line 96, in transform_parameter
    self._regex_replace_param_value(self.RE_GENNUMB, self._gen_rand_num(20))
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_template_params.py", line 376, in _regex_replace_param_value
    if self.regxfind(regex_pattern, self.param_value):
  File "/root/.pyenv/versions/3.8.1/lib/python3.8/site-packages/taskcat/_common_utils.py", line 87, in regxfind
    security_group = re_object.search(data_line)
TypeError: expected string or bytes-like object

If I add quotes around the default parameter, Taskcat will deploy successfully. e.g.
  TagReviewDate:
    Type: String
    Description: The review date - to be used by tags
    Default: "2021-03-25"

Tascat has been installed using pip3. It is using the latest version and tsted both locally using WSL & in AWS Codebuild. Both profile and no profile has been tested.

Turns out it's a datetime object that's being returned from upstream cfnlint.
# cat t.template.yaml
Parameters:
  TagReviewDate:
    Type: String
    Description: The review date - to be used by tags
    Default: 2021-03-25

>>> import pprint as pp
>>> import cfnlint
>>> t = cfnlint.decode.cfn_yaml.load('t.template.yaml')
>>> pp.pprint(t)
{'Parameters': {'TagReviewDate': {'Default': datetime.date(2021, 3, 25),
                                  'Description': 'The review date - to be used '
                                                 'by tags',
                                  'Type': 'String'}}}

It's easy enough to convert to a string.
>>> p = t['Parameters']['TagReviewDate']['Default']
>>> p
datetime.date(2021, 3, 25)
>>> str(p)
'2021-03-25'
>>>

I think the appropriate path forward here is an upstream fix. A quick conversion to a string on a datetime object is fine. However, IMO, cfnlint shouldn't be returning a datetime object to begin with. The type is defined as a string. We also run into supportability issues when we expand this out to all CFN Parameter types.

My gut is to follow whatever the yaml spec says should be done with interpretation of unquoted strings. However, I would not be opposed to a pr that converts every type not parsed by cfn to a string, which seems to be the underlying behavior in the service


Isolation of user dependencies

Currently, the Python worker implementation depends on the following libraries:
grpcio
grpcio-tools
pytest
requests
mypy
flake8

On start up, workerenv is bootstrapped with the latest version of the above packages.
Problem Statement
If the user attempts to install a different version of one or more of the pre-installed packages, the runtime will get conflicted. For e.g. if the Python worker needs requests == 2.18.4 but the user wants to install requests == 1.6 , pip will only resolve one of the requirements causing either the worker or the function to fail.
Is there a way to isolate the worker dependencies from user defined dependencies?

@elprans @1st1
\cc @christopheranderson @pragnagopa

There is no way to isolate, since the function is executed directly in the worker process.  However, the only actual runtime dependency is grpcio, all the other are development dependencies.  We can pin the grpcio version by appending it to user's requirements.txt (and document this).

Agreed, if grpcio is the only dependency.
Marking this as out of scope for now - let's revisit if the list of runtime dependencies grows in the future.

This is a very old comment, I am not sure if this is even relevant anymore and we havent seen any customer angst around it. Closing this out.


[ci] Disable the Verilator weak straps tests in CI

The sw_strap_value_sim_verilator test appears to be timing out in CI periodically but passes fine locally. We will disable this test for now in CI.

I've opened #16831 to address both comments.


add answers for invalid and not enough info to resolve market

See also #186 of mech https://github.com/valory-xyz/mech/pull/186

Thanks @Adamantios.
Updated and should be good to merge.


Gradle 4.8-rc-1 compat fix - use def when finding the buildType

Goal
Gradle 4.8-rc-1 changes project.android.buildTypes.store to return an Iterable rather than a Set, which can lead to a runtime error within the plugin. This changeset prevents the runtime error by using def instead.
Changeset
Changed
Altered affected types from specific Set implementation to def.
Tests
Mazerunner was run locally after running ./gradlew wrapper --gradle-version 4.8-rc-1 in each of the fixture projects.
Discussion
Alternative Approaches
We could use Iterable instead of def.
Linked issues
#109
Review

For the submitter, initial self-review:

[ ] Commented on code changes inline explain the reasoning behind the approach
[x] Reviewed the test cases added for completeness and possible points for discussion
[x] A changelog entry was added for the goal of this pull request
[x] Check the scope of the changeset - is everything in the diff required for the pull request?
This pull request is ready for:

[x] Initial review of the intended approach, not yet feature complete
[x] Structural review of the classes, functions, and properties modified
[x] Final review

For the pull request reviewer(s), this changeset has been reviewed for:

[ ] Consistency across platforms for structures or concepts added or modified
[ ] Consistency between the changeset and the goal stated above
[ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
[ ] Usage friction - is the proposed change in usage cumbersome or complicated?
[ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
[ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
[ ] Thoroughness of added tests and any missing edge cases
[ ] Idiomatic use of the language

Looks like whatever is wrong with CI is wrong on master also.


Saving a file with errors causes the extension to wipe it

Steps to repro:
1st create a file(x.zig) with a error (no return type):
pub fn x() { }
2nd try to save it
3rd :boom: File is wiped
Additional notes:
changing zig.formattingProvider to zls fixes it
I also set in my workspace
{
"zig.zigVersion": "0.12.0-dev.146+020105d0d",
"zig.zigPath": "/usr/bin/zigd",
"zig.formattingProvider": "zls",
}

Bug with third-party utility.


Cannot find module 'path' 'assert' and 'fs' from @babel

Ask your Question

this error shown after installing jest and react native testing library
below is my webpack.config.js

error on emulator
is there any missing configuration on my webpack.config.js ?

Hi @Ibnunds,
could you please create a reproduction repository with the problem you're having? The information you've provided is not enough to diagnose the issue.

Solved by adding configuration as above in webpack.config.js

While I'm glad you've managed to resolve your issue, i'm curious about one thing - are this runtime errors or Were these errors happening when running tests?

While I'm glad you've managed to resolve your issue, i'm curious about one thing - are this runtime errors or Were these errors happening when running tests?

Its error on runtime, I also don't know why suddenly such an error like that appears after doing jest setup. And i need to npm install path-browserify and assert then added the fallback to webpack.config.js


Replace gold block tps with respawn anchors

Turn them into respawn anchors. Activate the anchor if there is a suitable destination, do a full scan whenever a respawn anchor is broken, placed or a teleport works/fails. Means there still are piston shenanigans etc. to make a anchor display the false state and trick others, but that's fine.

We've already done a few things updating gold bock elevators, may as well let this go.


Check triangleIndices

This is decoded with quantized-mesh-decoder in js:

The triangleIndices looks a little suspect. Especially since there are two zeros in a row.

Could be related to #11 , where the tile is essentially flipped

The tile being flipped was I believe a result of triangle indices being clockwise instead of counter clockwise. That's being tracked in #13.


Move operations for Synapse workspaces

Despite Microsoft.Synapse/workspaces supporting cross-resourcegroup and cross-subscription movement, moving a workspace to another subscription via Azure CLI, fails with the error: {"code":"MoveResourcesFailed","message":"Resource move feature is not enabled"}. Move action also fails with no error message via the Portal.

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

ID: 23df5354-6833-a5da-0eb3-d860150c8b78
Version Independent ID: 682ec206-0fda-3e0b-5841-543860a87e34
Content: Move operation support by resource type - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/move-support-resources.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@real-oneill Thanks for your comment. We will review the issue and get back to you shortly.

@real-oneill Thanks for your feedback. I have made changes to the document and the changes will be live soon.We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


[ENG-3262] Bulk Upload Post-release Improvement - Frontend Piece

Ticket: ENG-3262
Feature flag: n/a
Backend PR: https://github.com/CenterForOpenScience/osf.io/pull/9841

Purpose
This is the frontend piece for bulk upload post-release improvement.
Summary of Changes
TBD
Screenshot(s)
TBD
Side Effects
TBD
QA Notes
TBD

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0007%) to 73.163%

Totals

Change from base Build<PHONE_NUMBER>:
0.0007%

Covered Lines:
5175

Relevant Lines:
6810

💛  - Coveralls


fix(bin): Removing reference to bin file

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"Missing translated storage aware property" with user defined searchable content

PHP Version
8.2
Shopware Version
<IP_ADDRESS>
Expected behaviour
Searchable extended products with translated fields in extension/association and elasticsearch.
Actual behaviour
Missing translated storage aware property extension_field in product_translation

How to reproduce
Given is a product extension with translatable fields such as ‘extension_field’ and ‘name’.
The fields of the association are to be taken into account in the product search, as are category names or manufacturer names.
The above error occurs.
Reason for this:
The actual field type for a TranslatedField is determined in this line:
https://github.com/shopware/elasticsearch/blob/da3fceebc293551aa3a3a08fe12350a513370171/Product/ProductSearchQueryBuilder.php#L71
However, the product definition is always transferred as the ‘EntityDefinition’.
If the field is an association field, the field of the association is searched for in the translation fields of the product.
If it does not exist, the above-mentioned error is thrown.
The search only works because manufacturer.name, category.name and category.description have field names that also appear in the Product entity and are therefore recognised as translatable fields.
In our extension, the ‘name’ field would therefore be taken into account, as the ‘name’ field exists in the product entity. This is a coincidence.
The ‘extension_field’ field would not be found and an error would occur.
EntityDefinitionQueryHelper::getTranslatedField($this->productDefinition, $field)
When using this function, you must therefore consider whether $field is actually a field of an association or the ‘base entity’.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37804.
[created from NEXT-37804, comment 488239]

Good that it's already reported. It can render ES useless in projects with custom entities that contain translated field.


Unicode font issues

Continue to work on improving support for Unicode/CID fonts for TrueType/OpenType. Current code implements everything that is supposedly needed but I get rendering errors on the Welcome test page with the NotoSansJP OpenType font.

Making this high priority for the next stable release since it will likely be important for supporting text filters, banner pages, etc. but not going to hold up the first beta for it.

[master 600fa4c] Fix Unicode font handling (Issue #16)


compaction: consider redundant mvcc.delete rows to trigger Rocksdb compaction

Development Task
Now we have region-compact-min-redundant-rows  to trigger compaction, however it does not consider the following situation:
table A, insert 1000 rows in a transaction, with the first 999 rows being deleted in another transaction,
now for rows 1-999, each row has two mvcc versions, and the mvcc information in rocksdb could be as followings:
row_1_t1=> PUT
row_1_t2=> DELETE
row_2_t1=>PUT
row_2_t2=>DELETE
...
row_999_t1=>PUT
row_999_t2=> DELETE
row_1000_t1=>PUT

with the help of region-compact-min-redundant-rows, the first compact will be trigger, and then it will left 1 version for each row:
row_1_t2=>DELETE
row_2_t2=>DELETE
row_3_t2=>DELETE
...
row_999_t2=>DELETE
row_1000_t1=>PUT

and when we try to select from table limit 1, it will always read the 999 DELETE versions first which is with bad performace. And region-compact-min-redundant-rows does not consider this situation and can not trigger a compaction.  Usually, no data will be inserted between row 1 to row 999, so these old versions will never be cleared.

/report customer


[staging-next] python3Packages.libarcus: fix build against protobuf 3.18+

Still needs upstream resolution (https://github.com/Ultimaker/libArcus/issues/121), but we can grab a Void Linux Vcpkg patch in the meantime

Motivation for this change
For https://github.com/NixOS/nixpkgs/pull/138268
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

cura
curaengine
python38Packages.libarcus
python38Packages.uranium
python39Packages.libarcus
python39Packages.uranium

Removing the return in the error case looks a bit fishy to me, but as long as it works I'm happy.  Did you try cura?

Hmm you're right, that is kind of suspicious. I haven't tried running any dependencies but that seems like a good idea.

@gebner I found a more surgical patch on Vcpkg. Built cura, not sure what to test though.

I'm going to merge this as is; the patch looks good, so if cura builds then let's roll with it.


feat: add keyup eventlistener

Closes #4xe05r8
Description
Fixes # (CU-4xe05r8)
Type of change
Add keyup eventlistener
How Has This Been Tested?

[x] I did tests testing the change in my<EMAIL_ADDRESS>line 1274

Task linked: CU-4xe05r8 Trigger/Segment Query Builder / Blur Event Fix (1 less click for user when adding a filter)


wip: start/stop threads commands

Fixes #415
Changes proposed in this PR:

start/stop indexing command (all or just specific chain id)

think we need one more rebase 😄


Add beforeCreateFunc to add required edges to ent before the item is created

This PR resolves https://github.com/Yiling-J/carrier/issues/4

[X] Tests
[X] Documentation

@dominikstraessle
How about using same way as lazy field by adding ent creator to Mutator as a field? So user can still access the values from Mutator in PreCreate function. And lazy function can also benefit from this.
So this is lazy example in README:
entUserMetaFactory.SetEmailLazy(
	func(ctx context.Context, i *factory.EntUserMutator) (string, error) {
		return<EMAIL_ADDRESS>i.Name), nil
	},
)

And the PreCreate example would be:
groupMetaFactory.SetBeforeCreateFunc(func(ctx context.Context, i *factory.EntUserMutator) error {
	user, err := client.User.Create().
		SetAge(30).
		SetName("John").
		Save(ctx)
	if err != nil {
		return err
	}
	i.Creator.AddUsers(user)
	return nil
})

Or maybe use a privite field _entCreator to avoid conflict and expose a method instead:
i.Creator().AddUsers(user)

Thanks for the contribution @dominikstraessle. Let me merge first and do some refactor based on your work. The final result would be the example in my reply.


Add resolve configuration in Webpack to avoid using relative paths in import

Hi guys.
I was wondering why don't you added some config like this in Webpack, to start doing
import foo from 'components/foo';
instead of
import foo from '../../components/foo';
Is there any issue about it?
Thank for your patience.

It’s been suggested quite a few times before (please search for "absolute imports" in issues). We won't be supporting it on Webpack level because it is incompatible with Node resolution mechanism.
But if you'd like, you can work around it by adding
NODE_PATH=src

to your .env file in project root.
Then this will work. Alternatively you can symlink node_modules/components to src/components and it will work too.
Hope this helps!

Adding the path to .env file doesn't seem to work.
I generated a new project using create-react-app test, edited index.js to import App from 'App'; instead of import App from './App'; and all I'm getting is
Failed to compile.

./src/index.js
Module not found: Can't resolve 'App' in '/var/www/test/src'

The only way I could get it working was by changing the start script to be "start": "NODE_PATH=src react-scripts start".
Is there a reason why my .env file is not being picked up?

Maybe you have a global system-wide NODE_PATH set and so .env is ignored. I'm not really sure how we should handle this. Ignoring existing keys almost always makes sense but not sure about this case.

I do indeed:
$ echo $NODE_PATH
/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript

How about doing something like export NODE_PATH="${NODE_PATH}:/path/to/src"?

It would be nice if this kind of substitution "just worked" in env files. Not sure if dotenv supports (or wants to support) this.

i found i have a global node path too.what should i do?

I'd recommend disabling it on your computer. You're going to run into more issues otherwise.

i am new in node ,pls tell me how to disbling the global node path.thx

It’s an environment variable. You need to figure out what’s setting it, and remove that. Unfortunately I don’t know how to debug this. You might want to ask on some Node discussion board.

i finally remove it by  using unset NODE_PATH thx @gaearon


[BUG] Failing to compile on android

Describe the bug
After updating to the latest react native version (0.72) and trying to run android or compile it for production, it fails with an error.
To Reproduce
Run android debug or try to compile android for release
Expected behavior
Compilation does not fail
Screenshots

* What went wrong:
Execution failed for task ':usercentrics_react-native-sdk:compileDebugKotlin'.
> 'compileDebugJavaWithJavac' task (current target is 11) and 'compileDebugKotlin' task (current target is 1.8) jvm target compatibility should be set to the same Java version.
  Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain

Additional context
react-native: 0.72

Repo to recreate: https://github.com/joleb/usercentrics-android-error/tree/0.72.0

Hey @joleb
have you tried changing the java version you are targeting in your compliance options of the app build.gradle file:

Cheers,
Rui

Hey @userCTest ,
I tried it multiple times with different variants, even trying to add to kotlin options, which almost always lead to the same result of not being able to compile it.

Hey @joleb ,
so you still get the same message if you set the compileOptions as below?

Hey @joleb ,
I being doing some testing on your repo and found the issue I think. You need to  change the grade version to < 8, e.g. 7.5

That coupled with the previous change of adding
compileOptions {
        sourceCompatibility = JavaVersion.VERSION_11
        targetCompatibility = JavaVersion.VERSION_11
    }

to the android block of the app build.gradle made the app compile without issues. Seems to be an issue with the gradle version 8+ that we will investigate.
Let me know if this helps.

Great news @joleb, thanks for the info.
Glad to help 😄
I've opened an internal ticket to see what might be the issue with newer gradle versions.
Will let you know once we have news.
Cheers

Hey @joleb
just wanted to let you know that the latest version of the SDK now supports gradle 8+
Have a look and let us know if you find any issues.
Cheers,
Rui

Hello @uc-rreis , the same error occurs when trying to use the latest react native version. It seems like that the latest gradle versions are no longer supported: https://github.com/Usercentrics/react-native-sdk/commit/140e45cc172cc614bc202b2c64eeb6ca8c804877

hi @joleb , we haven't changed anything on this matter, so it's kinda odd that this is happening... can you provide more details, please?

I cannot build the Android app with the latest React native and usercentrics versions. I get the following error.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':usercentrics_react-native-sdk:compileDebugKotlin'.
> 'compileDebugJavaWithJavac' task (current target is 17) and 'compileDebugKotlin' task (current target is 1.8) JVM target compatibility should be set to the same Java version.
  Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain

I'm using following versions:
"@usercentrics/react-native-sdk": "2.11.3",
"react-native": "0.73.2"

This has been a blocker for me in upgrading my project to the latest react-native version. 😞
I tried setting different compileOptions and kolinOptions in my project, but nothing helped. The same error was thrown.
Then I had a look on usercentrics react native sdk android/build.gradle and noticed jvmTarget is set to '1.8'.  In react-native 0.73, java 17 is a requirement now and according to docs, Kotlin 1.8.0 can generate classes with a bytecode version corresponding to JVM 19. So I removed this jvmTarget = '1.8' and I believe sourceCompatibility and targetCompatibility can still stay with JavaVersion.VERSION_1_8. I can get the project working with this patch and the usercentric features are working so far.
Here is the patch I created.
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 64ebf4b..1aac99b 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -34,10 +34,6 @@ android {
         targetCompatibility JavaVersion.VERSION_1_8
     }

-    kotlinOptions {
-        jvmTarget = '1.8'
-    }
-
     sourceSets {
         main.java.srcDirs += 'src/main/kotlin'
     }

I'm not a native Android developer, so I have little knowledge of this area. I'm not sure if this is the proper fix or what issues this might bring in.
@uc-leo Do you know any other ways I can try to get this working with react native-version 0.73? or any information regarding a timeline of a new version of usercentrics will be out supporting react-native 0.73?

We are also blocked by this, so any further updates would be much appreciated.

Hey @uc-leo , basically the same behaviour @csath described.

Hey guys,
I'll try having a look, will let you know as soon as I have any updates.
Cheers,
Rui

Hey Guys,
just wanted to give you a heads-up that we will be looking into fixing the issue.
As soon as we have any updates, we'll let you know.
Cheers,
Rui

Hey Guys,
just wanted to give you a heads-up that we will be looking into fixing the issue. As soon as we have any updates, we'll let you know.
Cheers, Rui

Thanks a lot. I have already rolled out our app to 100% users with the above patch I mentioned and it works without any problems.
I'm waiting for a updated version of this library to get rid of this patch. 🤞

thank you all for the effort and time invested on this issue 🤘
PR: #108


adjust hashID in embed

adjusting the hashID to match DEGEN's hashID placement

Merging as this was previously reviewed


Very rarely particles sneak through walls

Not sure why this happens, need to look at the algorithm and/or tolerances

Need a setup to see if I can reproduce it


How can I get extended tweets (full text) and expansions in Academic Search(Api v2)?

Here is my code:
gen = tweepy.Paginator(client.search_all_tweets,
                       '#covid19vaccineyesplease lang:en',
                       start_time='2021-02-01T00:00:00Z',
                       end_time = '2021-02-28T00:00:00Z',
                       expansions = ['author_id','referenced_tweets.id','referenced_tweets.id.author_id','in_reply_to_user_id','attachments.media_keys','entities.mentions.username'],
                       tweet_fields=['id','text','author_id','created_at','conversation_id','entities','public_metrics','referenced_tweets'],
                       user_fields=['id','name','username','created_at','description','public_metrics','verified'],
                       place_fields=['full_name','id'],
                       media_fields=['type','url','alt_text','public_metrics'],
                       max_results=10).flatten(10)

Here is one of the tweets:
{'author_id': '1951791067',
 'public_metrics': {'retweet_count': 4,
  'reply_count': 0,
  'like_count': 0,
  'quote_count': 0},
 'referenced_tweets': [{'type': 'retweeted', 'id': '1360640286737727488'}],
 'entities': {'mentions': [{'start': 3,
    'end': 10,
    'username': 'BWIHUK',
    'id': '1157738484737675270'},
   {'start': 80, 'end': 88, 'username': 'Ral_sez', 'id': '26884860'}],
  'hashtags': [{'start': 110, 'end': 118, 'tag': 'covid19'},
   {'start': 119, 'end': 139, 'tag': 'coronavirusvacccine'}]},
 'id': '1360663119945736192',
 'conversation_id': '1360663119945736192',
 'created_at': '2021-02-13T18:52:22.000Z',
 'text': 'RT @BWIHUK: Thanks for a thorough explanation of the vaccines and how they work @Ral_sez very well explained. #covid19 #coronavirusvacccine…'}

Q1: How can I get the full text of the tweet? I only found the extended tweets model in tweepy.API, rather than tweepy.Client.
Q2: It seems that I do not get all the expansions such as 'referenced_tweets.id.author_id', 'place_fields' and 'user_fields'
Many thanks for your time!

A1:

Twitter API v2 is built from the ground up to support Tweets with up to 280 characters. With v2, there is no concept of 'extended' Tweets.

https://developer.twitter.com/en/docs/twitter-api/tweets/search/migrate/standard-to-twitter-api-v2
The text is truncated because it's a Retweet. You'll have to get the full text from the Tweet being Retweeted.
A2: All of those will be part of the includes response/data object. You can read more about that in the documentation on expansions and fields parameters. Paginator.flatten will flatten the data and make includes inaccessible. You'll have to iterate through the Responses if you want to use includes.
As an example, you can access the text of that Tweet being Retweeted like so:
>>> for response in tweepy.Paginator(
...     client.search_all_tweets, '#covid19vaccineyesplease lang:en',
...     start_time='2021-02-01T00:00:00Z', end_time='2021-02-28T00:00:00Z',
...     expansions=[
...         'author_id', 'referenced_tweets.id', 'referenced_tweets.id.author_id',
...         'in_reply_to_user_id', 'attachments.media_keys',
...         'entities.mentions.username'
...     ],
...     tweet_fields=[
...         'id', 'text', 'author_id', 'created_at', 'conversation_id', 'entities',
...         'public_metrics','referenced_tweets'
...     ],
...     user_fields=[
...         'id','name', 'username', 'created_at', 'description', 'public_metrics',
...         'verified'
...     ],
...     place_fields=['full_name', 'id'],
...     media_fields=['type', 'url', 'alt_text', 'public_metrics'],
...     max_results=10,
...     limit=1
... ):
...     referenced_tweets = {
...         referenced_tweet.id: referenced_tweet
...         for referenced_tweet in response.includes["tweets"]
...     }
...     tweets = {
...         tweet.id: tweet for tweet in response.data
...     }
...     tweet = tweets[1360663119945736192]
...     referenced_tweet = referenced_tweets[tweet.referenced_tweets[0].id]
...     print(referenced_tweet.text)
...
Thanks for a thorough explanation of the vaccines and how they work @Ral_sez very well explained. #covid19 #coronavirusvacccine #covid19vaccineyesplease


use  as model_name if it can't be determined

use  as model_name if it can't be determined so that all downstream traces can be logged successfully.

Thank you very much for this Pull Request. Solve the problem using ChatOllama of this issue I indicated: bug: Callback Handler Issue with ChatOllama (Langchain) #622. Although in ChatLiteLLLM I get an error (which probably would also be before) and it does not register the response from the assistant. I will try to look at it.
A suggestion, out of ignorance, might it be a good idea to put the model name instead of "unknown"? At least if it exists. Writing the line like this:
model_name = kwargs["invocation_params"]["model_name"] if "model_name" in kwargs["invocation_params"] else kwargs.get("invocation_params").get("model")
When using ChatLiteLLLM, the model name appears correctly. When using ChatOllama, the model name doesn´t appear (I don´t know why), but there is no error.

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

@yueming-zhang and @DavidLMS this was resolved in this commit: https://github.com/langfuse/langfuse-python/commit/737ae20c21206cac136e3dfd4409b027a1ebc25d
Thanks a lot for the contribution!


bedCountSam

Description

🐛 Bug Report

Testing

None
Checklist before requesting a review

[ ] I performed a self-review of my code
[ ] If it this a core feature, I added thorough tests
[ ] The command go fmt or make clean was used on all files included

Just saw this come up and wanted to recommend an alternative that may save you some time. Unless you need this to work on sams an alternative method would be to used an indexed bam and call SeekBamReagion(bamReader, bed.Start, bed.End) which will return the reads overlapping the bed region. You could then just divide the number of reads by the length of the region. This will likely be a lot faster than reading through a whole same file, especially if you bed regions cover a small portion of the genome.

Thanks Dan, i didn't know that function existed. definitely will use it


(feat req) - add todoist link option to postfix

something like {todoist_url}.
It would be ideal if this url were in hyperlink format.
ex:
[task](https://todoist.com/app/task/<id>)
Let me know what you think

I'd like this functionality as well. Having it paste in as a full hyperlink might be hard to juggle with the default behavior of bringing in the title text though.
OTOH, a prefix of - [x] [ and a postfix of ](todoist_url) (inserted as a raw URL) would give me exactly what I want: a clickable link back to the original task, with an Obsidian checkbox marked complete.

Hi @erauner12 @geoelectric
Thanks for the suggestions!
This issue seems like a duplicate of https://github.com/Ledaryy/obsidian-todoist-completed-tasks/issues/24
so, I'll close this one.


POL-430 add check that AWS account array name exists before assigning it

Description
Added check that AWS account array is not empty before assigning it
Issues Resolved
Bug with error "Cannot access member 'name' of undefined" from trying to access an empty array
Contribution Check List

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

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


Added info to setup.py file

I noticed this file could do with some improvements so I added some key information.

Hi @mdonkorka , thank you for creating this PR. I see that you are trying to add some metadata into setup.py.
The same metadata already exists in setup.cfg: https://github.com/cyyc1/jupyter-notebook-parser/blob/a9d18cda6d0c2a2f29582182db33713ec6e47971/setup.cfg
IIRC if we opt to use setup.cfg we should leave the setup() method in setup.py empty. I'd be glad to be proven wrong though.


Pane textures do not connect when windowlogged

Both are Creates horizontal framed glass pane.

I have run into the same issue with vanilla spruce stairs and connected glass panes.

Oh i have long been aware of this, but i didn't yet find a reasonable way of resolving this issue without breaking too many other create addons or create itself. Which is why this issue is staying open, until i learn/simi implements a way to achieve that by reasonable means.
Of course, if you have any good ideas, you can PR a fix and i'll happily merge it.

Nah, sorry, I'm just a whiney user :D

If you use the connecting glass from the Connected Glass mod, it also doesn't visually connect. It does work though, so that's nice.


[@tests] update saucelabs version through wtr

Saucelabs recommend we update our sauce connect version. We were a major version behind. 6.
After an update landed forweb-test-runner-saucelabs, we could update as well.
https://github.com/modernweb-dev/web/pull/1967
https://github.com/lit/lit/pull/2933

accomplished with:
https://github.com/lit/lit/pull/2933


GROUP BY + LIMIT rewrite incorrect

Please answer these questions before submitting your issue. Thanks!
Which version of Sharding-Jdbc do you using?
1.5.0
Expected behavior
SELECT user_id FROM t_order GROUP BY user_id LIMIT ?

=>
SELECT user_id FROM t_order GROUP BY user_id ORDER BY user_id ASC LIMIT ?

Actual behavior
SELECT user_id FROM t_order GROUP BY user_id LIMIT ?

=>
SELECT user_id FROM t_order GROUP BY user_id LIMIT ORDER BY user_id ASC

fixed at 1.5.1


Crashing in iOS 10

      tokenView.promptText = "Top 5: "         tokenView.placeholder = "Type to search"         tokenView.descriptionText = "Languages"         tokenView.maxTokenLimit = 5 //default is -1 for unlimited number of tokens         tokenView.style = .squared
I added token view in my tableview cell. the private property _tokenField is crashing if I add promptText, placeholder, description.

Please provide sample code, how are you using it.

@khawars  I already added sample code. I am using tokenView inside the tableviewCell.


Import a bunch of new Functions related contracts.

Some are vendored in this project, where not available at @chainlink/contracts.

Please Ignore. This is a glorified stash.


Skip loading json metadata from file for broken file

Description
As reported in https://github.com/0xPolygon/polygon-edge/issues/824, json file of snapshots and metadata will be broken very rarely. Basically this issue happens when saving json, which is done in Close() of consensus was interrupted by panic from other modules' closing processes. This PR will not fix this issue and will work on another PR. But this PR adds a tolerance against such problem in loading json file. If json file is broken, consensus stops using the data from json file and recover data from local chain as it does in case of missing json file.
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[x] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

Manual tests
Please complete this section if you ran manual tests for this functionality, otherwise delete it
Documentation update
Please link the documentation update PR in this section if it's present, otherwise delete it
Additional comments
Please post additional comments in this section if you have them, otherwise delete it

Much appreciated as always @Kourin1996!

@Vuksan Recover snapshot from local chains

@trimixlover ping


Implementing API Endpoints in the Frontend

Its good you are making habit of creating issues. Next time try and keep the naming scheme consistent with the commit verb scheme. In this instance, "implementing" would be "implement". Good stuff regardless.

This issue is related to #26 . Merge will close both.

@reesedychiao For the login, the frontend should send a POST request with the following JSON values:

Username
Password
Email
Netid

The backend will respond with everything sent to it except for the password. If there is an error, do not log the user in. The error will be of the status code 401 in the HTTP header. This is how you will know there is an error. In the JSON body of the backend's response, there will also be a reason for the error.

closed by #29


[Android]: Could not resolve androidx.activity:activity:1.2.0.

🐛 Bug Report
Android Build error: Could not resolve androidx.activity:activity:1.2.0.
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'MyApp'.
> Could not determine the dependencies of null.
   > Could not resolve all task dependencies for configuration ':classpath'.
      > Could not resolve androidx.activity:activity:1.2.0.
        Required by:
            project : > com.facebook.android:facebook-android-sdk:16.2.0 > com.facebook.android:facebook-common:16.2.0
         > No matching variant of androidx.activity:activity:1.2.0 was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5.1' but:
             - Variant 'releaseApiPublication' capability androidx.activity:activity:1.2.0 declares a library, and its dependencies declared externally:
                 - Incompatible because this component declares an API of a component, with the library elements 'aar' and the consumer needed a runtime of a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'releaseRuntimePublication' capability androidx.activity:activity:1.2.0 declares a runtime of a library, and its dependencies declared externally:
                 - Incompatible because this component declares a component, with the library elements 'aar' and the consumer needed a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'sourcesElements' capability androidx.activity:activity:1.2.0 declares a runtime of a component, and its dependencies declared externally:
                 - Incompatible because this component declares documentation and the consumer needed a library
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about its elements (required them packaged as a jar)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
      > Could not resolve androidx.fragment:fragment:1.3.0.
        Required by:
            project : > com.facebook.android:facebook-android-sdk:16.2.0 > com.facebook.android:facebook-common:16.2.0
         > No matching variant of androidx.fragment:fragment:1.3.0 was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5.1' but:
             - Variant 'releaseApiPublication' capability androidx.fragment:fragment:1.3.0 declares a library, and its dependencies declared externally:
                 - Incompatible because this component declares an API of a component, with the library elements 'aar' and the consumer needed a runtime of a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'releaseRuntimePublication' capability androidx.fragment:fragment:1.3.0 declares a runtime of a library, and its dependencies declared externally:
                 - Incompatible because this component declares a component, with the library elements 'aar' and the consumer needed a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'sourcesElements' capability androidx.fragment:fragment:1.3.0 declares a runtime of a component, and its dependencies declared externally:
                 - Incompatible because this component declares documentation and the consumer needed a library
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about its elements (required them packaged as a jar)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
      > Could not resolve androidx.fragment:fragment:1.0.0.
        Required by:
            project : > com.facebook.android:facebook-android-sdk:16.2.0 > com.facebook.android:facebook-common:16.2.0 > androidx.legacy:legacy-support-v4:1.0.0
         > No matching variant of androidx.fragment:fragment:1.3.0 was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5.1' but:
             - Variant 'releaseApiPublication' capability androidx.fragment:fragment:1.3.0 declares a library, and its dependencies declared externally:
                 - Incompatible because this component declares an API of a component, with the library elements 'aar' and the consumer needed a runtime of a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'releaseRuntimePublication' capability androidx.fragment:fragment:1.3.0 declares a runtime of a library, and its dependencies declared externally:
                 - Incompatible because this component declares a component, with the library elements 'aar' and the consumer needed a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'sourcesElements' capability androidx.fragment:fragment:1.3.0 declares a runtime of a component, and its dependencies declared externally:
                 - Incompatible because this component declares documentation and the consumer needed a library
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about its elements (required them packaged as a jar)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
      > Could not resolve androidx.fragment:fragment:1.1.0.
        Required by:
            project : > com.facebook.android:facebook-android-sdk:16.2.0 > com.facebook.android:facebook-common:16.2.0 > androidx.appcompat:appcompat:1.1.0
         > No matching variant of androidx.fragment:fragment:1.3.0 was found. The consumer was configured to find a runtime of a library compatible with Java 11, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.5.1' but:
             - Variant 'releaseApiPublication' capability androidx.fragment:fragment:1.3.0 declares a library, and its dependencies declared externally:
                 - Incompatible because this component declares an API of a component, with the library elements 'aar' and the consumer needed a runtime of a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'releaseRuntimePublication' capability androidx.fragment:fragment:1.3.0 declares a runtime of a library, and its dependencies declared externally:
                 - Incompatible because this component declares a component, with the library elements 'aar' and the consumer needed a component, packaged as a jar
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')
             - Variant 'sourcesElements' capability androidx.fragment:fragment:1.3.0 declares a runtime of a component, and its dependencies declared externally:
                 - Incompatible because this component declares documentation and the consumer needed a library
                 - Other compatible attributes:
                     - Doesn't say anything about its target Java version (required compatibility with Java 11)
                     - Doesn't say anything about its elements (required them packaged as a jar)
                     - Doesn't say anything about org.gradle.plugin.api-version (required '7.5.1')

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 32s

Error when trying to run Android
To Reproduce
Follow installation steps for Android
Expected Behavior
Android builds
Code Example
No code added, just trying to get the very same app to run
Environment
System:
OS: macOS 13.5.2
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 85.63 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
Yarn: Not Found
npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.12.1 - /Users/steff/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10671973
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
Languages:
Java: 11.0.20 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.7 => 0.71.7
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

perhaps facebook-android-sdk has released a new version and we could adopt it here?
PRs happily accepted


bug(python-sdk): spawn_workflow feature bug due to misnamed ClientImpl rest_client property.

Bug description
Use Child Workflow with spawn_workflow feature lead to error

"This step failed with error 'ClientImpl' object has no attribute 'rest_client'"

Context
pip show hatchet-sdk

Name: hatchet-sdk
Version: 0.21.0
Summary:
Home-page:
Author: Alexander Belanger
Author-email<EMAIL_ADDRESS>License:
Location: /home/mathieu/Projet/Data Pipelines/Hatchet/sdk/venv/lib/python3.10/site-packages
Requires: aiostream, grpcio, grpcio-tools, loguru, protobuf, pydantic, python-dateutil, python-dotenv, pyyaml, urllib3
Required-by:

How to reproduce ?
I wrote a minimal PoC reproducing the issue:
from dotenv import load_dotenv
import asyncio
from hatchet_sdk import Hatchet, Context

load_dotenv()

hatchet = Hatchet(debug=True)

@hatchet.workflow(name="subflow", on_events=["user:create"])
class Subflow:
    @hatchet.step()
    def first_subflow_step(self, context: Context):
        word: str = context.workflow_input()["word"]
        return {
            "word": word.capitalize()
        }

@hatchet.workflow(name="mainflow", on_events=["user:create"])
class Mainflow:
    @hatchet.step()
    async def split_workflow(self, context: Context):
        data = [
            "this",
            "is",
            "awesome",
            "!"
        ]
        futures = []
        for word in data:
            future = context.spawn_workflow("subflow", input={"word": word})
            futures.append(future.result())

        results = await asyncio.gather(*futures)
        return {
            "sentence" : ' '.join([word["first_subflow_step"]["word"] for word in results])
        }

worker = hatchet.worker('ChildTest', max_runs=100)
worker.register_workflow(Mainflow())
worker.register_workflow(Subflow())

worker.start()

Expected result :
{
  "sentence": "This Is Awesome !"
}

Raised error :
[
  "This step failed with error 'ClientImpl' object has no attribute 'rest_client'"
]

Solution
I found that rest_client property of ClientImpl class has been recently renamed to rest. This change seems not to be propagated to context.py :
class ChildWorkflowRef:
    ...
    def getResult(self) -> StepRunEvent:
        try:
-          res = self.client.rest_client.workflow_run_get(self.workflow_run_id)
+          res = self.client.rest.workflow_run_get(self.workflow_run_id)

Using the right property name solve the error and the workflow works.

@mathieudupoux this should be fixed in Python SDK 0.21.1


The default functions has wrong behave to handle param given in url

Plugin name and version
Maven Plugin for Azure Functions
Plugin configuration in your pom.xml
pom.txt(the default maven create)
Expected behavior
when running the function,and excute the command "curl http://localhost:7071/api/hello?req=world", it should return "Hello, world"
Actual behavior
get the 400 response
Steps to reproduce the problem
with the guideline https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven , the default function created by maven is below:
`@FunctionName("hello")
public HttpResponseMessage hello(@HttpTrigger(name = "req", methods = {"get", "post"}, authLevel = AuthorizationLevel.ANONYMOUS) HttpRequestMessage request,
final ExecutionContext context) {
context.getLogger().info("Java HTTP trigger processed a request.");
    // Parse query parameter
    String name = request.getQueryParameters().get("name");

    if (name == null) {
        // Get request body
        Object body = request.getBody();
        if (body != null) {
            name = body.toString();
        }
    }

    if (name == null) {
        return request.createResponse(400, "Please pass a name on the query string or in the request body");
    } else {
        return request.createResponse(200, "Hello, " + name);
    }
}`

there is a confuse: why the parameter key is named "name" in code rather than“req”
String name = request.getQueryParameters().get("name");"

If I change the code "String name = request.getQueryParameters().get("name");" to be "String name = request.getQueryParameters().get("req");"
and excute the command "curl http://localhost:7071/api/hello?req=world", then it get 400 response,that is it can not get the parameter "req".That is, the function can only handle the "name" param

@JunyiYi  Above code is coming from Azure Functions Java templates. Could you help explain more about this issue?

We are upgrading to BETA-2 runtime now, so the sample above is somehow out-of-dated, we will update the templates soon. But for your questions:

"req" is the name of HttpTrigger that represents the whole http request message, while "name" is the query parameter within that http request message; which is to say, "req" contains a query parameter called "name". So the URL to trigger it should be "curl http://localhost:7071/api/hello?name=world".
This should work. At least in BETA-2.

@JunyiYi thanks.
but it still cannot work well in  version 2.0.1-beta.21.
below I restate the steps:
change the default templates line 21 the "name" string to "param" :
String name = request.getQueryParameters().get("param");
then execute the command: curl http://localhost:7071/api/hello?param=a
it get 400 response,while execute  curl http://localhost:7071/api/hello?name=a, it get "right" response

Did you rerun the whole mvn clean package and then mvn azure-functions:run after you change the code from "name" to "param"?

@JunyiYi yes. I have rerun the command.and today it work well while date 11-12 can not work.
Now,I still confuse the code: name="req" in  @HttpTrigger .
As you say:

"req" is the name of HttpTrigger that represents the whole http request message

But what is the "req" use for? Since there is a HttpRequestMessage parameter named "request".
Would you mind show me an example? thanks.

Sure. So first let me explain about the whole maven plugin:

You write *.java code as functions
After you run mvn clean package, it will generate 3 things in target/azure-functions/**/.:

*.jar which contains your logic
function.json which used to declare all bindings
host.json which used to declare the host configuration

mvn azure-functions:run will invoke NodeJS Azure Functions Runtime you installed globally, which only recognizes host.json and functions.json, it doesn't care about anything in Java.

So "req" is used as the binding name in function.json mentioned above.  You do not directly use it, but Azure Functions Runtime cares about it. And the HTTP parameters are metadata in the "req" binding.

@JunyiYi thank you for you reply

@JunyiYi  Can you please let me know how to update azure-functions-java-core to the latest.  My current version in the POM shows [1.0.0-beta-1,1.0.0)

Just update <version>1.0.0-beta-2</version> section of the azure-functions-java-core dependency in your POM.xml.

Close it since the problem looks to have been solved.


Alternate style for user icons

What do you think about adding an alternate user icon set?
I like the current one, but I think this rounded version would fit certain designs better and is a pretty conventional style:

Vote +1


Consider adding ES6 support

Hi there,
Great work with the template.
I thought it would be cool if you could add ES6 support, I believe gulp has gulp-babel that can transpile ES6 -> ES5?
https://onsen.io/blog/trying-out-javascript-es6-using-babel/

This is planned, although we should give an ES6/TypeScript choice.

Have added a TODO to implement a Babel feature as opposed to the current TypeScript feature we have already.

Thank you that would be great,
I didn't see the TODO list before I like it
Just so you know jquery validation plugin now includes the minified version in npm if you use package 1.16.0

Cool! I actually submitted the PR to add that.

Updated to 1.16.0


CLI: get schema by ID

Currently a user can view schemas in an mcap file with mcap list schemas. However, it is difficult to actually extract a schema from the output since it is rendered in table form.
It would be useful to also support an mcap get schema <id> that returns just the schema for that ID. Questions to consider:

Is get the verb we want to go with? This should match what we do for attachments as well I expect.
Should this command also return the rest of the metadata for that schema in some way? Or perhaps it should render the table view by default, and support a --schema-only flag?

Is this related to #402 ?


mockPeerChaincode not working

First of all, thank you for this project, it has been really helpful to make the chaincode migrations from Go to TS <3
But I found a problem with mockPeerChaincode, trying to make a chaincode invoke another one. Looks like invokables is not being initialized anywhere, and also the invokeChaincode functions is calling the wrong function otherStub.MockInvoke and the correct one is otherStub.mockInvoke.
If I get some time in the near future I'll submit a PR with the fixes, just reporting these for now.

Thanks for reporting, this feature isn't included in the tests, so I'm not suprised it isn't working.


Submitting a "purge" job doesn't set the update flag on the server.

Set parents too!!!!

Seems like the code to set the update bit is not in the API submission path, but it is in the UI submission path.

Also shouldn't set the update flag on OFFLINE servers


Documentation examples to also include serializing to Rust examples

Hi!
For the arrays there is a great line about conceptualising how an Arrow concept fits into Rust, for example this handy snippet:
/// A [`Utf8Array`] is arrow's equivalent of an immutable `Vec<Option<String>>`.
/// Cloning and slicing this struct is `O(1)`.

Are there thoughts around also providing examples to convert this back to Rust Vec<Option<String>> (or whatever the context is) in an efficient/recommended way?

Good point. I have been trying improve the docs to achieve that. In main we have something like that already:
https://github.com/jorgecarleitao/arrow2/blob/main/src/array/utf8/mod.rs#L37
but improvements are always welcome ^^

Awesome!
I'll take notes about how I convert them and maybe write a guide, it would be handy for the getting started guide that exists.

@jkcoxson, thanks for your interest!
Could you provide the function signature that you are looking for? (e.g. fn f(chunk: Chunk, index: usize) -> Option<PrimitiveArray<i32>> {todo!()}?) just so we get an idea of the documentation.
This because the arrow spec is quite extensive and it is a bit difficult to narrow this issue to a concrete usecase.

Might be worth converting this into a discussion @jorgecarleitao :)


Are your mod is spawning mobs with Armours?

Additional some mobs are glowing? Is this also caused by your mod? Can you add a config to disable this?

Hi, I will need more info about the mods you installed.

Mobs can spawn with armour in vanilla minecraft. It depends on the local difficulty: the more you stay in a place, the more likely it is that there spawn mobs with armours. I didn't change anything about rate of spawn or anything related.
Mobs can have glowing effect in only two ways in vanilla and I didn't add any behavior related to glowing:

You hit them with a spectral arrow
Pillagers close to a bell you're ringing during a raid

So my best guess is that you installed other mods modifying the mobs. Hope it helped =)


ORC-1563: Fix documentation Spark and Hive configuration

What changes were proposed in this pull request?

Add orc.compress enumeration value description
Fix orc.bloom.filter.fpp default value (ORC-1338)

Why are the changes needed?
The document is out of date.
How was this patch tested?
local check

For ORC-1563, we can backport this to branch-1.8 because ORC-1338 is Apache ORC 1.8.2, @cxzl25 .

Merged to main/1.9/1.8.
I also published the fixed doc to the webpage, @cxzl25 .

https://orc.apache.org/docs/spark-config.html
https://orc.apache.org/docs/hive-config.html


adding solution to convert_age_to_days

Description
enter here if you have any details
Program Name - Hactoberfest2020
Issue No.- #334

Type issue number after hash(#)

Checklist(self check)

[x] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

thank you @aayushi-droid for assign me this.


Inquiries about the log axis

Hello, I am making a logo map containing 200,000 sequences, so there are some amino acids with a frequency as low as 0.00005 (the highest is 100%, represented by 1), and such low-frequency amino acids cannot be seen in the picture , Therefore, I plan to use 10e-6, 10e-5, 10e-4...10e0, which has a uniform scale length on the integer scale of 10. I tried to use "plt.yscale('log')" but it seems that this function cannot be achieved, and because the frequency is between 0-1, I can't log the data first and then input the data to draw the graph.
So I would like to ask you if there is a way, or if there is hope to add this function to this python package. Looking forward to your reply and wish you all the best.

Hello, I think understand what you're saying, but it would be helpful for me if you could provide me a minimal example to reproduce your type of logo, and I can try to help with the visualization of the low-frequency amino-acids from there. Thanks.
Ammar

Hello @liyunjian , pinging you for a minimal example. Thanks.

Hello, atareen, I am sorry that I have been busy these days and forgot to reply you.
I created a fasta file containing 10,000 amino acid sequences, each of them is "MFVFLVLLPM", which will be used as a reference sequence. Then I changed the first "M" of the first sequence to "L", the second "F" of the first 100 sequences was changed to "M", and the last "M" of all sequences Change to "L".
In this way, the first "L" frequency of this file is 1/10000, the second "M" frequency is 100/10000, and the last "L" frequency is 10000/10000.
thanks for your help.

test.zip

Hello, have you received this example, or what else needs to be provided. @atareen

Hello,
I took a quick look at your test.fasta file and wrote a notebook to visualize the low frequency amino acids. I can't attach the notebook here so I've pasted my minimal code at the end. Basically if I convert to a relative abundance or probability matrix, I have no issues the really low frequency amino-acids.
The follow is a logo from your file in linear scale:

This is with y-scale logged (really low frequency M is visible)

Note that in the log scaled logo, the individual Glyph objects representing amino-acids are really stretched due to their high frequency, but these can be fixed via applying some stylizing to the Glyph objects, as shown here:
https://github.com/jbkinney/logomaker/blob/master/logomaker/tutorials/6_glyph_objects.ipynb
I would suggest learning about the Glyph objects and play around with the functions alignment_to_matrix and it's different arguments. As far as I can, visualizing your data at really low frequencies should be totally possible with logomaker without changes to the underlying source, though it will need some advanced styling.
import numpy as np
import pandas as pd
import matplotlib.pyplot as plt
%matplotlib inline
plt.ion()

import logomaker as lm
with open("test/test.fasta","r") as f:
    raw_seqs = f.readlines()

seqs = [seq.strip() for seq in raw_seqs if ('#' not in seq) and ('>') not in seq]
# preview sequences
print('There are %d sequences, all of length %d'%(len(seqs), len(seqs[0])))

seqs_df = pd.DataFrame(seqs,columns=['sequence'])
print(seqs_df.value_counts())

# create a relative abundance matrix - can play around with pseudocount.
mat = lm.alignment_to_matrix(seqs,to_type='probability',pseudocount=0)
mat

# linear axis logo
fig, ax = plt.subplots(1,1,figsize=(12,3))
logo = lm.Logo(mat,ax=ax)

fig, ax = plt.subplots(1,1,figsize=(12,3))
logo = lm.Logo(mat,ax=ax)
ax.set_yscale('log')
#logo.style_glyphs_in_sequence('MMVFLVLLPL',color='blue')
ax.set_ylim(1e-3,1.1)
ax.set_title('Should be restyled with glyphs')

Hello, thank you for your help, I probably understand, let's learn.


Extract common icon concept from material to widget

So that icons in the generic sense can be reused in cupertino.
Very tentatively tagging API break. Though it shouldn't affect any users, except perhaps if user previously imported widget and also imported/implemented their own Icon class etc.

Will need for #9926

I don't think we will be able to do this. It would break pretty much every application ever.

Ok chatted offline:
We're just moving icon, not making a new one.
To solve some of the icon_theme->theme dependency, let icon theme just find a parent icon theme without referring to Theme directly, by having Theme actually insert IconThemes into the widget tree. Do the same text and let the original theme inherited widget still be an inherited widget as _Theme and let it be the child of a parent Theme grouping container that's a stateless widget which inserts IconTheme


[1.9] CI: disable bindings tests

Disable the bindings tests in the CI.  They primarilly targetted Podman
v2 development and pretty flaky and make backporting a bit harder.
So let's just silence them for the 1.9 branch.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

/lgtm


Fix mac install

Enforced binary install to prevent build-from-source suggestion causing install failures on mac

@phoebeheywood @nick-gorman if one of you has time in the next few days could you try running the updated install script to let me know if it works on windows?

[ ] tested install script on windows


evince: 3.36.5 -> 3.36.6

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/evince/versions.
meta.description for evince is: "GNOME's document viewer"
meta.homepage for evince is: "https://wiki.gnome.org/Apps/Evince"
meta.changelog for evince is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.36.6 with grep in /nix/store/92qlsddhlk4f4hghf0l48l09r3irblag-evince-3.36.6

directory tree listing: https://gist.github.com/48aaaa3de0d36ae4f9b4f4165ae0c433

du listing: https://gist.github.com/f6ca2072e9d83030360a9de7f2aecae4

Rebuild report (if merged into master) (click to expand)

21 total rebuild path(s)

7 package rebuild(s)

7 x86_64-linux rebuild(s)
7 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
7 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
denemo
evince
glom
gnome3.evince
gnome3.gnome-books
gnome3.gnome-documents
gnome3.sushi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/92qlsddhlk4f4hghf0l48l09r3irblag-evince-3.36.6 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A evince https://github.com/r-ryantm/nixpkgs/archive/5d356886bbc004a7a551f3212e8484980987de45.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/92qlsddhlk4f4hghf0l48l09r3irblag-evince-3.36.6
ls -la /nix/store/92qlsddhlk4f4hghf0l48l09r3irblag-evince-3.36.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

6 packages built:
- denemo
- evince
- glom
- gnome3.gnome-books
- gnome3.gnome-documents
- gnome3.sushi

Maintainer pings
cc @hedning @jtojnar @worldofpeace @vcunat for testing.

changes look okay: https://ftp.gnome.org/pub/GNOME/sources/evince/3.36/evince-3.36.6.news


Adding export for data added to sysdata

@rwdudley-usgs This should make what's going on more clear, sorry for the confusion.

No problem, @dblodgett-usgs. So I should generally be able to use the same syntax as that used with the histCounties data?

Yeah, more or less, the variable names will be different, but the subsetting method will be the same.

Ok, I have it working, but I'm not seeing all the HUCs for Maine showing up; I'm getting 10 of 21 of them. And if I search huc08Poly for, say, 01010001 (St. John), which is among the missing in the rendered map, it doesn't appear to be among the data. Could you confirm @dblodgett-usgs ?

@rwdudley-usgs - It looks like that huc8 isn't in the dataset...
The reason you aren't seeing everything is that the states field is a little weird in that it uses a comma separated list of states. I think you could use grepl to subset in this case?

I selected all the ones with 'ME' in the name in a GIS and got this:

Ok that helps. Yeah, I'll do a grepl.