how do i access "g"? i can only get the first value from g

                form, err := c.MultipartForm()
                if err != nil {

                        fmt.Printf("HELLO = %s\n",err)
                        return

                }

fmt.Printf("form  = %s\n",form)
      form  = &{map[c:[] city:[] country:[] d:[] f[]:[               ] g:[70010100 70011200 70011000] h:[] p:[] q:[] state:[] v:[]] map[]}

how do i access "g"? i can only get the first value from g
g := c.PostForm("g")
which is 70010100 and not the rest.
anyone knows how to get the other values of g from "form"?

fmt.Println(form.Value["g"])

fmt.Println(form.Value["g"])

thank you! u r the best!


Crashes when Monitor Disconnects

Fixed

No longer crashes, but freezes instead...

This should probably wait until I can rebase on upstream skulpin instead of my hacky fork

I'm hitting this very often when I do something that changes display geometry (i.e. reconnect to my RDP session after overnight) which results in the majority of my neovim sessions not closing cleanly, which results in my oldfiles not being updated :(
Is there anything I can do to help with this one?

We could start implementing a feature for saving changes on crashes as a temporary measure, but I would imagine this would have a much broader use case. I know Sublime Text has this feature.

This is most definitely a bug which should be raised upstream in sculpin. I will make an issue and start some debugging.
An auto saving feature seems interesting, but I'm nervous that for some users saving temporary files might not be desirable?
Further at the moment neovide doesn't even detect the crash which makes this harder...

Also the upstream to skulpin is done now. So the above comment https://github.com/Kethku/neovide/issues/147#issuecomment-591702037 is no longer valid

https://github.com/aclysma/skulpin/issues/47 Upstream issue is here

Are there flags I can pass to neovide that will collect the relevant logs?

--log

Log attached, but there doesn't seem to be anything of note in here.
neovide_rCURRENT.log
I'm running the windows build produced by this action run: https://github.com/Kethku/neovide/actions/runs/95481207
Unfortunately, I can't get a stack trace from the dump because the action doesn't publish .pdbs. I'm setting up my environment to build neovide and I'll collect more information about where it's crashing.

Further at the moment neovide doesn't even detect the crash which makes this harder...

Forgot about that. Looks like this requires more print statements.

Here's the stack trace I'm seeing. I was hoping I'd be able to get symbols for nvoglv64.dll from the nvidia symbol server, but no luck.

If you have any logging changes you'd want me to apply and repro with, I can do that.

@vivlim I just confirmed that the skulpin sdl2 example https://github.com/aclysma/skulpin/blob/master/examples/interactive_sdl2.rs exhibits the exact same issue (as far as I can tell).

Discussion here: https://gitter.im/neovide/community seems to indicate that the problem is indeed upstream

I believe this is fixed by https://github.com/aclysma/skulpin/pull/49 trying now

Yup! On windows this no longer crashes! Once the pr merges we can update the version and close this bug. @vivlim after that happens could you try on other platforms?

I changed the reference to neovide to point to aclysma/skulpin (https://github.com/vivlim/neovide/tree/point-skulpin-at-upstream) and found the following

Windows: I was able to repro the issue, and it went away after taking the upstream change
Linux (Ubuntu 19.10 / Intel): I wasn't able to repro the issue, no noticeable change either way.
Mac (10.15.3): I wasn't able to repro the issue, but I wasn't able to run neovide after pointing to upstream skulpin. I tried to narrow it down with one of the skulpin examples and found https://github.com/aclysma/skulpin/issues/50

Looks like the reason I wasn't able to run neovide on the Mac is because the vulkan debug layer was enabled and something's broken about my vulkan-sdk install. Disabling the debug layer allowed it to run, and everything seems fine.

This is now fixed. Closing


Is elastic_reqwest pulling its weight?

I'm working on support for cluster sniffing in #243 and am finding myself wanting our better response building in elastic. It feels like elastic_reqwest isn't really pulling its weight anymore.
I think we should merge elastic_reqwest into elastic, and keep a nice separation of the low-level client details from the high-level builders. It'll save some boilerplate too.
I'm interested in any feedback anyone else has here. It's a move towards something more opinionated than what we have now, but I feel like as an abstraction elastic_reqwest isn't really offering too much.

What do you think @stephanbuys?

I've started playing with this in the node-sniffer branch.
The idea is that we should be able to use the same low-level Sender trait for connection pooling as we do for making other client requests. I think with a bit of effort this could work out quite nicely.

Hi, I had a look and I fully agree, you approach on the load-balanced Async client is almost certainly the direction this library should take. Dragging the reqwest client forward seems unnecessary, while this lib is pre 1.0 you should be brutal (thinking Rust's own journey to 1.0).
From what I've seen the API still stays natural and isn't a massive departure (or increase of complexity) over reqwest, which is another huge plus.

Ok, the contents of the old elastic_reqwest crate are now in a new client::sender module in elastic. It's sitting  in the vNext branch now and will be part of the next breaking release.


Improve CI jobs mostly by adding '--workspace' where required

When working on wasmi_core sub crate I found that our current CI did not check certain properties of wasmi_core.

Would make sense to add all crates that should be build to the default-members instead of relying on --workspace, though.


(Suggestion) Add configurable option to make other doors act like Iron Doors

Hey Billy,
As you know Iron doors are awesome because only players can open then via a redstone input (assuming you're not using  pressure plates only haha).
However iron doors don't match every builds aesthetic and I'd be cool if we could find a way replicate that behavior over to the other doors.
My request would be to add a feature that would either
A) Create a item block tag state for doors that could be modified via /data modify block or /setblock , preferably some way a regular player could.
Example tag :
minecraft:spruce_door[facing=east,half=upper,hinge=right,open=false,powered=false,**deny-mob-use=true**,**deny-villager-use=true**]
doors:
    activate: false
     deny-mob-usage-block-tag: true
     deny-villager-usage-block-tag:true

B) add specific door types  in purpur config that can do this example:
doors:
   activate:false
   deny-mob-usage: true
   deny-villager-usage:true
   types:
   - minecraft:spruce_door
   - etc
   - etc

C) combo of A and B but also be
doors:
   activate:false
---- below is individual door toggle editable via block tags
  deny-mob-usage-block-tag: true
  deny-villager-usage-block-tag:true
---below is blanket usage
   deny-mob-usage: true
   deny-villager-usage:true
       types:
       - all
       or
       - minecraft:spruce_door
       - etc
       - etc

These are just examples, not sure what's doable but C) would be cool A) would be my preference if  C) is not doable so we can control this per door instead of blanket usage for each type.

Awesome! so this is a all or nothing option correct?

Awesome! so this is a all or nothing option correct?

https://pl3xgaming.github.io/PurpurDocs/Configuration/#door. You add which wooden doors require redstone through a list e.g.
door:
  requires-redstone:
    - oak_door
    - jungle_door

It's handled on a per-world basis.


Please add CMakeLists.txt

You can use xmake to generate a CMakeLists.txt if you wish.
xmake project -k cmakelists


Completed copyright add to source files for issue #8

All sources files are now updated with copyright info (this is in addition to pull request #23). Should be able to close out issue #8
Issue found @ https://github.com/numenta/numenta-web/issues/8

:+1: looks great please merge


Client host rejected: Access denied

First of all, thank you very much for setting up the docker environment!
The only problem I have right now is that I can't seem to send mail. I always get the following message:
Client host rejected: Access denied
Login is not an issue, just sending mail.

What's your configuration? (compose, userfile). We're blind 🙈

And paste more logs from postfix. Thanks.

Could you paste /etc/postfix/main.cf?

Here you go:
# See /usr/share/postfix/main.cf.dist for a commented, more complete version

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no
append_dot_mydomain = no
readme_directory = no

# Basic configuration
# myhostname =
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination =
relayhost =
mynetworks = <IP_ADDRESS>/8 [::1]/128 [fe80::]/64 <IP_ADDRESS>/16 <IP_ADDRESS>/16
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
#smtpd_tls_CAfile=
#smtp_tls_CAfile=
smtpd_tls_security_level = may
smtpd_use_tls=yes
smtp_tls_security_level = may
smtp_tls_loglevel = 1
tls_ssl_options = NO_COMPRESSION
tls_high_cipherlist=EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA
smtpd_tls_protocols=!SSLv2,!SSLv3
smtp_tls_protocols=!SSLv2,!SSLv3
smtpd_tls_mandatory_ciphers = high
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3
smtpd_tls_exclude_ciphers = aNULL, LOW, EXP, MEDIUM, ADH, AECDH, MD5, DSS, ECDSA, CAMELLIA128, 3DES, CAMELLIA256, RSA+AES, eNULL
smtpd_tls_CApath = /etc/ssl/certs
smtp_tls_CApath = /etc/ssl/certs

# Settings to prevent SPAM early
smtpd_helo_required = yes
smtpd_delay_reject = yes
smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, permit
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination,
    reject_unauth_pipelining, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_unknown_recipient_domain,
    reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net
smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unauth_pipelining
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unknown_sender_domain

# SASL
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = /var/spool/postfix/private/auth
smtpd_sasl_type = dovecot
dovecot_destination_recipient_limit = 1

smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
broken_sasl_auth_clients = yes

# Mail directory
virtual_mailbox_base = /var/mail
virtual_mailbox_domains = /etc/postfix/vhost
virtual_mailbox_maps = hash:/etc/postfix/vmailbox
virtual_alias_maps = hash:/etc/postfix/virtual
virtual_uid_maps = static:5000
virtual_gid_maps = static:5000
# Enable Dovecot Sieve
virtual_transport = dovecot

# Additional option for filtering
content_filter = smtp-amavis:[<IP_ADDRESS>]:10024

# Milters used by DKIM
milter_protocol = 2
milter_default_action = accept
smtpd_milters = inet:localhost:12301,inet:localhost:54321
non_smtpd_milters = inet:localhost:12301,inet:localhost:54321

Who is trying to send an email? A client configured with SMTP Auth? A web application trusted on the network?
Part of <IP_ADDRESS>/8 [::1]/128 [fe80::]/64 <IP_ADDRESS>/16 <IP_ADDRESS>/16?
What did you check so far?

I'm running the image in a VPS. I've added the e-mail account in my local machine to use the mail server within the docker image running on a VPS. I would want to be able to send mail from any device from this mail server.
I've read that it could have something to do with permit_sasl_authenticated or permit_mynetworks. As authenticated sasl users should be able to send mail, but according to the documentation these values appear to be OK.

@alycklama It seems that you are trying to perform SMTP authentication on 25 port. Please make sure that you are using 587 port for SMTP authentication.
Even better show your full client configuration.

The client configuration was set to port 143, but changing it to 587 didn't make any difference. I dived into the client settings and noticed that I hadn't filled in the authentication settings for the mail server. It fully makes sense now why I couldn't connect. The only problem I'm still facing is that I can't seem to send anything.
postfix/submission/smtpd[1430]: 57F3A224C5: client=unknown[x.x.x.x], sasl_method=PLAIN<EMAIL_ADDRESS>postfix/cleanup[1442]: 57F3A224C5<EMAIL_ADDRESS>opendkim[521]: 57F3A224C5: DKIM-Signature field added (s=mail, d=mydomain.com)
opendmarc[541]: 57F3A224C5: mydomain.com none
postfix/qmgr[1360]: 57F3A224C5<EMAIL_ADDRESS>size=689, nrcpt=1 (queue active)
postfix/smtp[1444]: connect to <IP_ADDRESS>[<IP_ADDRESS>]:10024: Connection refused
postfix/smtp[1444]: 57F3A224C5<EMAIL_ADDRESS>relay=none, delay=0.2, delays=0.2/0/0/0, dsn=4.4.1, status=deferred (connect to <IP_ADDRESS>[<IP_ADDRESS>]:10024: Connection refused)

Check that amavis is running.

I've added the following to the docker run command and now it works!
-h myhostname.com
The only question I have remaining has to do with ClamAV. It gives me a message in the log:
The virus database is older than 7 days!
Is there any cron job running that takes care of this within the container, or am I supposed to update it myself once in a while?

The hostname should be checked on startup t be sure that they've been setup.
I'll create an issue for that.
Regarding the virus database, freshclam is the command you may type on first boot to be synced.
There's a cron that should work every night :-)


Update dependencies

          1 Warning

:warning:
The podspec was updated, but there were no changes in either the Cartfile nor Cartfile.resolved. Did you forget updating Cartfile or Cartfile.resolved?

  Generated by :no_entry_sign: danger

Current coverage is 83.27% (diff: 100%)

Merging #842 into master will not change coverage

@@             master       #842   diff @@
==========================================
  Files            34         34
  Lines          2769       2769
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2306       2306
  Misses          463        463
  Partials          0          0

Powered by Codecov. Last update 3fdc051...35955d7

Yay Danger! :D

SwiftLint found issues
Warnings

File
Line
Reason

Moya+Internal.swift
111
Prefer -> Void over -> ().

Moya+Internal.swift
210
Prefer -> Void over -> ().

Moya.swift
5
Prefer -> Void over -> ().

Moya.swift
96
Prefer -> Void over -> ().

NetworkActivityPlugin.swift
12
Prefer -> Void over -> ().

  Generated by :no_entry_sign: danger

After this was merged, when I run pod install in the Demo directory, I get this:

I'm using the beta of the new cocoapods release because I was having issues with the current release. I think we just need a minor change to the Podfile to support this.

Strange; I don't think I have run into any issues myself doing this. 🤔

Yeah, I don't know what's going on here. After playing around a bit more, I think it is quite possible it was on my local machine. Running a pod update ReactiveSwift and not committing the changes seems to have solved it for me. This is likely some difference between cocoapods 1.1.1 and 1.2.0-beta3.


remoteach: use predictable TraceNumbers

Do we need to randomly generate TraceNumber values? We should be able to create sequential values starting at "ABA + 01" and the ACH library will increment them.
See: https://github.com/moov-io/ach/pull/537#discussion_r290038772 as this came up before
Code:

Generator: https://github.com/moov-io/paygate/blob/36ccd7e2530ec0fd435bbc37f8e3a6fd14c32d83/internal/remoteach/files.go#L146-L152
Example Usage: https://github.com/moov-io/paygate/blob/36ccd7e2530ec0fd435bbc37f8e3a6fd14c32d83/internal/remoteach/ccd.go#L41

This looks fine. Each batch's trace numbers are incremented.
  BatchNumber  Type  ServiceClass  Addendas  TotalDebits  TotalCredits
  1            PPD   200           6         72           72

    TxCode  AccountNumber      Amount  Name                    TraceNumber
    32      729971827          33      Elated Minsky<PHONE_NUMBER>53015
    32      729971827          39      Elated Minsky<PHONE_NUMBER>53016
    27      729971827          72      Elated Minsky<PHONE_NUMBER>53017

  BatchNumber  Type  ServiceClass  Addendas  TotalDebits  TotalCredits
  2            PPD   200           6         50           50

    TxCode  AccountNumber      Amount  Name                    TraceNumber
    32      722071444          20      Clever Meninsky<PHONE_NUMBER>76141
    32      722071444          30      Clever Meninsky<PHONE_NUMBER>76142
    27      722071444          50      Clever Meninsky<PHONE_NUMBER>76143

  BatchNumber  Type  ServiceClass  Addendas  TotalDebits  TotalCredits
  3            PPD   200           6         46           46

    TxCode  AccountNumber      Amount  Name                    TraceNumber
    32      294202992          2       Clever Meninsky<PHONE_NUMBER>87708
    32      294202992          44      Clever Meninsky<PHONE_NUMBER>87709
    27      294202992          46      Clever Meninsky<PHONE_NUMBER>87710


[Security] Selectively bump yarn packages nth-check and set-value

What
Resolve yarn packages security vulnerabilities
Ticket
N/A
Why
See Github's Advisory database related to issues
nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
set-value - https://github.com/advisories/GHSA-4jqc-8m5r-9rpr
How
Selectively bump yarn packages nth-check and set-value

Sanity check on a hosted env before deploying.


Use stack trace to guess if exception was thrown by Pimple

Follow-up to #1663. Maybe this method has caveats, so it needs to be reviewed.
ping @Sam-Burns @mnapoli :)

:+1:

This PR requires a unit test.

Actually this seems to be already tested, in ContainerTest.php see testGetWithDiConfigErrorThrownAsContainerValueNotFoundException whereweareexpoectinga ContainerExpception.

Another side thought, In the unlikely event that someone extends the container and overrides offsetGet this will no longer work.
I don't see why would we would want to change it. What was the point of this PR?

@geggleto The current code relied on string matching which may be more brittle

I thought about a test like is_a($trace['class'], 'Pimple\Container', true), but currently Slim Container "hard extends" Pimple Container and cannot extend a different class.

But someone can extend Container and then implement offsetGet…

Got your point.

If this custom offsetGet makes use of Pimple and the latter throws an exception, it will be detected as well.
If this custom offsetGet throws exceptions by itself, they should be Interop exceptions. Otherwise, there is just no way to properly detect them.


Linguistic operations

Question for the Passau group: Are these appropriate translations?

I have changed this according to http://rhetoric.byu.edu/


Fix location of recursive type parsing depth check

In #646 I accidentally put the check in the wrong function and then
forgot to check it against the original fuzz inputs.

Jeez, I should have caught this too.  Sorry about that.


Add support for faraday 0.10.x

This relaxes the version constraint to allow support for faraday version 0.10.x which was recently released.

bump

Thanks!

We thank you!


Feature: Support Prompt Caching

This PR  supports tracking and logging prompt caching(#1838) metrics in the OpenTelemetry Anthropic instrumentation.
Specifically, it captures and logs the cache_creation_input_tokens and cache_read_input_tokens fields from the API response. This enhancement allows users to monitor the effectiveness of their prompt caching strategy, providing insights into cache utilization and efficiency.
Changes include:

Updated _set_token_usage and _aset_token_usage functions to log caching metrics.
Added new span attributes for cache_creation_input_tokens and cache_read_input_tokens.
Updated streaming.py to support prompt caching metrics in streaming responses.

@kowshik24 note that you still have lint / test errors. LMK once you want me to re-review

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: kowshik24:x: kowshikkowshik seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@nirga @kowshik24 What is the status of the changes here? If this is stale, we are happy to contribute!

Would love for you to contribute @dinmukhamedm! I think @kowshik24 is no longer working on this

@nirga thanks, and sorry about the delayed response. This is requiring a little bit more work with counting tokens (and testing that) than I've expected, and I was out for a day. I'm still on this though


in_app_purchase example update

Example app needs to...

Show how to implement required app store restore button and apply result.
How to parse validation data to check if subscription is still valid in dart.

These two things are all that is preventing me from submitting my flutter app to the apple store.  Tough to get the mindset when information in the read me and the example app seem to disagree on variables and some read me items aren't part of the example.  I've done storekit in ios successfully using SwiftyStorekit when I was IOS only, but this example and read me have left me more confused then when I started.

/cc @mklim

Any news on this subject ?
I also need to implement a verification on subscription state

does any one knows ??????

Any idea when an example will be available? Any pointers in the interim would be very helpful.

Any update on this?


exit with failed code on lock

We rely on the exit code from cronsul to determinate logic after the fact.  Changing the exit code when a lock already exists will help us to determine resultant logic.

I could see this being controlled by a command line flag, but I don't have a strong opinion about the return code in this case, so I'll merge this as-is.


Smoke tests have non-deterministic timing gaps

While tracking down test failures for #4060 @cj-oci and @wanderingbort identified that failures seemed directly related to an unintended and non-deterministic gap in production during certain test scenarios.
logs from CI machine (located here for those with access: https://buildkite.com/EOSIO/eosio/builds/2167 ) indicated that between block 222 and 223 there was an unintentional 7.5 second gap that also corresponds with the loss of a transaction and failure of the test.
The lost transaction is being addressed in another issue.
This issue is to

[ ] identify the source of that unintended gap
[ ] eliminate the cause from the existing scenarios
[ ] author new scenario(s) that explicitly invoke the cause of the gap in order deterministically replicate the failure modes it exercises.

After more digging I think the production gap may be exacerbating the real source of the non-determinism which is whether any node is in a producing mode when it receives the transaction.
If a node receives the transaction while producing (either by RPC or P2P) then the test should pass because it can immediately include it in the block it signs and sends out.
If all nodes receive the transaction while speculating then the test fails because of a bug found as part of #4145
The 7.5 second gap makes it extremely likely that all nodes are "speculating" and therefore there is no way the transaction can arrive on a node while its producing.
So, to make this deterministic we need to simulate the 2 cases explicitly:  ensure that there is a producing node that will receive the transaction (maybe by direct submission) AND ensure that the network has only speculating producers when submitting the transaction (maybe by downing a producer and ensuring we broadcast the tx during the gap)


Using service principal for user creation

Clarified using service principal while creating users does not require @domain.com

@arvindindeed : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@nanditavalsan can you please review this?

Thanks and appreciate your response. Please provide the link (or mention the link in the doc) for " Execute the T-SQL statement create user command “create user [app display name] from external provider”." I'm afraid I couldn't find in this page and customers are asking repeated questions due to this.

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @meenalsri, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#hold-off

@nanditavalsan Is @domain.com needed for users and not needed for Service Principals only?
Are you recommending updating the<EMAIL_ADDRESS>text to [app display name] everywhere in the doc ? or just at the create user step add an additional command like below:
create user [app display name] from external provider

#sign-off

@Jak-MS can you please merge this PR.


enhance documentation

This is comprised of two parts.

README documentation: We should have some more details in the README file that gives more clear information about our project and how to use it.

Source code documentation. PEP 257 defines the standard conventions for source code documentation in python.

Along with the goal of more readable code, some function names should be changed. orinstr(), for example, isn't a great name.

Closed by #21


hardening

How about adding a sandboxed package to enhance security? This software has many dependencies, but I couldn't find any audit details.
Here's the firejail profile that I'm using (just a proof of concept, definitely not the minimal profile):
dbus-system none
ignore dbus-user none
dbus-user filter
dbus-user.talk org.freedesktop.secrets

include electron.profile
include chromium-common-hardened.inc.profile

noblacklist ${HOME}/.config/anytype
whitelist ${HOME}/.config/anytype

I guess a better way is using bubblewrap, but I haven't been able to get it working.
What do you think?

Sounds like a good idea.

If it needs setuid then it's probably not viable for an application like this. Bubblewrap sounds like a better option. I see some packages using it in upstream nixpkgs. (I have not researched this much myself.)


test-backend argument parsing doesn't work with options at end

I've been finding this pretty annoying recently:
(zulip-py3-venv) tabbott@zaset:~/zulip$ test-backend test_decorators --coverage
-- Running tests in serial mode.
Traceback (most recent call last):
  File "/home/tabbott/zulip/tools/test-backend", line 366, in <module>
    failures, failed_tests = test_runner.run_tests(suites, full_suite=full_suite)
  File "/home/tabbott/zulip/zerver/lib/test_runner.py", line 459, in run_tests
    self.test_imports(test_labels, suite)
  File "/home/tabbott/zulip/zerver/lib/test_runner.py", line 435, in test_imports
    check_import_error(test_name)
  File "/home/tabbott/zulip/zerver/lib/test_runner.py", line 362, in check_import_error
    raise exc from exc  # Disable exception chaining in Python 3.
  File "/home/tabbott/zulip/zerver/lib/test_runner.py", line 360, in check_import_error
    __import__(test_name)
ImportError: No module named '--coverage'

@zulipbot claim


Too many signficant digits for latitude and longitude

Right now when you pick an observation location from the map it fills in the latitude and longitude values to 10 decimal places. This is the equivalent of specifying a location to 1/100th of a millimeter. Since you can't actually zoom in that close in the map, and no camera's GPS system is anywhere near that accurate, it would be better to truncate the coordinates to a more reasonable number of decimal places, like 5 or 6. Five decimal places is the equivalent of specifying the location to the exact meter.

Whether or not this is absurd, these are the numbers reported by the devices we use to measure location (phone's positioning system, Google Maps). They may be unrealistically precise, but there's no way for us to know how unrealistically precise.


FileShare snapshot name should be unique

Is this a BUG REPORT or FEATURE REQUEST?:
FileShare snapshot name should be unique

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Hotpot(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

It is fixed in #931, so closing this issue


Self reference in controllers.

Is there a reason why this in controllers and probably in other modules as well references the global window (or sails) object instead of the object itself? For example
module.exports = {

	//Default options
	options: {
		sort: 'desc',
		test: 'base'
	},

	find: function (req, res) {
		console.log(this);
		return res.ok('Test');
	}
}

Prints the window/sails object instead of itself, so there is no way to access this.options

http://stackoverflow.com/questions/23278857/how-can-i-call-a-sails-js-controllers-function-from-another-function-of-the-sam

Hi @Bartinger, this should be fixed in the master branch of Sails; you can try it with npm install sails@beta.


Anime Vintage Effect

Here animefy and 2 supporting functions (KHist and update_C functions) uses K-means algorithm to cluster the histogram of image and generate a non-photo realistic animated rendering of input image giving it an animated effect. Effect is applied on the user provided images resulting in 4 output files (as a result of 1 effect's call). A variety of anime effects can be generated for a single input (so as to demonstrate).
Results are really mesmerizing (by local survey on different images) [added in assets directory].

Greetings Sir,
Please let me know if anything else i can serve here.
tqdm and samples have been added. Please merge the changes if all looks fine to you. That way i can submit my next PR on different effect.
Thank you.

This is awesome!. Could you please update the readme with the same


[Diagnostics] Serialize educational note paths in .dia files

Add a new optional record type which may appear in diag blocks and contains the path to the educational note.
This is a WIP so I can build a toolchain and run some tests. Open questions:

Instead of adding swift-specific record IDs starting at 32, should I try upstreaming a new record ID to clang? My thinking is that clang would have no use for it and might not want to accept swift-specific changes
Does Xcode ignore records with unknown IDs? The Clang SerializedDiagnosticReader does and I'm hoping that's what Xcode uses. I'm going to attempt to test this manually, but it would be great if someone with source access could confirm.
Does this require a format version bump? It looks like it wasn't bumped when remarks were introduced.

@swift-ci please build toolchain macOS platform

macOS Toolchain
Download Toolchain
Git Sha - d9ff76a7cd207fcea5f954f71068d989d3a83f5b
Install command
tar -zxf  swift-PR-30420-491-osx.tar.gz --directory ~/

^ I tried this toolchain out over the weekend and didn't encounter any issues.
@swift-ci please smoke test

cc @xedin / @hborla do you know who has the most context on the .dia file format these days? It looks like it hasn't changed in a long time and I'm not sure I fully understand the implications of making a change like this.

Maybe @tkremenek?

This is going to require a lot more than just changes to Swift. We do not get to define dia as a format, so any changes needs to be upstreamed to LLVM and their version numbers bumped before we can move here.
On the plus side, this change may enable clang to start supporting educational notes!

@CodaFi thanks for confirming, I'll look into upstreaming this.


Ginkgo register tos changes

@stvstnfrd WIP PR for formatting gingko register page
This PR adds a menu of links on each legal page that links to all the other pages so we can use the combined link option that edX has for the register page.

added margin above research paragraph on register page:

This PR adds a menu of links on each legal page that links to all the other pages so we can use the combined link option that edX has for the register page.

@stvstnfrd this has everything addressed, let me know when you want me to squash so you can merge / cherry-pick


docs: fix code examples formatting

included in https://github.com/PiwikPRO/next-piwik-pro/pull/26


Set STOPSIGNAL for SystemD images

This commit updates the SystemD Dockerfiles to use STOPSIGNAL SIGRTMIN+3.
SystemD responds to the default signal sent by docker stop, SIGTERM, by
re-executing a new process instead of shutting down. Sending SIGRTMIN+3
is the proper way to signal SystemD to shut down.
Ref. https://www.freedesktop.org/software/systemd/man/systemd.html#SIGRTMIN+3
Ref. https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/

@Sharpie Thanks for the contribution! :)
We're in the process of automating our image builds, so this will probably be added to the published images after that.


Problem with sortBySelector cssClasses

Hi,
I have a problem on instant search v2, select classes in instantsearch.widgets.sortBySelector doesn't work.
I try
   search.addWidget(       instantsearch.widgets.sortBySelector({         container: '#results-sort',         indices: options.indices,         cssClasses: {            select: 'form-control'         }       })     );
And form-control class is not display.
Please I need help 😩

Thanks @renanbronchart for the issue. I am trying to reproduce the issue 👍

Which version of InstantSearch.js are you using? I've tried with our latest version and it seems to works.

Thanks for response, I use gem algoliasearch-rails for ruby on rails application.
And I use cdn<EMAIL_ADDRESS>for instant search.
Can you show me on example to use select classes in sortBySelector

I saw your example, actually this work at you, but not on my side :/

Do you have a link where I can see the behaviour? Maybe a jsFiddle with your code? That would be very helpful, thanks a lot.

My bad, actually this has been fixed in 2.2.0 with https://github.com/algolia/instantsearch.js/pull/2423
If you upgrade it should be fixed.

Thanks a lot !! It work with 2.2.0 !!


Cannot  install in /usr/lib64 with cmake3/make

Fedora packaging guidelines place .so files /usr/lib64 but the h3 cmake/make do not appear to support LIB_SUFFIX=64.
This is what I have tried but nothing works to put .so file in /usr/lib64.
cmake3 -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_DOCS=YES -DBUILD_SHARED_LIBS=true -DCMAKE_INSTALL_LIBDIR=/usr/lib64 -DLIBRARY_OUTPUT_PATH=/usr/lib64 ..
make %{?_smp_mflags}
make docs
make kml
make install DESTDIR=%{buildroot} LIB_SUFFIX=64 LIB_INSTALL_DIR=/usr/lib64

I have this kludge in my spec file to get around the issue but we really need a supported cmake/make option.
mv %{buildroot}/usr/lib %{buildroot}/usr/lib64

I forked to https://github.com/mrdvt92/h3 and the spec file builds these RPMs.
h3-3.7.1-4.el7.mrdvt92.src.rpm
h3-3.7.1-4.el7.mrdvt92.x86_64.rpm
h3-devel-3.7.1-4.el7.mrdvt92.x86_64.rpm

The Makefile does not have a make dist target so you will have to build a tar ball like this.
git clone https://github.com/mrdvt92/h3.git h3-3.7.1
tar cvfz h3-3.7.1.tar.gz h3-3.7.1/
rpmbuild -ta h3-3.7.1.tar.gz

I think this is because around line 47 in CMakeLists.txt the LIBRARY_OUTPUT_PATH variable is not set to be cached, so each time CMake will take the value in CMakeLists over the one you provide. If it's changed to set(LIBRARY_OUTPUT_PATH lib CACHE STRING "Output library directory") it might help. It may need some more changes around line 684 to use LIBRARY_OUTPUT_PATH there too.

This one line change worked for me. I do not know cmake and so I cannot state how portable this is or if it's even the correct way to handle this issue.
$ git diff CMakeLists.txt
diff --git a/CMakeLists.txt b/CMakeLists.txt
index f6d32f8..1cdab52 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -681,7 +681,7 @@ install(
     TARGETS h3
     EXPORT "${TARGETS_EXPORT_NAME}"
     COMPONENT libh3
-    LIBRARY DESTINATION "lib"
+    LIBRARY DESTINATION "lib${LIB_SUFFIX}"
     ARCHIVE DESTINATION "lib"
     RUNTIME DESTINATION "bin"
     INCLUDES DESTINATION "${include_install_dir}"

Then in the spec file the cmake command is
cmake3 -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_DOCS=YES -DBUILD_SHARED_LIBS=true -DLIB_SUFFIX=64 ..

thanks @kou for fixing this in #819. Please let me know if this does not fix it.


[couchdb] Use lowercase for _byParents child_ids.

I found that when I create a one-to-many relationship using resourceful with user.createPost() it was stored through post_ids, not Post_ids as the couchdb map function assumes.
This wasn't caught in the tests because they create the objects with Article_ids manually (not through resourceful).
So this pull request makes it always lowercase. I've also added tests for this use case.
All tests passes for me.

Changed the couchdb relationship tests to create it's fixtures using resourceful.
This led to another issue found (as the tests tell when they fail):
When calling author.createArticle() it doesn't update author.article_ids with the created id.

@bmeck @slaskis This broke the build: http://travis-ci.org/#!/flatiron/resourceful/builds/367560
Looks like a legitimate complaint from Travis. Any thoughts?

Uhm, sorry I wasn't aware the pull request got updated when I pushed to github...
But yeah I noticed that too. Which is why I added a test (that fails, I never got to getting it to pass) for it in slaskis@2774771


Have you tried it in a Raspberry?

Hi!
Now that you added the ARM version, this project could be deployed on a Raspberry I'm thinking of a Raspberry Pi 4 Model B with 8GB RAM)
Have you tried it? I think it would be a great option to avoid paying AWS or any of these cloud services

Hi!
I haven't tried it.
Cloud providers are not only about CPU and Memory, but also about power, internet connection, handling reboots, so sometimes it worths it :)
Please share you experience with Raspberry PI if you'll make it, it's an interesting idea! :)


change the success message as some opensource models like empower-fun…

change the success message as some opensource models like empower-functions-medium (can be tested with baseUrl: https://app.empower.dev/api/v1/functions/) accepts Tool Message as Json only

Hi,
Thanks for the contribution, but I can't say I really understand this change

Hi,
Thanks for the contribution, but I can't say I really understand this change

There is an exception happening when you try open-source LLMs like empower you get the following exception
log.txt
you could check it out by having this configurations no api-key needed
quarkus.langchain4j.openai.chat-model.model-name=empower-functions-medium
quarkus.langchain4j.openai.base-url=https://app.empower.dev/api/v1/functions/

I will check soon, thanks

@langchain4j does this seems correct to you?

A bit strange (regarding JSON strictness), but if there is such a requirement, what can we do...


Combined shader support

Since layered shader support (see #27) does not work properly, roll back to combined shader support for now. Apply all shaders on the sam texture.

As a preperation I had to patch box2dlights since Version 1.4 does not support lighting in combination with FrameBuffer usage (see https://github.com/libgdx/box2dlights/commit/ee03de49a25808440a86d20860ce1b828f332b22)


ZSH Shell Completion is not working?

I have added into ~/.zshrc
# jira CLI
eval "$(j --completion-script-zsh)"

and j points to jira-linux-amd64
~/Development/tools
➜ ls -la $(which j)
lrwxrwxrwx 1 root root 47 Jun  9 17:52 /usr/local/bin/j -> /home/dmitry/Development/tools/jira-linux-amd64

and this is my ~/.zshrc
Any ideas what is wrong?

If you run the jira --completion-script-zsh above script you will see:
#compdef jira
autoload -U compinit && compinit
autoload -U bashcompinit && bashcompinit

_jira_bash_autocomplete() {
    local cur prev opts base
    COMPREPLY=()
    cur="${COMP_WORDS[COMP_CWORD]}"
    opts=$( ${COMP_WORDS[0]} --completion-bash ${COMP_WORDS[@]:1:$COMP_CWORD} )
    COMPREPLY=( $(compgen -W "${opts}" -- ${cur}) )
    return 0
}
complete -F _jira_bash_autocomplete jira

I think the last line is the relevent line, for autocomplete to work the command name need to be jira.  It will not work with your symlink because j does not trigger the autocomplete.
You can probably just manually copy/paste the above into your .zshrc directly and modify jira to j to get it to work.

@dmitry-saritasa You could also modify your ~/.zshrc and add this line after the eval, so both the jira and j commands get autocomplete:
complete -F _jira_bash_autocomplete j


Write Jupyter notebook for the tensorwaves workflow

The examples/python/workflow.py script already illustrates a complete fit procedure with tensorwaves, but needs to be rewritten into a Jupyter notebook. These notebooks should reflect the ComPWA Workflow. Step 2 of that workflow (generate data) is already as available in tensorwaves (see examples/jupyter/generate.ipynb).

[x] Step 1: Create amplitude model
(can't be done as long as the expertsystem only produces XML).
[x] Step 2: Generate data samples
(existing notebook needs to be renamed into 2_generate_data)
[x] Step 3: Perform fit -- see https://github.com/ComPWA/tensorwaves/issues/68

Closed by #143


Some issue when I setup this component

Hi there,
I have tried to use your component like you used on your examples.
It seems that context.getMap() throw an error.
Do you have some idea of the process to install your component ?

@tomchentw I've been struggling with this component for about everyting I wanted to do and I have found no other solution than to dive into more or less all the Issues and the source code to find little bits of explanations. I admit I'm pretty new to React as well so it hasn't helped.
So yes I absolutely agree : a Getting Started guide would have been deeply appreciated :relieved:


Fix link to ModHeader

For some reason, Mozilla removed ModHeader from their repository. let's delegate addon/ext distribution to the official site of the ModHeader ext (there are links to other browsers)

Thank you for your contribution, @alies-dev


Can't open an old resume [BUG]

Describe the bug
I'm simply just trying to open the resume as per usual.
The last time I opened it from my phone, using Samsung Browser, I didn't edit anything so I doubt that had any effect on it.
Product Flavor

[x] Managed (https://rxresu.me)
[ ] Self Hosted

To Reproduce
Open a resume that's only 7 days old.
Expected behavior
To just open my resume.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Home
Browser Microsoft Edge, I also attempted with Google Chrome with same result.
Version Latest as of 16/10/2022 (DD/MM/YYYY)

Yes, there was a small issue in the last release and had to push a patch overnight. Sorry for the inconvenience. It should be all fixed now. Thank you for raising an issue in time :)


update: shift signup data to mongodb

Once #8 , #6 are solved, update the signup route to store data in MongoDB

Will you please assign this issue to me?


Show incorrectly scoped attribute as an issue

Currently (I think "it's hard to tell without the logs") the SP is dropping scoped attributes that have a scope that differs from that in the IdP's Metadata. Examples include eduPersonPrincipalName and eduPersonScopedAffiliation.
Having the attribute value dropped by the Shibboleth SP the IdP, it is difficult for the IdP admin to diagnose the issue of the missing attributes when their logs are telling them that a value has been sent.
The validator should get the show the value, but highlight as an error if the scope part of the attribute does not match the scope defined for the IdP in the metadata.

Hi @trsau
This behavior of ShibSP is configurable - and is configured in /etc/shibboleth/attribute-policy.xml
You can drop the ScopingRules from the scoped attributes there.  Btw, recent versions (2.6+) also apply rules similar to the scoping rules to the schacHomeOrganization attribute (to make the value match the IdP scope).
And there are also rules that filter all *affiliation attributes to the predefined dictionary.  All meaningful rules, but I'd agree on Attribute Validator, you would want to see the raw values.
You might either make the SP export the raw assertion and extract the original values from there (more work but cleaner), or you might just drop the filtering rules for the attribute validator - would make sense to me.
Cheers,
Vlad

Hi Vlad,
Thanks for highlighting the new rules in 2.6+.
I think the difficult part will be getting the validator application to obtain the scope that the IdP has published in the Federation Metadata.
    <Extensions>
        <shibmd:Scope regexp="false">example.org.com</shibmd:Scope>
    </Extensions>

Once you have that and the values provided by the IdP (i.e. not dropped because their scope does not match) then you can check of issues on all scoped attributes provided and flag appropriately.

You can get the entityID of the IdP from the session information.
You then need to query somewhere to get the IdP metadata based on the entityID - either an MDQuery eg to the SAML Service, or parsing the whole federation metadata file and looking up the IdP by its entityID...
All doable - with an additional external dependency, and a configuration entry to point there...
Cheers,
Vlad


NullReference on .CurrentUser.Username

Discord.WebSocket.DiscordSocketClient.CurrentUser.get returned Nothing.
Same thing happens when i try to take anything from the .CurrentUser.
Is this no longer working? or am i going about it wrongly? This used to work for me.

I am doing it after the client has started, but i believe im trying to access it too quickly.


It can be hard for a non-user to understand what ESMValTool code has been used in a publication (parent issue)

An additional use-case for ESMValTool recipe documentation is a non-user seeking more specifics on the code or methodology underpinning a science publication that used ESMValTool. Without knowledge of how ESMValTool works, it can be hard for them to find the code, or even the recipe documentation.
Following discussions at the June 2023 community workshop, some improvements are proposed:

Link to recipes and diagnostic scripts from recipe doc pages
Add recommendations to advanced tutorial regarding:

good examples of recipe documentation to use as a model for documenting new recipes
good practice on how to document use of ESMValTool in a science publication

Add new ways to find a specific recipe for someone who doesn't have a direct link to the recipe doc page
Make more explicit the expectations for PR science review of methodology description

Would you be able to help out?
Yes.

Looks very good. Thanks @alistairsellar !


Add RISC-V bit manipulation instruction 'bext'.

'bext' instructions implement the generic bit extract .
funct7 | rs2 | rs1 | f3 | rd | opcode
0110000 | rs2 | rs1 | 110| rd | 0110011

Please address compilation errors

Closing since there is no update within 7 days


Misc fixes and enhancements

Hi,
This is my first contribution to flatcc, so please let me know if something is missing or must be done differently (either patches or process).
This series contain 4 commits:

The first 2 commits are fixes (one in json parser and the other in code generation of file identifiers)
The 3rd one aligns file extensions definition to file identifiers
The last one is an enhancement of bfbs2json to dump documentation

Thanks!
Olivier

Hi Olivier, thanks for contributing.
I think you should keep the bfbs in as a separate PR. If you want to generate documentation, you should also make sure it is added. I don't think that is the case currently (The reflection schema has changed over time). https://github.com/dvidelabs/flatcc/blob/master/src/compiler/codegen_schema.c
As to file_identifier. This was made such that you could include a file and always know what the file identifier was without making the code specific to one table name. The table name specific file identifiers inherit from the schemas file_identifier which is helpful in cases where mulitple files are included, but generally it inherits from the schema file and should be working correctly as is, so I am no inclided to make the suggested change for no apparent reason.
I'm happy to add file_extension if that was missing. The identifier and extension without the 'file_' prefix should be avoided because it creates name conflicts with users adding field names like "identifier". I believe the deprecated _identifier is still present but should be removed after next release.

I should add that if you add file_extension, it should be done the same way as file_identifier obviously so not the way you are currently doing it, unless you have a good argument for doing so.

As to the README, you can add the file_identifer assignment and "..." before the table the specific name in the README to improve documentation.

I think you are correct about the JSON parser end_loc fix. That should also be a separate PR.
For you information (and is I recall), generally any sub-parser either returns input location if it cannot proceed with a match, or end location if it finds an error, or the end for input parsed so far if input is successfully consumed. Therefore there can be cases where a parser chooses not to return the input of a sub-parser it calls, especially if there might be other alternatives to explore by the calling the parser. However, I do not think that is applicable here. I think I simply forget to assign the buffer, but the reason why might relate to the above.

No, the 'end_loc' should not be assigned there. The parse_as_root is still an intermidate parser.
This is the generated top-level monster parser you can find in build/Debug/json_test/generated:
static int monster_test_parse_json(flatcc_builder_t *B, flatcc_json_parser_t *ctx,
        const char *buf, size_t bufsiz, int flags)
{
    flatcc_json_parser_t parser;
    flatcc_builder_ref_t root;

    ctx = ctx ? ctx : &parser;
    flatcc_json_parser_init(ctx, B, buf, buf + bufsiz, flags);
    if (flatcc_builder_start_buffer(B, "MONS", 0, 0)) return -1;
    MyGame_Example_Monster_parse_json_table(ctx, buf, buf + bufsiz, &root);
    if (ctx->error) {
        return ctx->error;
    }
    if (!flatcc_builder_end_buffer(B, root)) return -1;
    ctx->end_loc = buf;
    return 0;
}

Sorry, I take that back. I think it is reasonable to have end_loc assigned as you suggest. The generated code was problably added before the as_root function.

I think you should keep the bfbs in as a separate PR. If you want to generate documentation, you should also make sure it is added. I don't think that is the case currently (The reflection schema has changed over time). https://github.com/dvidelabs/flatcc/blob/master/src/compiler/codegen_schema.c

Indeed, the documentation is not added in the binary schema by flatcc. I used flatc to generate it (as specified in the commit log). To give more context about why I did this change: I'm thinking about doing an interactive cli to send/recv rpc using flatbuffers, and interactive help would be generated from the schema documentation. So I just wanted to check that documentation is "introspectable", and that's why I modified bfbs2json.
As you suggest, I'll later do a separated PR for this if I also change the binary schema generator.

As to file_identifier. This was made such that you could include a file and always know what the file identifier was without making the code specific to one table name. The table name specific file identifiers inherit from the schemas file_identifier which is helpful in cases where mulitple files are included, but generally it inherits from the schema file and should be working correctly as is, so I am no inclided to make the suggested change for no apparent reason.

The problem I see currently is when I have 2 schema files, which have different file identifiers. If in my code I do:
#include <schema1_reader.h>
#include <schema2_reader.h>

It will result in the following code:
  // from schema1_reader.h
  #undef flatbuffers_identifier
  #define flatbuffers_identifier "SCH1"

  #ifndef Schema1_Table_file_identifier
  #define Schema1_Table_file_identifier flatbuffers_identifier
  #endif

  // from schema2_reader.h
  #undef flatbuffers_identifier
  #define flatbuffers_identifier "SCH2"

  #ifndef Schema2_Table_file_identifier
  #define Schema2_Table_file_identifier flatbuffers_identifier
  #endif

If later in my code, I use Schema1_Table_file_identifier, it will be defined to "SCH2", which is not expected.

I'm happy to add file_extension if that was missing. The identifier and extension without the 'file_' prefix should be avoided because it creates name conflicts with users adding field names like "identifier". I believe the deprecated _identifier is still present but should be removed after next release.

OK, will do. It looks only the documentation has to be modified in my commit, or did I miss something?

I should add that if you add file_extension, it should be done the same way as file_identifier obviously so not the way you are currently doing it, unless you have a good argument for doing so.

I suppose you are talking about using flatbuffers_extension` vs using the string directly, right?

If later in my code, I use Schema1_Table_file_identifier, it will be defined to "SCH2", which is not expected.

No that is not how it was intended. Getting time of macro resolution right is notoriously hard and apparently I got it wrong here. Usually I work with double macro wrappers to deal with this, but in this case it may be better to just do as you suggest.
If you are aware of any other places where there might be such a problem, please let me know.

About the json parser fix, I'll do a separated PR as you suggest.
Thank you for the quick feedback on all the patches.

I suppose you are talking about using flatbuffers_extension` vs using the string directly, right?

I was referring to you adding an entirely new function static void print_file_extension(fb_output_t *out, fb_compound_type_t *ct) suggesting I must have missed something.
both file_extension and <name>_file_extension should be defined similar to file_identifier, while <name>_extension should be avoided if not already there.

Please note that the bfbs2json is just an example and that generating output to JSON should normally use the json printer instead. There was a similar discussion on generating and printing RPC data in a recent PR. Still it is fine to improve bfbs2json as long the the bfbs export is also there.

I suppose you are talking about using flatbuffers_extension` vs using the string directly, right?

I was referring to you adding an entirely new function static void print_file_extension(fb_output_t *out, fb_compound_type_t *ct) suggesting I must have missed something.
both file_extension and <name>_file_extension should be defined similar to file_identifier, while <name>_extension should be avoided if not already there.

Sorry, I'm not sure I'm getting your point.
In v2, I'm planning to:

keep the new print_file_extension() function as is (do not add _extension because it does not exist currently)
fix the README: _extension -> file_extension

Is it what you expect?

Is it what you expect?

Yeah, I haven't studied all the code super carefully yet.

Close this PR, it has been split in #186 and #187. The changes related to bfbs2json may come later in a separate PR.


Add ZooKeeper pack with non_blocking_lease action

ZooKeeper
Status

new pack, minimally complete

Description
Pack which allows integration with Apache ZooKeeper.
Checklist (tick everything that applies)

[x] Metadata: pack.yaml, icon, structure (required for new packs)
[ ] Version bump (required for changed packs)
[ ] Code linting (required, can be done after the PR checks)
[ ] Tests (not required but really recommended)

Nice, thanks. :+1:
Will review it as soon as possible.

Nice!


Remove unneeded Container() interface

It's wired that Container() interface is duplicated with Containers().Get(), this will fix that.
Signed-off-by: Harry Zhang<EMAIL_ADDRESS>

what.. what purpose on the Container() interface? anyone can input some advise?


Changing random to seconds since epoch to prevent BQ job name colliss…

…ions
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

 Thanks.

LGTM. Thanks.

Run Python 3.8 PostCommit

Run Python 3.8 PostCommit

Is there a Jira I can reference?

Found this by reading code and history trying to answer https://stackoverflow.com/questions/66240753/dataflow-jobs-launching-bigquery-jobs-failing-intermittently-with-error-errors.
I claimed that this PR should fix their problem. Please LMK or response there if you think it is a different problem.

that's correct Kenn. Thanks!


gRPC DNS resolution doesn't seem to work

It seems that in the current version that gRPC DNS resolution is broken. As far as I can tell this is an issue with gRPC and not chirpstack as everything works fine if you use IP addresses.
I've filed an issue against gRPC for this.
https://github.com/grpc/grpc-go/issues/3572
Wanted to file this here for FYI for others and to track updating gRPC once the issue is resolved over there.

I am seeing this a lot in production now. It usually happens when there is a node count change in Kubernetes and pods get shuffled around. Frequently, the ChirpStack containers (NS or AS) never update to the new DNS for their self-ingress/services (those that they use to connect to each other via gRPC), no matter how long they are running.
The immediate fix is to kill them, and let them restart with new DNS successfully being picked up. As a workaround, we've raised their priority to minimize pod shuffling, but even that isn't a complete fix.
I don't recall when this started, but I noticed it a lot more in the past couple releases. Historically, ChirpStack pods were our most reliable when it came to reconnection logic, and now it seems we need to manually intervene any time there is a topology change.
@brocaar Any thoughts on gRPC and DNS? Or if this gRPC at all?

Sorry not too familiar with Kubernetes, so not sure how to relate this to a Docker-compose setup.
From what I'm experiencing DNS seems to be working and updating just fine. Chirpstack AS and NS both connect to and communicate with redis, postgresql and mosquitto just fine. It's only the gRPC comms between NS and AS that fail. When I assign static IPs to the containers and use the IPs for NA and AS everything works perfectly. And I know the docker DNS proxy is updating correctly as I've been able to check using nslookup within the AS and NS containers.
As for killing and restarting, I'm not sure if you're talking about restarting the container or going and killing the process in the container. But no matter how I have tried to restart the container (restart or down/up) the same issues happens. I did not try killing the AS or NS process itself within the container though. However, since redis, postgresql, and mosquitto all seem to work perfectly fine throughout and gRPC is the only thing with an issue, I think this suggests that gRPC has an underlying issue with it's DNS resolution code.

We're seeing the same issues when running in docker-compose

It could be that this is related to this change: https://github.com/brocaar/chirpstack-network-server/commit/1d20dbb85f07c79ccffcd2899347605e6fa31eee ?
This was introduced to support DNS based load-balancing.
	dialOptions := []grpc.DialOption{
		grpc.WithBalancerName(roundrobin.Name),
	}

Is there to enable roundrobin load-balancing.
	// the default is passthrough, see:
	// https://github.com/grpc/grpc-go/issues/1783
	resolver.SetDefaultScheme("dns")

Is there to make sure the documented default scheme is used. The default in Go is passthrough, but the documented default is dns:

The URI scheme indicates what resolver plugin to use. If no scheme prefix is specified or the scheme is unknown, the dns scheme is used by default.

https://github.com/grpc/grpc/blob/master/doc/naming.md#name-syntax
There was a TXT related issue to this change, but this has been fixed in the latest gRPC version and has been updated in the ChirpStack NS and AS.: https://github.com/brocaar/chirpstack-application-server/issues/426.

General questions to all of you:
Please report the exact error you are seeing
I assume this is?
chirpstack-network-server_1 | time="2020-04-27T05:06:18Z" level=warning msg="creating insecure application-server client" server="chirpstack-application-server:8001"
chirpstack-network-server_1 | time="2020-04-27T05:06:23Z" level=warning msg="ccResolverWrapper: reporting error to cc: dns: A record lookup error: lookup chirpstack-application-server on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: operation was canceled"
chirpstack-network-server_1 | time="2020-04-27T05:06:23Z" level=error msg="gateway: handle gateway stats error" ctx_id=68623603-d2d2-4f2c-a6e4-34f56eae1dad error="get application-server client error: get application-server client error: create application-server api client error: dial application-server api error: context deadline exceeded"

That way I don't have to make any assumptions what "same issue" means :-)
Please report the exact versions that you are using
When the ChirpStack components start, they will print the version to the logs. Using the latest chirpstack-docker doesn't mean you are using the latest ChirpStack components as Docker images and containers are cached.
Knowing the exact versions is quite helpful ;-)

Running chirpstack versions.
chirpstack-application-server_1  | time="2020-04-27T06:12:55Z" level=info msg="starting ChirpStack Application Server" docs="https://www.chirpstack.io/" version=3.10.0

chirpstack-network-server_1      | time="2020-04-27T06:12:50Z" level=info msg="starting ChirpStack Network Server" band=US915 docs="https://www.chirpstack.io/" net_id=ca571e version=3.9.0

hmm, could be related to the roundrobin, but still sounds like a bug in gRPC as it should still work if there is only a single address provided from DNS.

I just did a test with the application server and removed the load balancer line and I got the same error as before, so not sure it's related to the load balancer.
Line removed:
internal/backend/networkserver/networkserver.go:
112:             grpc.WithBalancerName(roundrobin.Name),

For anyone not following along on the grpc-go issue. I've pulled together some sample code that reproduces most of the original issue. You can find the code here:
https://github.com/evil-dog/grpc-go-issue-3572-repro

I've the same problem on the docker-compose unfortunately

Hi
Any way around  this?
This is my config
`version: "3"
services:
chirpstack-network-server:
image: chirpstack/chirpstack-network-server:latest
# environment:
#   - POSTGRESQL__DSN=postgres://chirpstack_ns:chirpstack_ns@postgresql/chirpstack_ns?sslmode=disable
#   - REDIS__URL=redis://redis:6379
#   - NETWORK_SERVER__BAND__NAME=EU868
#   - NETWORK_SERVER__GATEWAY__BACKEND__MQTT__SERVER=tcp://mosquitto:1883
#   - JOIN_SERVER__DEFAULT__SERVER=http://<IP_ADDRESS>:8003
#   - GEOLOCATION_SERVER__SERVER=<IP_ADDRESS>:8005
# ports:
#   - 8000:8000
volumes:
- ./configuration/chirpstack-network-server:/etc/chirpstack-network-server
networks:
default:
ipv4_address: <IP_ADDRESS>
chirpstack-application-server:
image: chirpstack/chirpstack-application-server:latest
# environment:
#   - POSTGRESQL__DSN=postgres://chirpstack_as:chirpstack_as@postgresql/chirpstack_as?sslmode=disable
#   - REDIS__URL=redis://redis:6379
#   - APPLICATION_SERVER__INTEGRATION__MQTT__SERVER=tcp://mosquitto:1883
#   - APPLICATION_SERVER__API__PUBLIC_HOST=<IP_ADDRESS>:8001
#   - APPLICATION_SERVER__EXTERNAL_API__JWT_SECRET=verysecret
volumes:
- ./configuration/chirpstack-application-server:/etc/chirpstack-application-server
ports:
- 8080:8080
networks:
default:
ipv4_address: <IP_ADDRESS>
chirpstack-gateway-bridge:
image: chirpstack/chirpstack-gateway-bridge:latest
ports:
- 1700:1700/udp
# environment:
#   - INTEGRATION__MQTT__AUTH__GENERIC__SERVERS=tcp://mosquitto:1883
volumes:
- ./configuration/chirpstack-gateway-bridge:/etc/chirpstack-gateway-bridge
networks:
default:
ipv4_address: <IP_ADDRESS>
chirpstack-geolocation-server:
image: chirpstack/chirpstack-geolocation-server:latest
# environment:
#   - GEO_SERVER__BACKEND__NAME=collos
volumes:
- ./configuration/chirpstack-geolocation-server:/etc/chirpstack-geolocation-server
networks:
default:
ipv4_address: <IP_ADDRESS>
postgresql:
image: postgres:latest
environment:
- POSTGRES_PASSWORD=root
volumes:
- ./configuration/postgresql/initdb:/docker-entrypoint-initdb.d
- ./data/postgresql:/var/lib/postgresql/data
networks:
default:
ipv4_address: <IP_ADDRESS>
redis:
image: redis:latest
volumes:
- ./data/redis:/data
networks:
default:
ipv4_address: <IP_ADDRESS>
mosquitto:
image: eclipse-mosquitto:latest
ports:
- 1883:1883
networks:
default:
ipv4_address: <IP_ADDRESS>
networks:
default:
ipam:
driver: default
config:
- subnet: <IP_ADDRESS>/16
`
I tried using the fixed IP, then I get the network server added on to the application server, but when it wants to register the gateway
`time="2020-08-25T09:01:17Z" level=info msg="gateway/mqtt: gateway stats packet received" gateway_id=XXXXXXXXXXXX stats_id=2fc6221f-f9ea-421b-aaf8-42fb10ea4bfc
time="2020-08-25T09:01:17Z" level=info msg="gateway updated" ctx_id=2fc6221f-f9ea-421b-aaf8-42fb10ea4bfc gateway_id=XXXXXXXXXXXX
time="2020-08-25T09:01:17Z" level=warning msg="creating insecure application-server client" server="chirpstack-application-server:8001"
time="2020-08-25T09:01:22Z" level=warning msg="ccResolverWrapper: reporting error to cc: dns: A record lookup error: lookup chirpstack-application-server on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: operation was canceled"
time="2020-08-25T09:01:22Z" level=error msg="gateway: handle gateway stats error" ctx_id=2fc6221f-f9ea-421b-aaf8-42fb10ea4bfc error="get application-server client error: get application-server client error: create application-server api client error: dial application-server api error: context deadline exceeded"`
I don't understand why it keep looking for chirpstack-application-server:8001 I already change it in the conf files and also on the env variables but I cannot find a way to set up the fix IP for this.
Any help would be appreciated, I added it here as I thought is related to the issue but let me know if I have to open a new one
Thanks

Same problem here, any suggestions on getting the docker compose to work?
chirpstack-application-server_1  | time="2020-09-21T17:41:45Z" level=warning msg="creating insecure network-server client" server="chirpstack-network-server:8000 "
chirpstack-application-server_1  | time="2020-09-21T17:41:50Z" level=warning msg="ccResolverWrapper: reporting error to cc: dns: A record lookup error: lookup chirpstack-network-server on <IP_ADDRESS>:53: dial udp <IP_ADDRESS>:53: operation was canceled"
chirpstack-application-server_1  | time="2020-09-21T17:41:50Z" level=error msg="finished unary call with code Unknown" ctx_id=f5a614f6-5402-4f2a-bcb3-5efcdfd9379f error="rpc error: code = Unknown desc = context deadline exceeded" grpc.code=Unknown grpc.method=Create grpc.service=api.NetworkServerService grpc.start_time="2020-09-21T17:41:45Z" grpc.time_ms=5028.882 peer.address="<IP_ADDRESS>:58598" span.kind=server system=grpc

My quick fix solution was to set up an ubuntu vm and follow the directions here, it went faster and smoother than the docker compose:
https://www.chirpstack.io/project/guides/debian-ubuntu/

I have been looking at this again, and potentially this issue might have been introduced after this line which has been added to all components:
resolver.SetDefaultScheme("dns")

I'm going to change this into a configuration option which can be enabled to see if this solves the issue.

If your host has static IP you can work around this bug by using it instead of application server hostname. Besides changing the value in config file I needed to change it in postgres database chirpstack_ns, table routing_profile. Then just add port 8001 and 8803 to docker-compose.yml
  chirpstack-application-server:     image: chirpstack/chirpstack-application-server:latest     ports:       - 8080:8080       - 8001:8001       - 8003:8003     volumes:       - ./configuration/chirpstack-application-server:/etc/chirpstack-application-server
If for any reason you dont want to expose these ports to the public, you can make virtual network adapter with private ip and then use its ip in config files and when exposing ports: https://docs.docker.com/compose/compose-file/#ports

Do you still experience this issue with the latest ChirpStack components? The change I proposed on Oct. 16 is already part of the latest versions. Else I will close this issue.

Hi brocar all working ok now, I'll close the issue.  This issue seems to not be occuring in the current Chirpstack version.

Thanks for confirming @evil-dog. I'll close this issue.

@brocaar
I'm still facing this issue
<_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "DNS resolution failed for https://nnxx.com/: C-ares status is not ARES_SUCCESS qtype=AAAA name=https is_balancer=0: Domain name not found"
        debug_error_string = "UNKNOWN:DNS resolution failed for https://nnxx.com/: C-ares status is not ARES_SUCCESS qtype=AAAA name=https is_balancer=0: Domain name not found {created_time:"2024-03-11T09:45:20.354939546+00:00", grpc_status:14}"
>
ERROR:root:GRPC Exception:  DNS resolution failed for https://nnxx.com/: C-ares status is not ARES_SUCCESS qtype=AAAA name=https is_balancer=0: Domain name not found

My code
BASE_URL = "https://nnxx.com"  # opens chirpstack v4 UI
channel = grpc.insecure_channel(BASE_URL)
device_stub = api.device_pb2_grpc.DeviceServiceStub(channel)


Building a Vite project with @vue/devtools imported causes Vite to try and bundle the node version

Vue devtools version
6.5.0
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-ptp8ed?file=log.txt
Steps to reproduce & screenshots

npm run build the reproduction, or check the saved log.txt

What is expected?
A browser build using Vite shouldn't try to bundle a Node version of @vue/devtools
What is actually happening?
It tries to bundle the Node version. This even fails in some setups with errors such as:
[commonjs--resolver] Failed to resolve entry for package "fs". The package may have incorrect main/module/exports specified in its package.json.
file: /Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/@vue+devtools<EMAIL_ADDRESS>error during build:
Error: Failed to resolve entry for package "fs". The package may have incorrect main/module/exports specified in its package.json.
    at packageEntryFailure (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/vite@4.4.8_@types+node@18.17.1/node_modules/vite/dist/node/chunks/dep-75f53616.js:28687:11)
    at resolvePackageEntry (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/vite@4.4.8_@types+node@18.17.1/node_modules/vite/dist/node/chunks/dep-75f53616.js:28684:5)
    at tryNodeResolve (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/vite@4.4.8_@types+node@18.17.1/node_modules/vite/dist/node/chunks/dep-75f53616.js:28415:20)
    at Object.resolveId (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/vite@4.4.8_@types+node@18.17.1/node_modules/vite/dist/node/chunks/dep-75f53616.js:28176:28)
    at file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/rollup@3.27.1/node_modules/rollup/dist/es/shared/node-entry.js:25416:40
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processImmediate (node:internal/timers:447:9)
    at async PluginDriver.hookFirstAndGetPlugin (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/rollup@3.27.1/node_modules/rollup/dist/es/shared/node-entry.js:25316:28)
    at async resolveId (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/rollup@3.27.1/node_modules/rollup/dist/es/shared/node-entry.js:23991:26)
    at async ModuleLoader.resolveId (file:///Users/segevfiner/prj/swimm-tech-debt/node_modules/.pnpm/rollup@3.27.1/node_modules/rollup/dist/es/shared/node-entry.js:24405:15)
 ELIFECYCLE  Command failed with exit code 1.
 ELIFECYCLE  Command failed.

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.6.10 - /usr/local/bin/pnpm
  npmPackages:
    vue: ^3.3.4 => 3.3.4

Any additional comments?
This is caused by the dynamic code to figure out if running in browser or node done in index.js this package should migrate to package.json exports instead which Vite can understand.

Somehow the side effect of modules should be removed.

https://stackblitz.com/edit/vitejs-vite-ptp8ed?file=log.txt

↑ In this reproduction, the devtools is tree-shaked. the console's log output is not always reliable.
You can check the dependency map.

Yes. It should be. But something in my project caused it to not be tree shaken when I updated Vite/esbuild past a certain version...


Travis bundle size much bigger

Travis fails every time because bundle size is bigger than local
Local:
File sizes after gzip:
  275.76 KB  build/static/js/bundle.1547240c.js
  3.32 KB    build/static/css/bundle.4d67a76b.css

Travis:
Failed to compile.
asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  static/js/bundle.a3f3a1f8.js (998 KiB)
entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  client (1020 KiB)
      static/css/bundle.4d67a76b.css
      static/js/bundle.a3f3a1f8.js

See https://github.com/jaredpalmer/razzle/issues/671

Thanks for the reply @dguo i already moved to Next


Not Authorized to access listEntries on type Query - Can't run amplify mock function

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.2.3
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I've been trying to run the amplify mock function command in VS code so that I can test a lambda function I'm creating without having to deploy it each time. I created this function using the add option so roles etc. have been autogenerated. I'm building a flutter app so i can't do the amplify codegen, only amplify codegen models, if that makes any difference.
I'm getting the following error:
"statusCode": 400,
  "body": "{\"data\":{\"listUserEntries\":null},\"errors\":[{\"path\":[\"listUserEntries\"],\"data\":null,\"errorType\":\"Unauthorized\",\"errorInfo\":null,\"locations\":[{\"line\":3,\"column\":3,\"sourceName\":null}],\"message\":\"Not Authorized to access listUserEntries on type Query\"}]}"

I've seen several threads on GitHub talking about this issue, which suggest I redeploy my schema file to update the resolvers and prevent this from happening, but those aren't working. I've also tried amplify api gql-compile
If I look in the resolver for this type, i can see the authorisation for cognito and api key but not IAM. I have IAM configuration defined as an additional option through the update api command. I've checked in cloudformation to see what roles amplify creates to execute lambdas, and i've also added those to my local access. Still getting unauthorized. Please help, I don't want this error message to haunt my dreams anymore.
type UserEntry
  @model
  @auth(
    rules: [
      { allow: owner, operations: [read, update, create] }
      { allow: private, provider: userPools,  operations: [create]}
      { allow: private, provider: iam, operations: [read, create, update]}
    ] .....

{
  "version": 1,
  "serviceConfiguration": {
    "apiName": "xxxxxxxx",
    "serviceName": "AppSync",
    "defaultAuthType": {
      "mode": "AMAZON_COGNITO_USER_POOLS",
      "cognitoUserPoolId": "xxxxxxxxxx"
    },
    "conflictResolution": {},
    "additionalAuthTypes": [
      {
        "mode": "API_KEY",
        "expirationTime": 7,
        "apiKeyExpirationDate": "2023-08-10T19:12:13.872Z",
        "keyDescription": ""
      },
      {
        "mode": "AWS_IAM"
      }
    ]
  }
}

## [Start] Authorization Steps. **
$util.qr($ctx.stash.put("hasAuth", true))
#set( $isAuthorized = false )
#set( $primaryFieldMap = {} )
#if( $util.authType() == "API Key Authorization" )

#end
#if( $util.authType() == "User Pool Authorization" )
  #if( !$isAuthorized )
    #set( $authFilter = [] )
    #set( $ownerClaim0 = $util.defaultIfNull($ctx.identity.claims.get("sub"), null) )
    #set( $currentClaim1 = $util.defaultIfNull($ctx.identity.claims.get("username"), $util.defaultIfNull($ctx.identity.claims.get("cognito:username"), null)) )
    #if( !$util.isNull($ownerClaim0) && !$util.isNull($currentClaim1) )
      #set( $ownerClaim0 = "$ownerClaim0::$currentClaim1" )
      #if( !$util.isNull($ownerClaim0) )
        $util.qr($authFilter.add({"owner": { "eq": $ownerClaim0 }}))
      #end
    #end
    #set( $role0_0 = $util.defaultIfNull($ctx.identity.claims.get("sub"), null) )
    #if( !$util.isNull($role0_0) )
      $util.qr($authFilter.add({"owner": { "eq": $role0_0 }}))
    #end
    #set( $role0_1 = $util.defaultIfNull($ctx.identity.claims.get("username"), $util.defaultIfNull($ctx.identity.claims.get("cognito:username"), null)) )
    #if( !$util.isNull($role0_1) )
      $util.qr($authFilter.add({"owner": { "eq": $role0_1 }}))
    #end
    #if( !$authFilter.isEmpty() )
      $util.qr($ctx.stash.put("authFilter", { "or": $authFilter }))
    #end
  #end
#end
#if( !$isAuthorized && $util.isNull($ctx.stash.authFilter) )
$util.unauthorized()
#end
$util.toJson({"version":"2018-05-29","payload":{}})
## [End] Authorization Steps. **

Expected behavior
It authorises!
Reproduction steps

amplify add function
amplify push
adjust schema, amplify push
amplify mock function x
mock should authorize.

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

not using function option anymore.

Can anyone give insight into this? I'm experiencing the same exact problem.


Build error for python-pygobject

Hi,
I have added meta-gir/meta-gir in bblayer.conf
and tried to build girepository using bitbake libgirepository but it is
throwing error due to g-ir-scanner.py bad interpreter: No such file or directory
I have tested on Yocto jetro 2.0 branch. will it only work with QEMU??
Is it a know issue?? or any other configuration required ??
Please let me know answer

i'll test it in jethro branch laster. Thanks for your report.

Hi,
just leaved an issue... I had the same issue it seems to be related to the length of the "hash-bang" ("#!/bin/...etc), if it exceeds 128 bytes it cannot be launched. So to get it work you just have to build it again in a new directory with shorter absolute path...
Aurele


ActiveModel::RangeError (35693 is out of range for ActiveModel::Type::Integer with limit 2 bytes)

I have a really long article with a "body" field that is fuzzily searchable. At some point it starts taking a long time for fuzzily to re-index / update the search trigrams for the article when I click "update" on my web form and it does the article.save! in my rails application.
Eventually it crashes with this error!
Trigram Exists (0.7ms)  SELECT  1 AS one FROM "trigrams" WHERE "trigrams"."trigram" = $1 AND "trigrams"."owner_type" = $2 AND "trigrams"."owner_id" = $3 AND "trigrams"."fuzzy_field" = $4 LIMIT $5  [["trigram", "**<"], ["owner_type", "Article"], ["owner_id", 1094], ["fuzzy_field", "body"], ["LIMIT", 1]]
App 11471 output:    (0.5ms)  ROLLBACK
App 11471 output: Completed 500 Internal Server Error in 517ms (ActiveRecord: 84.7ms)
App 11471 output:
App 11471 output: ActiveModel::RangeError (35693 is out of range for ActiveModel::Type::Integer with limit 2 bytes):

This is bad. I believe it's because the trigram "score" is really high and because of this line:
t.integer "score", limit: 2

Specifically I think it's because it's an article with a lot of html symbols and it seems to be searching for a trigram on "**<" which is a little odd, but ok.
In the trigrams migration. I need this limit to be higher I guess. removing the 2-byte limit with a migration, date_update_trigrams_score.rb ...
class UpdateTrigramsScore < ActiveRecord::Migration[5.2]
  # allow higher fuzzily scores for long searchable article bodies...
  def change
    change_column :trigrams, :score, :integer
  end
end

and my problem is resolved. So, maybe 2 bytes is a little too low for normal usage on the trigrams score?

I think I will just have to disable trigram search on the body field of my articles, as it indexes way too many items, takes too long, when the articles are more than a page or two long. I want to be able to put whole novels into my article bodies, so maybe trigram search just isn't the right tool for searching the bodies of the articles, or really long texts in general...


External Source Dependencies (Phase 1)

Context
With this initial implementation of Phase 1 of the External Source Dependencies feature, users can specify a mapping from maven group:artifactId to the version control system which contains the sources for that artifact. During the build, when any version of that dependency is resolved, the source code is cloned locally and built instead of using the dependency from a binary repository.
Caveats

Only git repositories are supported
Only the default branch for the git repository can be cloned
The source code must be built with a Gradle build
This breaks build scans for projects which use the feature
There is no locking of the working directory (it's not thread-safe yet) gradle/gradle-native#146
The clone operations are not done very efficiently gradle/gradle-native#148
There is no support for build operations yet gradle/gradle-native#147

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation including proper use of @since and @Incubating annotations for all public APIs

Will we need someone from Cloud Services team to look into build scan support for this feature? If yes we should let them know in advance so they can plan this work.

@pioterj, I don't think so. I think that @big-guy should have good enough of an understanding of what he and @bigdaz did to get composite builds working with build scans to fix it.

Something that will be missing from scans is visibility into why a build happened to be included or not. For an explicitly included build this is less of a problem as this tends to be hard-coded in the settings.gradle so is a bit more obvious. Not necessarily something we should prioritise now, just something to consider.

@eljobe how can I most efficiently learn about how we intend for these builds to integrate? For example, do/will they share the same task graph and build operation tree?
With the work we are doing for composite build support right now, it makes sense for us to have an eye on this.

@ldaley the implicitly included builds will look pretty much the same as the explicitly included builds. There'll be some differences between when the explicitly and implicitly included builds are discovered. The explicitly included builds will be known about at the end of the settings execution, implicitly included builds will be discovered during the task graph calculation and possibly also during execution, if we decide we want to go there.

@eljobe the diff is pretty ugly.  Ive tried to pull the different compositr build related types into a new IncludedBuildRegistry. There are still some weird things (and synchronization issues) that make this more complicated than I like.
But the internet connection is oit so im taking that as my cue to sleep.  Please take a look and we can chat in my morning.

This version of the branch, doesn't actually work. When I try it with the
skrimple project I used in our demo video, it doesn't pick up the
skramplitude dependency from the head of master, even when I set the
version of the dependency to latest.inegration. ;(
On Tue, Oct 3, 2017 at 10:27 AM Pepper Lebeck-Jobe<EMAIL_ADDRESS>wrote:

@eljobe commented on this pull request.
In subprojects/core-api/src/main/java/org/gradle/vcs/VersionRef.java
https://github.com/gradle/gradle/pull/2978#discussion_r142337475:

@@ -19,21 +19,12 @@
import org.gradle.api.Incubating;

/**
I think you've reverted some of the changes from master to this class.
In
subprojects/version-control/src/main/java/org/gradle/vcs/git/internal/DefaultGitVersionControlSpec.java
https://github.com/gradle/gradle/pull/2978#discussion_r142339116:

@@ -52,7 +51,7 @@ public String getDisplayName() {

 @Override
 public String getUniqueId() {

   return Hashing.md5().hashString(getDisplayName()).toString();

   return getUrl().toASCIIString();

I thought we wanted the implementation to be unique across version control
systems? What if you could have both a GitVersionControlSystem and
SimpleVersionControlSystem based on some local directory? We'd have a
clash, no?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gradle/gradle/pull/2978#pullrequestreview-66682078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApf9LG57WAee8kytvqlf2qEkXf8022Pks5soe_mgaJpZM4PdYR6
.


How to calculate MF-Value (eq(10)) in MF-AC/MF-Q

Hi, recently I am trying to reproduce your work and feel a little confused when implementing MF-AC. According to the algorithm at somewhere the MF-Value (10) should be calculated, where it seems it involves many computations to enumerate all possible mean-field actions and their probabilities. I took a look at you MF-AC implementation in battle-game, but it appears to me (please correct me if i am wrong) here the MF-values are substituted with the returns from the sampled trajectory? Could you explain more about how to calculate the MF-value eq(10), for both MF-AC and MF-Q? Thanks

It just occurred to me that the sampled trajectory is an unbiased estimator of the MF-Value? It works for REINFORCE-like AC. But still confused how to calculated for off-policy RL like MF-Q?


linebreak style breaks with default line endings on Windows

Since several students (I think primarily in London) are using Windows/WSL, they have CRLF line endings by default in VSCode.
This came up during the React class, as the lint rules are applied via the CRA template.
IMO enforcing consistent line endings is good for the final projects, since the code will need to be run on multiple machines. However for the React exercises, they are done solo and so fiddling with line endings is a distraction. Therefore I would be in favour of dropping these rules from the CRA template.

Closing in favour of https://github.com/CodeYourFuture/syllabus/issues/237, since it'll get more eyes there.


Reformatting the Steps Layout

Problem:
The alignment of the Steps layout on the Home page is not visually appealing

Solution :
The paragraphs under each Step can be aligned left/right with respect to the positioning of the illustrations.

I would like to take upon this issue @smaranjitghose

@smaranjitghose Will, you be tagging any labels? (I'm a GSSoC'21 Participant)

@smaranjitghose Will, you be tagging any labels? (I'm a GSSoC'21 Participant)

yup


merge dev into main

:tada: This PR is included in version 0.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Backend storage got removed from endpoint, IO failed

Environment info

NooBaa Version: master-20210719
Platform: OCP 4.7

Actual behavior

Backend storage got unmapped from endpoint pod and IO failed

Expected behavior

Backend storage should not get unmapped on its own

Steps to reproduce
Debug Level is set to 5.

Upgrade from master-20210718 to master-20210719 build
Created bucket-22, bucket-23
Started upload of files of multiple sizes to these buckets:
upload failed: akshat/1M-objects/obj_816380 to s3://bucket-23/1M-objects/obj_816380 An error occurred (NoSuchKey) when calling the PutObject operation: The specified key does not exist. upload failed: akshat/1M-objects/obj_816374 to s3://bucket-23/1M-objects/obj_816374 An error occurred (NoSuchKey) when calling the PutObject operation: The specified key does not exist. upload failed: akshat/1M-objects/obj_816377 to s3://bucket-23/1M-objects/obj_816377 An error occurred (NoSuchKey) when calling the PutObject operation: The specified key does not exist.

In the middle of the run, found IO failing and df -h is not showing /nsfs mounted.
[root@ocp-akshat-1-inf ~]# oc rsh noobaa-endpoint-5b6c977579-fknb9
sh-4.4# df -h
Filesystem                            Size  Used Avail Use% Mounted on
overlay                               250G   56G  195G  23% /
tmpfs                                  64M     0   64M   0% /dev
tmpfs                                  16G     0   16G   0% /sys/fs/cgroup
shm                                    64M     0   64M   0% /dev/shm
tmpfs                                  16G   53M   16G   1% /etc/hostname
tmpfs                                  16G  8.0K   16G   1% /etc/mgmt-secret
tmpfs                                  16G  8.0K   16G   1% /etc/s3-secret
/dev/mapper/coreos-luks-root-nocrypt  250G   56G  195G  23% /etc/hosts
tmpfs                                  16G   28K   16G   1% /run/secrets/kubernetes.io/serviceaccount
tmpfs                                  16G     0   16G   0% /proc/acpi
tmpfs                                  16G     0   16G   0% /proc/scsi
tmpfs                                  16G     0   16G   0% /sys/firmware

Namespacestore is giving error as well:
[root@ocp-akshat-1-inf ~]# noobaa namespacestore status nsfs-nsr-1
I0719 11:48:42.045212 1019284 request.go:645] Throttling request took 1.02930404s, request: GET:https://api.ocp-akshat-1.cp.fyre.ibm.com:6443/apis/operator.openshift.io/v1alpha1?timeout=32s
INFO[0001] ✅ Exists: NamespaceStore "nsfs-nsr-1"
ERRO[0001] ❌ NamespaceStore "nsfs-nsr-1" Phase is "Rejected": Namespace store mode: STORAGE_NOT_EXIST NamespaceStorePhaseRejected

# NamespaceStore spec:
nsfs:
  fsBackend: GPFS
  pvcName: gpfs-vol
  subPath: ""
type: nsfs

Uploading must-gather logs
More information - Screenshots / Logs / Other output

must-gather-2.tar.gz

2nd run results:
noobaa_diagnostics_1626766094.tar.gz
must-gather-3.tar.gz

Getting same result on new deployment as well:
must-gather-4.tar.gz

@akmithal with this PR in https://github.com/noobaa/noobaa-operator/pull/693
Please repro, the endpoint should not restart and we can see what's happening


DNEXT-23501:add the new api SECValidateAccessToken in docs.

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


Change last child to first child(ie8)

Change :last-child to :first-child and padding from left to right, so that the css is compatible with IE8.  No visual changes.

👍


Something wrong with gradle

Trying to run my app for android and facing this error
Could not find gradle wrapper within android sdk. Might need to update your Android SDK
Then I navigate to platform/android dir and tried runnig gradle prepareWrapper:prepareWrapper and got
No installed build tools found. Please install the Android build tools version 19.1.0 or higher
That is strange because I have exactly build tool version 19.1.0
Also I found issue #369 which is a similar problem
Is there some kind of bug?

I have the same proble, and with this post i SOLVED... THANKS!!!

you saved my day man! awesome \o/


Remove "Natures Organics"

Natures Organics does not have, and has never had, a bug bounty program. Not sure what data this list was compiled from.

Thanks for the update 👍


Faster implementation of monitor than standard library

I'll try https://github.com/nurse/ext_monitor

oh… I made a mistake… transfered to fluent/fluentd.

Here is my benchmark result of https://github.com/fluent/fluentd/pull/2561
Monitor#synchronize is still slower...
- ruby 2.6.3

Warming up --------------------------------------
             monitor   184.967k i/100ms
               mutex   289.882k i/100ms
Calculating -------------------------------------
             monitor      3.287M (± 2.2%) i/s -     16.462M in   5.011436s
               mutex      8.005M (± 1.6%) i/s -     40.294M in   5.034949s

- ruby 2.6.5
Warming up --------------------------------------
             monitor    56.806k i/100ms
               mutex   280.742k i/100ms
Calculating -------------------------------------
             monitor    678.492k (± 4.7%) i/s -      3.408M in   5.035571s
               mutex      8.054M (± 2.4%) i/s -     40.427M in   5.022535s

- ruby 2.6.5 with ext_monitor
Warming up --------------------------------------
             monitor    62.786k i/100ms
               mutex   292.756k i/100ms
Calculating -------------------------------------
             monitor    754.165k (± 2.2%) i/s -      3.830M in   5.080977s
               mutex      8.031M (± 1.4%) i/s -     40.400M in   5.031691s

For my understanding, this gem is a faster version of the exising Monitor class, not Mutex class.
So we should compare Monitor library ruby provides and this gem.
require 'benchmark/ips'
# require 'ext_monitor'

mo = Monitor.new
mu = Mutex.new

p "Ruby #{RUBY_VERSION}"

Benchmark.ips do |x|
  x.report("monitor") do
    mo.synchronize {}
  end

  x.report("mutex") do
    mu.synchronize {}
  end
end

with ext_monitor
"Ruby 2.5.5"
Warming up --------------------------------------
             monitor   266.565k i/100ms
               mutex   351.016k i/100ms
Calculating -------------------------------------
             monitor      4.937M (± 4.7%) i/s -     24.791M in   5.036034s
               mutex      7.851M (± 4.7%) i/s -     39.314M in   5.018843s

without ext_monitor (commented out)
"Ruby 2.5.5"
Warming up --------------------------------------
             monitor   228.634k i/100ms
               mutex   347.341k i/100ms
Calculating -------------------------------------
             monitor      3.797M (± 2.1%) i/s -     18.977M in   5.000240s
               mutex      8.139M (± 1.8%) i/s -     40.986M in   5.037270s

Yes, but the problem is ruby 2.6.4 and later has slower Monitor.
See my benchmark result. ruby 2.6.5 with ext_monitor is still very slower than ruby 2.6.3 without ext_monitor.

ah, my bad. You already compared them...
The benchmark running on my local MacBook results in a similar one to yours (around 838.033k even if using ext_monitor).

Thank you for testing. I found a bug and fixed and released v0.1.1: https://rubygems.org/gems/ext_monitor/versions/0.1.1

Great 👏
with ext_monitor (2x faster)
"Ruby 2.6.3"
Warming up --------------------------------------
             monitor   327.029k i/100ms
               mutex   362.710k i/100ms
Calculating -------------------------------------
             monitor      7.507M (± 2.4%) i/s -     37.608M in   5.012856s
               mutex     10.517M (± 2.5%) i/s -     52.593M in   5.004291s

without ext_monitor
"Ruby 2.6.3"
Warming up --------------------------------------
             monitor   230.079k i/100ms
               mutex   364.688k i/100ms
Calculating -------------------------------------
             monitor      3.781M (± 4.7%) i/s -     18.866M in   5.000347s
               mutex      9.479M (± 5.1%) i/s -     47.409M in   5.014644s

with ext_monitor(10x faster)
"Ruby 2.6.5"
Warming up --------------------------------------
             monitor   333.879k i/100ms
               mutex   377.950k i/100ms
Calculating -------------------------------------
             monitor      8.036M (± 3.1%) i/s -     40.399M in   5.033352s
               mutex     10.204M (± 3.9%) i/s -     51.023M in   5.008424s

without ext_monitor
"Ruby 2.6.5"
Warming up --------------------------------------
             monitor    73.338k i/100ms
               mutex   385.539k i/100ms
Calculating -------------------------------------
             monitor    892.246k (± 5.1%) i/s -      4.474M in   5.028408s
               mutex     10.528M (± 2.6%) i/s -     52.819M in   5.020783s


Improve Scenario Detection

Molecule should be able to detect scenarios.
For example, maybe during molecule list commands and so on

Closed by #3989


early versions of flit have requires_python="3"

This breaks the in-progress deps subcommand.  Is this even valid?

Appears to be valid, per https://www.python.org/dev/peps/pep-0345/#version-specifiers

Requires-Python: 3: Any Python 3 version, no matter which one, excluding post or pre-releases.