Add OCI-Referrers header

This adds an optional header that servers can use to inform clients about the lack of a referrers listing for a given manifest, enabling clients to skip some requests.
Related to #454.

If we know they don't have reference we also know whether they do.

@mikebrow Since this is a "MAY", the absence of the header needs to be treated as if referrers could exist. For a client that is pulling referrers along with the rest of the image, the workflow is the same if there was an OCI-Referrers: present header as if it didn't exist. Are there use cases where adding that header would change the client behavior?
From the previous discussions and linked issue, the workflow we were considering for referrers that exists is to add a Link header giving clients a direct URL to pull the referrers from a CDN. The Link header would avoid querying the referrers API to get the 307 (redirect) to the CDN location. I'm avoiding #454 with this PR so the Link header can be added in a separate PR.
For the "point in time", that applies to every referrers API request. That would make more sense in documenting the referrers API itself, and not the manifest GET response.

If we know they don't have reference we also know whether they do.

@mikebrow Since this is a "MAY", the absence of the header needs to be treated as if referrers could exist. For a client that is pulling referrers along with the rest of the image, the workflow is the same if there was an OCI-Referrers: present header as if it didn't exist. Are there use cases where adding that header would change the client behavior? If we can't find use cases today but discover them later, we could also add this to the spec later.

isn't it more expensive to force all clients to assume existence every time make the extra referrers requests?

From the previous discussions and linked issue, the workflow we were considering for referrers that exists is to add a Link header giving clients a direct URL to pull the referrers from a CDN. The Link header would avoid querying the referrers API to get the 307 (redirect) to the CDN location. I'm avoiding closing the linked #454 with this PR so the Link header can be added in a separate PR.

fair to say a link header would be one way/mode to provide a positive indicator.. still not sure why avoiding link or positive notice for local is encouraging clients to not call referrers, when no negative response header is provided.. though I do expect clients to configure yes/no look for artifacts even if no response header is provided indicating artifact existence..

For the "point in time", that applies to every referrers API request. That would make more sense in documenting the referrers API itself, and not the manifest GET response.

the lack of subject refers to the manifest would be a point in time notice.. not following why making that point here and in the referrers api will not make sense to the reader...

client1.. pull image with unpack... trace log includes that artifacts have been reported for the following:
client1.. reports upstream the notified existence of artifacts for...
upstream client.. pulls said artifacts for reported.. applying upstream filters etc..
upstream client requests client1 run the container

isn't it more expensive to force all clients to assume existence every time make the extra referrers requests?

It's very expensive and will be at least half of the referrers requests for clients that implement recursive queries, which is why this PR is here. But making the opposite assumption, that a lack of the header means there are no referrers, cannot be safely done.
We have the following decision logic:

Client doesn't want referrers (i.e. today's runtimes that aren't referrers aware)

1: Just pull the manifest and ignore any headers if they exist

Client wants referrers

Registry is 1.0 and client will fallback

2a: Referrers query fails, fallback tag get fails, no referrers
2b: Referrers query fails, fallback tag finds referrers

Registry is 1.1 but does not implement the header

3: Referrers query returns list, possibly empty if none exist

Registry is 1.1 and implements the absent header

4a: If there are no referrers, client sees the absent header and skips the referrers query
4b: Referrers query returns listing

Registry is 1.1 and implements the absent and present header

5a: If there are no referrers, client sees the absent header and skips the referrers query
5b: If there are referrers, present header exists and referrers query returns listing

The client behavior between the 4 and 5 is the same. And a client must run the referrers query if there is no header to handle scenarios 2 and 3. Effectively when the client doesn't get an absent header, it may be 4b, 3, or 2, and the client doesn't know until it runs the referrers query.
Is there a scenario I'm missing where adding the present header would help clients?

I would prefer not encouraging registries to do more (potentially unnecessary) work on any of the APIs in the "pull" workflow. Some clients will need this information, but (IMO) most won't, so it seems like our goal should be to keep the manifest GET API should be as simple as possible.

I would prefer not encouraging registries to do more (potentially unnecessary) work on any of the APIs in the "pull" workflow. Some clients will need this information, but (IMO) most won't, so it seems like our goal should be to keep the manifest GET API should be as simple as possible.

@michaelb990 agreed, that's why this was only a MAY. If/when registries think that the added work will reduce their overhead, they can add it. And until then, there won't be any header so clients that need to pull referrers will always query for them.

I would prefer not encouraging registries to do more (potentially unnecessary) work on any of the APIs in the "pull" workflow. Some clients will need this information, but (IMO) most won't, so it seems like our goal should be to keep the manifest GET API should be as simple as possible.

Agree with this.
How do we feel about a client header that positively indicates that the client wants referrers information? Then the registry doesn't have to guess about whether it's "worth" calculating this header for the client.
For clients that don't care about referrers, the registry doesn't have to do any additional work to query referrers.

How do we feel about a client header that positively indicates that the client wants referrers information? Then the registry doesn't have to guess about whether it's "worth" calculating this header for the client.
For clients that don't care about referrers, the registry doesn't have to do any additional work to query referrers.

@jonjohnsonjr @michaelb990 I've updated with the client header. Let me know if that covers your concerns.
@mikebrow have your concerns above been addressed?

We are leaning towards not implementing this header in Azure Container Registry due to the added processing cost of consistently calculating this value.

Based on the Jan 11th call, we're postponing any decision to 1.2

if not included in OCI 1.1 clients and the registries can proof of concept the header optimization ...


Adding my name to the Hall of Fame

Hello,
Please add me im learning to get used to github. :)
greetings David

Thanks for opening this @Bigedigedi - very nice :yellow_heart:


nixos/system: Support pre-activated images

Description of changes
Mostly refactoring, except for the last commit which introduces the feature.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

@ofborg test simple installer.simple switchTest
@ofborg test systemd-boot
@ofborg test nixos-rebuild-specialisations

This has uncovered some previously broken tests, but works with my fixes applied:

https://github.com/NixOS/nixpkgs/pull/237069
https://github.com/NixOS/nixpkgs/pull/237063

Don't know how to fix:

https://github.com/NixOS/nixpkgs/issues/237073

I wasn't happy about the lack of validation or test, so I did the thing, not just refactor prep anymore. See last commit.

I am following this PR but my bandwidth is a bit low right now, I will try
to give it a proper review later on.
Le mer. 28 juin 2023 à 14:10, Robert Hensing @.***> a
écrit :

I wasn't happy about the lack of validation or test, so I did the thing,
not just refactor prep anymore. See last commit.
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/237040#issuecomment-1611287614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACMZRFGC4MIMMMEJMX7AR3XNQNKLANCNFSM6AAAAAAZBWCGJA
.
You are receiving this because you commented.Message ID:
@.***>

Thanks!


docker/volumes-backup-extension:1.1.9

On export to local file any volume return "Failed to backup volume volume_name to user_defined_path: {"message":"Internal Server Error"}. HTTP status code: 500". And no file create.
Docker version 4.32 on WSL
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3880
Steps to reproduce the behavior:

Go to Extensions -> Volumes Backup $ Share
Click on any volume "Export volume"
Select directory
Click "Export" button
Wait some time, see error on bottom right corner

The same error.
Docker Desktop v4.33.1
Windows 11

The same error, Docker Desktop v4.33.1


Test fails to complete after git clone

faucet-1967 gauge-1967
*** Starting 3 switches
s0b s0c s0d ...
*** Waiting for switches to connect
__main__.FaucetAPITest.test_api (subunit.RemotedTestCase)
__main__.FaucetAPITest.test_api ... FAIL
error: __main__.FaucetAPITest.test_api [
Traceback (most recent call last):
  File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 212, in tearDown
    0, os.path.getsize(os.environ['FAUCET_EXCEPTION_LOG']))
  File "/usr/lib/python2.7/genericpath.py", line 57, in getsize
    return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: '/tmp/faucet-tests-y6Typi/FaucetAPITest-test_api-JN9Gab/faucet-exception.log'
faucet-1967 gauge-1967
*** Starting 3 switches
s0b s0c s0d ...
*** Waiting for switches to connect
__main__.FaucetAPITest.test_api (subunit.RemotedTestCase)
__main__.FaucetAPITest.test_api ... FAIL
error: __main__.FaucetAPITest.test_api [
Traceback (most recent call last):
  File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 212, in tearDown
    0, os.path.getsize(os.environ['FAUCET_EXCEPTION_LOG']))
  File "/usr/lib/python2.7/genericpath.py", line 57, in getsize
    return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: '/tmp/faucet-tests-y6Typi/FaucetAPITest-test_api-JN9Gab/faucet-exception.log'
]
*** Creating network
*** Adding controller
*** Adding hosts:
u131 u132 u141 u142
*** Adding switches:
s13 s14
*** Adding links:
(s13, s14) (u131, s13) (u132, s13) (u141, s14) (u142, s14)
*** Configuring hosts
u131 u132 u141 u142
*** Starting controller
faucet-1964 gauge-1964
*** Starting 2 switches
s13 s14 ...
*** Waiting for switches to connect

On a fresh Ubuntu 16.04 server install, i get the above error when trying to run "sudo ./faucet_mininet_test.py". Where the test fails to progress for over 30 minutes.
I've installed all the dependencies that the test requests and cloned/installed mininet
commit d528da479d82a0efa9e73a4b5d8959f91c9f3cdf
mininet: 2.3.0d1
required binary/library ryu-manager --version version is 4.11
required binary/library ovs-vsctl --version version is 2.5
required binary/library tcpdump -h version is 4.9
required binary/library nc present (nc from the netcat-openbsd)
required binary/library vconfig present (the VLAN you are talking about)
required binary/library fuser -V version is 22.21
required binary/library mn --version version is 2.3
required binary/library exabgp --version version is 3.4
required binary/library pip show influxdb version is 4.0
required binary/library pylint --version version is 1.6
required binary/library curl --version version is 7.47
required binary/library ladvd -v version is 1.1

I then do
pip install ryu-faucet which makes the test complete. but with errors similar to
ERROR: __main__.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
__main__.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "./faucet_mininet_test.py", line 1130, in setUp
    self.start_net()
  File "./faucet_mininet_test.py", line 192, in start_net
    name='faucet', ports_sock=self.ports_sock, port=self.of_port))
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 173, in __init__
    self.build()
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 501, in build
    self.buildFromTopo( self.topo )
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 488, in buildFromTopo
    self.addLink( **params )
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 399, in addLink
    link = cls( node1, node2, **options )
  File "build/bdist.linux-x86_64/egg/mininet/link.py", line 450, in __init__
    node1, node2, deleteIntfs=False )
  File "build/bdist.linux-x86_64/egg/mininet/link.py", line 494, in makeIntfPair
    deleteIntfs=deleteIntfs )
  File "build/bdist.linux-x86_64/egg/mininet/util.py", line 195, in makeIntfPair
    ( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (u131-eth0,s13-eth3): RTNETLINK answers: File exists

======================================================================
FAIL: __main__.FaucetTaggedIPv4RouteTest.test_tagged (subunit.RemotedTestCase)
__main__.FaucetTaggedIPv4RouteTest.test_tagged
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
  File "./faucet_mininet_test.py", line 1505, in test_tagged
    second_host, second_host_routed_ip)
  File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 674, in verify_ipv4_routing
    with_group_table=with_group_table)
  File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 627, in wait_for_route_as_flow
    'SET_FIELD: {eth_dst:%s}.+%s' % (nexthop, nw_dst_match), timeout)
  File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 364, in wait_until_matching_flow
    msg=exp_flow)
  File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
    raise self.failureException(msg)
AssertionError: SET_FIELD: {eth_dst:e2:6f:7e:88:92:aa}.+"nw_dst": "<IP_ADDRESS>/<IP_ADDRESS>"

facuet-test-error.txt

Looks like a couple of different problems. First problem - may be that
there is a missing dependency (which means the controller isn't starting).
Taking a look at the logs under /tmp/faucet-tests would be helpful.
When you pip install likely that corrects the missing dependencies. It
looks like something on the machine may be interfering with the tests. Is
this output from running the tests under docker? This is the preferred way
to avoid any potential interference from the host.
On Tue, Feb 28, 2017 at 9:51 AM, Bairdo<EMAIL_ADDRESS>wrote:

I then do
pip install ryu-faucet which makes the test complete. but with errors
similar to
ERROR: main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged (subunit.RemotedTestCase)
main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged
_StringException: Traceback (most recent call last):
File "./faucet_mininet_test.py", line 1130, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 192, in start_net
name='faucet', ports_sock=self.ports_sock, port=self.of_port))
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 173, in init
self.build()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 501, in build
self.buildFromTopo( self.topo )
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 488, in buildFromTopo
self.addLink( **params )
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 399, in addLink
link = cls( node1, node2, **options )
File "build/bdist.linux-x86_64/egg/mininet/link.py", line 450, in init
node1, node2, deleteIntfs=False )
File "build/bdist.linux-x86_64/egg/mininet/link.py", line 494, in makeIntfPair
deleteIntfs=deleteIntfs )
File "build/bdist.linux-x86_64/egg/mininet/util.py", line 195, in makeIntfPair
( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (u131-eth0,s13-eth3): RTNETLINK answers: File exists
======================================================================
FAIL: main.FaucetTaggedIPv4RouteTest.test_tagged (subunit.RemotedTestCase)
main.FaucetTaggedIPv4RouteTest.test_tagged
_StringException: Traceback (most recent call last):
File "./faucet_mininet_test.py", line 1505, in test_tagged
second_host, second_host_routed_ip)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 674, in verify_ipv4_routing
with_group_table=with_group_table)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 627, in wait_for_route_as_flow
'SET_FIELD: {eth_dst:%s}.+%s' % (nexthop, nw_dst_match), timeout)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line 364, in wait_until_matching_flow
msg=exp_flow)
File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
raise self.failureException(msg)
AssertionError: SET_FIELD: {eth_dst:e2:6f:7e:88:92:aa}.+"nw_dst": "<IP_ADDRESS>/<IP_ADDRESS>"
facuet-test-error.txt
https://github.com/REANNZ/faucet/files/804973/facuet-test-error.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/REANNZ/faucet/issues/426#issuecomment-282848986, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEgZ1-09PM4a7qyu5Or69HT38HU-hN-Vks5rgzdCgaJpZM4MNmqK
.

when you do pip install, it pulls Faucet from pypi repository which is
1.3.2.  The test suite is using the code changes as of now.  So, you will
want to do from your git cloned repo is:
$ make
$ sudo -H pip install dist/ryu*gz
This will make sure you have the correct code.
Thanks
/Shivaram
On Mon, Feb 27, 2017 at 12:55 PM, Josh Bailey<EMAIL_ADDRESS>wrote:

Looks like a couple of different problems. First problem - may be that
there is a missing dependency (which means the controller isn't starting).
Taking a look at the logs under /tmp/faucet-tests would be helpful.
When you pip install likely that corrects the missing dependencies. It
looks like something on the machine may be interfering with the tests. Is
this output from running the tests under docker? This is the preferred way
to avoid any potential interference from the host.
On Tue, Feb 28, 2017 at 9:51 AM, Bairdo<EMAIL_ADDRESS>wrote:

I then do
pip install ryu-faucet which makes the test complete. but with errors
similar to
ERROR: main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged
(subunit.RemotedTestCase)
main.FaucetTaggedAndUntaggedTest.test_seperate_untagged_tagged
_StringException: Traceback (most recent call last):
File "./faucet_mininet_test.py", line 1130, in setUp
self.start_net()
File "./faucet_mininet_test.py", line 192, in start_net
name='faucet', ports_sock=self.ports_sock, port=self.of_port))
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 173, in
init
self.build()
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 501, in build
self.buildFromTopo( self.topo )
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 488, in
buildFromTopo
self.addLink( **params )
File "build/bdist.linux-x86_64/egg/mininet/net.py", line 399, in addLink
link = cls( node1, node2, **options )
File "build/bdist.linux-x86_64/egg/mininet/link.py", line 450, in
init
node1, node2, deleteIntfs=False )
File "build/bdist.linux-x86_64/egg/mininet/link.py", line 494, in
makeIntfPair
deleteIntfs=deleteIntfs )
File "build/bdist.linux-x86_64/egg/mininet/util.py", line 195, in
makeIntfPair
( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (u131-eth0,s13-eth3): RTNETLINK
answers: File exists
======================================================================
FAIL: main.FaucetTaggedIPv4RouteTest.test_tagged
(subunit.RemotedTestCase)
main.FaucetTaggedIPv4RouteTest.test_tagged
_StringException: Traceback (most recent call last):
File "./faucet_mininet_test.py", line 1505, in test_tagged
second_host, second_host_routed_ip)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line
674, in verify_ipv4_routing
with_group_table=with_group_table)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line
627, in wait_for_route_as_flow
'SET_FIELD: {eth_dst:%s}.+%s' % (nexthop, nw_dst_match), timeout)
File "/home/mininet/faucet/tests/faucet_mininet_test_base.py", line
364, in wait_until_matching_flow
msg=exp_flow)
File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
raise self.failureException(msg)
AssertionError: SET_FIELD: {eth_dst:e2:6f:7e:88:92:aa}.+"nw_dst": "
<IP_ADDRESS>/<IP_ADDRESS>"
facuet-test-error.txt
https://github.com/REANNZ/faucet/files/804973/facuet-test-error.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/REANNZ/faucet/issues/426#issuecomment-282848986,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEgZ1-
09PM4a7qyu5Or69HT38HU-hN-Vks5rgzdCgaJpZM4MNmqK>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/REANNZ/faucet/issues/426#issuecomment-282850299, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmf84zeVDOQuSLj3iPaozw4JLFSWWh7ks5rgzhKgaJpZM4MNmqK
.

Thanks Guys. The original tests were not from Docker. I've since tried running them with Docker but get a similar result.
I've had a look at the docker filesystem under 2 of the tests that fail and cannot see any obvious error messages.
facuet-test-error-docker.txt

I believe I found the problem - update_nexthop() would be a NOP, if the nexthop was expired but hadn't changed (it's a race, basically).
https://github.com/REANNZ/faucet/commit/58056630d7decaf5dc8f69cbe4fe60121c239a5e just now fixes it.
I need to add more extensive explicit tests of the various resolution paths to make sure they're all caught.

That seems to fix it. Thank you


Run pdk update

The pdk templates have changed significantly since pdk was last
used on this module.  This runs the pdk update command
and brings in all the latest module best practices that pdk
uses.

@dylanratcliffe I am making a lot of changes to this repo and could use a reviewer who knows latest puppet best practices.  This change here is simple a pdk update with 1.17 templates.  Also a few modifications to to get it working with rubocop and travis.


secrets.json > keypass for important tokens, passwords?

Hi @patrickbeeson,
Thank you for setting up the initial repo for the portlandpython.org site. I have tried to test the repo, but it is asking for a secrets.json file. What variables/constants are stored in your secrets.json?
Would it be ok to a store an encrypted version of the json file somewhere (but not in this repo!) or store all tokens and passwords in a keypass (e.g. kbdx file) and we read all variables from the bash environment?
What do you think?
-Hannes

Hey Hannes!
You can get a sense of what's being stored in the secrets.json file by looking in the settings. I've not used a keypass before but I'm certainly open to anything.
I'm currently storing the secret key, db name (prod), db password (prod) and email host password (prod) in the json file.
Of course, those values don't mean much yet since we don't have a production environment configured. Also, we have yet to solve for email sending.
But you'll need the secret key to run locally. How would you like to share this value?

Hey Patrick,
I am sorry for the late reply. I created a secrets.json with the required keys and random values and everything worked fine (the basic test suite ran fine). Have you used the secrets.json option with Heroku? Is it difficult to upload the file without adding it to the repo (for the automatic deployment)?
Heroku handles environment variables nicely and I used to keep all variables/passwords in a keypass file which could be shared between the contributors. However, the way with the secrets.json file seems very clean. I would suggest: If Heroku runs fine with the secrets.json file, let's go with that. Otherwise, I would create a file with the environment variables. What do you think?

Environment variables would work nicely. I'm open to whatever is easier for
contributors and the deployment environment.
Can you point me to docs outlining what's needed?
On Mon, Sep 21, 2015 at 3:15 PM, Hannes Hapke<EMAIL_ADDRESS>wrote:

Hey Patrick,
I am sorry for the late reply. I created a secrets.json with the required
keys and random values and everything worked fine (the basic test suite ran
fine). Have you used the secrets.json option with Heroku? Is it difficult
to upload the file without adding it to the repo (for the automatic
deployment)?
Heroku handles environment variables nicely and I used to keep all
variables/passwords in a keypass file which could be shared between the
contributors. However, the way with the secrets.json file seems very clean.
I would suggest: If Heroku runs fine with the secrets.json file, let's go
with that. Otherwise, I would create a file with the environment variables.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/portlandpython/portlandpython.org/issues/8#issuecomment-142125137
.

--
Patrick Beeson
<EMAIL_ADDRESS>

Hi Patrick,
Nothing is needed at this stage. I rewrote the get_secret method so that it reads env variables and raises an error if the key isn't set. This could be better handled in the future with os.environ.get() and with a default value.
Based on the changes, I created the hook to travis-ci.org/portlandpython/portlandpython.org/. I had to drop the Python 2.6 support due to a strange Django error, but we shouldn't use 2.6 at this stage anymore.
Once we run actual tests (my current sample test isn't executed), the coverage results can be found [here] (https://coveralls.io/github/portlandpython/portlandpython.org#).
My next step is the setup for the automatic push to a Heroku staging environment. It will be based on the encryption keys settings. The setup is a bit weird and in the past I only used codeship which integrates very nicely with Heroku. Give me a few days and I can write up some documentation about the whole process.


Fixed new FTB installer args and manifest

Fix regression from https://github.com/itzg/docker-minecraft-server/pull/3174
Applies info from https://github.com/FTBTeam/FTB-Modpack-Issues/issues/6312#issuecomment-2516899020

Currently closes the server, this is what it says in the logs:
[init] Running as uid=1000 gid=1000 with /data as 'drwxr-x--- 18 1000 1000 4096 Nov 15 19:48 /data'
[init] FTB modpack ID 126, version ID 100001 is ready to go
jq: error: Could not open file .manifest.json: No such file or directory

Ah, I'm sorry, I broke the legacy installer support with that and I'll see if I can fix that. For now you can set FTB_FORCE_REINSTALL to "true".

@framerunner this build should fix the issue https://github.com/itzg/docker-minecraft-server/actions/runs/12180940206


Changing carb ratio doesn't work with every value

FAX Version: <IP_ADDRESS>
IOS 15.1
Phone: Iphone 12 mini
Emalink
Chosing some values (e.g. 6.1 g/U or 7.8 g/U) CR is automatically reset to 3.0 (see attached movie)
https://user-images.githubusercontent.com/62246679/141456004-2580c815-6dd3-4c91-b4a3-c09922837933.MP4

Fixed


proposal: OOVSkills

these are some notes i had in a gist, just an idea not something in roadmap, but i figured it would be cool to discuss
OOVSkills framework proposal

out-of-vocabulary intents skill class - OOVSkills
triggered before common_query framework
match an intent using something like https://github.com/GT4SD/zberta

this gives us an intent classification without a registred handler
"handle this question" becomes "handle this intent somehow"
OOVSkills can use this info for a richer common_query experience

send the intent_tag + utterance to OOVSkills

I like the notion. I couldn’t help noticing that the image above depicts an overcapture that might not be avoidable.

To summarize some notes from a chat with @JarbasAl:
I could see using this system to handle "common" intents ("time", "weather", "jokes", etc.) where the intent matching is all done in some intent engine (or bundled adapt/padatious intents) and skills simply register handlers for these known intents.
The advantage here is that skill processing is separated from intent matching, so someone wanting to make a different "joke" skill or a specialized alarm handler doesn't need to write intents or manage intent conflicts

my design would be that we add a OOV plugin in there, any downstream can then do whatever it wants such as loading default padatious/adapt intents
i think a good output of this new plugin class would be a simple list of top 5 intents + confidence
as for plugin implementations it would be nice to team up with our friends at @secretsauceai and have 1 plugin for each of their implementations https://github.com/secretsauceai/NLU-engine-prototype-benchmarks we can also collaborate in intent datasets.
ping @AmateurAcademic

Gladly. All the intent tags have been cleaned for the data set and are ready. I am still working through the entity tags, that one takes a while. You are welcome to use whatever data you like, and if I can help further with data, please let me know. This is where I spend most of my leisure time. LOL
As for NLU engines, I do think the easiest solution is actually still Snips. It is fast, easy to run. I don't think you could run anything faster that performs so well. I have done many tests with logistic regression with BOWs/TFIDF, as well as other stuff like random forest, etc. and I have found nothing really beats logistic regression when it comes to these low powered engines. That CRFs for entity extraction are also based on LR is a great bonus. Snips uses this, plus it has a deterministic classifier so that it ensures that the training set works.
However, I have a few others I have been experimenting with that would provide the best results possible. The biggest, badest on the block would be the DistilBERT joint intent and entity classifier. I would highly recommend this one, based on my benchmarks. @JarbasAl, I can perhaps help you out there with this one. This will probably be the NLU engine I use in the end, since it gives the best performance. This is a PyTorch implementation I currently use: https://github.com/monologg/JointBERT. One drawback here is the lack of few-shot, to quickly train a classifier without fine-tuning.
I have also tried some few-shot models from Hugging Face. For intent tagging, it works pretty well. However, for entity tagging, it worked very poorly.
For a really good few-shot intent AND entity classifier, I am experimenting with several models, including few-shot with a t5. In theory, the t5 could do it all:

Few-shot for intent classification (intents, domains, or both).
Few-shot for entity extraction.
Maybe: few-shot for response generation (NLG) (I am still working on this).

For at least intent and entities it could very likely perform well with a t5-small (possibly even tiny) model, so it could be run by pretty much anyone in real-time. I am not sure when this will be ready. I want to finish cleaning the entity data first.
If there is anything else we can do, kindly let me know. Always happy to help!

my design would be that we add a OOV plugin in there, any downstream (such as neon-core) can then do whatever it wants such as loading default padatious/adapt intents

I'm not sure I understand what "out of vocabulary" means in this context; I would think that any intent engine could be plugged in wherever it wants relative to the other intent plugins.

i think a good output of this new plugin class would be a simple list of top 5 intents + confidence

Maybe this should be a broader intent refactoring? I could see the flow looking more like:

Converse
Collect intents with some normalized confidence (adapt, padatious, CommonQuery, any other engines)
Select best response with minimum confidence
Fallback

my design would be that we add a OOV plugin in there, any downstream (such as neon-core) can then do whatever it wants such as loading default padatious/adapt intents

I'm not sure I understand what "out of vocabulary" means in this context; I would think that any intent engine could be plugged in wherever it wants relative to the other intent plugins.

i think a good output of this new plugin class would be a simple list of top 5 intents + confidence

Maybe this should be a broader intent refactoring? I could see the flow looking more like:
1. Converse

2. Collect intents with some normalized confidence (adapt, padatious, CommonQuery, any other engines)

3. Select best response with minimum confidence

4. Fallback

the current flow is:

Converse
Skill Intents
CommonQA
Fallbacks

the new flow is:

Converse
Skill Intents
OOV framework
CommonQA
Fallbacks

OOV means you get a intent classification without a specified handler, it was provided by core but not by any specific skill, hence "out of vocabulary" from the registered skills POV
OOV service would itself be a plugin, several implementations for testing and benchmarks would be:

default (hardcoded) adapt/padatious intents  <- the easiest way for downstreams to use existing OVOS/Neon projects for testing
https://github.com/OpenJarbas/little_questions <- a simple  but useful question classifier, this is the sort of output I am personally interested in
collect different intent datasets, provide models for all implementations from @secretsauceai benchmarks under a plugin (model to load defined in config)
Zberta plugin, just to have a SOTA implementation of sorts to stimulate research into other similar and lightweight options

This should cover all use cases

related dataset: https://github.com/OpenJarbas/mycroft_intent_dataset

I think it would be better to implement Skill Intents as part of the OOV framework with confidence values used to determine which handler is used. i.e. a Padatious high conf match from a skill should not always take priority over a Padatious match from the OOV service.
In practice, you might end up with Adapt/Padatious intents taking top priority in any case since you'd have to weight the different OOV plugins in any case
From an implementation standpoint too, giving skill intents priority would mean that "legacy" skills would always take priority over skills implementing OOV.

this is indeed intended behavior, different setups may use different OOV frameworks (by design, classifiers trained for a specific domain) which means OOV skills will NOT work everywhere.
regular skills should take precedence, that is the default way to add new intents to the framework without retraining anything at runtime
a skill can ofc use both frameworks, like it can use converse + intents + fallback all at once
since by default ovos-core does not force skills, any derivative voice assistant (such as classic core or neon) could use exclusively the OOV framework if desired and dedicated skills, this seems to lign with what mycroft-dinkum intended and could be implemented via something like https://github.com/OpenVoiceOS/my-assistant
on a related note hardcoded adapt/padatious are also roadmapped to be pluginified with a lot of work done already, i'd like to keep that discussion in other threads however, see linked issues in roadmap for intent plugins. the skill intents framework itself will soon also be replaceable

here is an approach for this https://gist.github.com/JarbasAl/e07e17a2d98a80eb6bf60139acc1b9c7


Question: column customization with multiple data fields

The data schema as followed:
{ symbol: 'AAPL', name: 'Apple', close: 123.45 }
Assuming there are 2 columns in the table: Stock and Price.  The Stock column will render two fields: symbol and name.
{symbol}

{name}

Based on your example, my Stock column will be something like below:
export const stockColumn = [
    {
        name: 'Stock',
        dataIndex: 'symbol + name',  // <--- what should be the input for multiple fields?
        renderer: ({ column, value, row }) => {
            // can the value be a object containing symbol and name?
            ...
        }
    }
];
Please advise me.  Thanks in advance!

For something like this, where you'd like to combine two data entries into a single column you should use a custom renderer. The implementation would like something like this:
const columns = [
    {
        name: 'Combined Column',
        dataIndex: 'it-wont-matter',
        renderer: ({ column, value, row }) => {
            return (

                     { row.stock }
                     { row.symbol }

            );
        }
    }, // ... rest of columns
];

Since the renderer determines what the final output will be, it's not important what the dataIndex for the column is. Let me know if you need more information.

Thanks again @bencripps, let me go try it out.


Remove guard question from diversity section

This removes the guard question from the diversity section. This mirrors work that happened on Apply last year.
In most cases, one or both of the diversity questions is answered - so having a guard question usually adds extra steps.
As a byproduct, the summary card will now always have rows for ethnicity and disabilities.

 Prototype: remove guard question from diversity section


ca: Readd WaitGroup to Server

The WaitGroup was removed as a simplification in #1841, but this causes (*Server).Stop to potentially return before Run is finished. This is unwanted behavior that causes data races in tests. Readd the WaitGroup, but only use it to wait for Run to finish, not RPC handlers.
cc @dperny @cyli

LGTM

Merging this to fix CI on master. Feel free to do more review after the fact.


System Digest integration

Integrate system digest once it has been built.

Nearly there - add right click option to dual wall to show/hide


Update README.md

Hi,
This is an update on the description of my Discord bot project - vnc-lm in the README.
Thank you,
Jake

Thank you!


feat: for ios, solve the CORS problem

I found a CORS problem when I send a request 'https://xxx' from 'localhost'.
I just modified some code for my project and it does work.
Of course it would be great if you have better solution.

Just confirmed the fix, I was facing CORS issues too and it have been solved after applying the changes provided by @ImHeXin on file ios/GCDWebServer/core/GCDWebServerConnection.m.
There is any plans to approve and release this PR @fchasen ?
Regards

Fixed in #89


Update UI design for SC body

Coverage increased (+0.2%) to 71.198% when pulling 006abc55633e04497beae44228810fccb3db39d3 on asifdxtreme:master into cfb2ab88a5a976d2375826da14898e52ff95c127 on ServiceComb:master.

Codecov Report

Merging #105 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #105      +/-   ##
==========================================
- Coverage    66.8%   66.75%   -0.06%
==========================================
  Files          18       18
  Lines        3956     3956
==========================================
- Hits         2643     2641       -2
- Misses       1148     1150       +2
  Partials      165      165

Impacted Files
Coverage Δ

server/service/governservice.go
64.07% <0%> (-1.46%)
:arrow_down:

server/service/services_dependency.go
68.3% <0%> (+0.7%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cfb2ab8...006abc5. Read the comment docs.


Cocos-91 - Update Makefile and cocos documentation

Updated Makefile to include install instructions for manager.
Updated manager/README.md and cli/README.md to reflect changes in the Makefile.
Resolves #91

No need for automated installation for now. We can keep CLI in the build dir. This cli will be published on our GitHub on our GitHub, compiled statically and downloadable from GitHub - so no installation will be done via Makefile.


Validation Of Details In Feedback Form Is Not working!

If I Keep All The Fields Empty and Do not enter Any Detail Then Also The Feedback Form is getting Submitted and Do Not Show Any Warning.
It Needs To Be Fixed.

TAGS
 Bug , LGMSOC

While I Was Fixing The Issue I thought Of Adding The (city, state, and zip code) Fields!
@nlok5923  @QAZIMAAZARSHAD Bhaiya  Should I add These Fields... It Will Give a More Professional Feel To The Viewers. Shall I add It or Go with the previous One!

Sure go ahead.

i think i have settle the validation for this feedback form just i cannot push to it

please check


fix explain plan render, which is going to be multiple line in v2

before:

after:

Codecov Report

Merging #10208 (6677b9a) into master (c03e17d) will decrease coverage by 56.67%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #10208       +/-   ##
=============================================
- Coverage     70.39%   13.72%   -56.67%
+ Complexity     5751      178     -5573
=============================================
  Files          2017     1962       -55
  Lines        108978   106492     -2486
  Branches      16557    16263      -294
=============================================
- Hits          76714    14618    -62096
- Misses        26875    90726    +63851
+ Partials       5389     1148     -4241

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
13.72% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Learn more


#85 Implement scan command

Checks

[ ] Debugging completed
[x] Please debug me

Related Issue
This PR closes #85

Codecov Report
Base: 83.17% // Head: 82.99% // Decreases project coverage by -0.18% :warning:

Coverage data is based on head (2abb898) compared to base (d100df7).
Patch coverage: 67.21% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
- Coverage   83.17%   82.99%   -0.19%
==========================================
  Files          46       46
  Lines        2116     2146      +30
==========================================
+ Hits         1760     1781      +21
- Misses        356      365       +9

Impacted Files
Coverage Δ

necst/core/commander.py
83.51% <28.57%> (-9.08%)
:arrow_down:

tests/ctrl/test_coordinate_conversion.py
56.14% <61.53%> (+0.78%)
:arrow_up:

necst/ctrl/antenna/horizontal_coord.py
86.66% <82.75%> (+1.60%)
:arrow_up:

necst/definitions.py
100.00% <100.00%> (ø)

tests/core/test_commander.py
97.32% <100.00%> (+0.53%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


sec: Create organization CloudTrail

Terraform plan for sec-dev:
Terraform will perform the following actions:

  # module.sec_resources.data.aws_iam_policy_document.cloudtrail_log_bucket_policy will be read during apply
  # (config refers to values not yet known)
 <= data "aws_iam_policy_document" "cloudtrail_log_bucket_policy" {
      + id   = (known after apply)
      + json = (known after apply)

      + statement {
          + actions   = [
              + "s3:GetBucketAcl",
              + "s3:PutObject",
            ]
          + effect    = "Allow"
          + resources = [
              + (known after apply),
              + (known after apply),
            ]
          + sid       = "AllowAccessByCloudTrailSvcPrincipal"

          + condition {
              + test     = "StringEquals"
              + values   = [
                  + "533266992459",
                ]
              + variable = "aws:SourceAccount"
            }

          + principals {
              + identifiers = [
                  + "cloudtrail.amazonaws.com",
                ]
              + type        = "Service"
            }
        }
    }

  # module.sec_resources.aws_cloudtrail.main will be created
  + resource "aws_cloudtrail" "main" {
      + arn                           = (known after apply)
      + enable_log_file_validation    = true
      + enable_logging                = true
      + home_region                   = (known after apply)
      + id                            = (known after apply)
      + include_global_service_events = true
      + is_multi_region_trail         = true
      + is_organization_trail         = true
      + name                          = "main-dev"
      + s3_bucket_name                = (known after apply)
      + tags_all                      = (known after apply)
    }

  # module.sec_resources.aws_s3_bucket_lifecycle_configuration.log["cloudtrail"] will be created
  + resource "aws_s3_bucket_lifecycle_configuration" "log" {
      + bucket = (known after apply)
      + id     = (known after apply)

      + rule {
          + id     = "delete-old-files-dev"
          + status = "Enabled"

          + expiration {
              + days                         = 1
              + expired_object_delete_marker = (known after apply)
            }

          + filter {
            }
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].data.aws_iam_policy_document.baseline_bucket_policy will be read during apply
  # (config refers to values not yet known)
 <= data "aws_iam_policy_document" "baseline_bucket_policy" {
      + id                      = (known after apply)
      + json                    = (known after apply)
      + source_policy_documents = [
          + (known after apply),
        ]

      + statement {
          + actions   = [
              + "s3:*",
            ]
          + effect    = "Deny"
          + resources = [
              + (known after apply),
              + (known after apply),
            ]
          + sid       = "RequireLatestTLS"

          + condition {
              + test     = "NumericLessThan"
              + values   = [
                  + "1.3",
                ]
              + variable = "s3:TlsVersion"
            }

          + principals {
              + identifiers = [
                  + "*",
                ]
              + type        = "*"
            }
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket.main will be created
  + resource "aws_s3_bucket" "main" {
      + acceleration_status         = (known after apply)
      + acl                         = (known after apply)
      + arn                         = (known after apply)
      + bucket                      = "devshrekops-demo-cloudtrail-logs-dev"
      + bucket_domain_name          = (known after apply)
      + bucket_prefix               = (known after apply)
      + bucket_regional_domain_name = (known after apply)
      + force_destroy               = false
      + hosted_zone_id              = (known after apply)
      + id                          = (known after apply)
      + object_lock_enabled         = (known after apply)
      + policy                      = (known after apply)
      + region                      = (known after apply)
      + request_payer               = (known after apply)
      + tags_all                    = (known after apply)
      + website_domain              = (known after apply)
      + website_endpoint            = (known after apply)
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_ownership_controls.main will be created
  + resource "aws_s3_bucket_ownership_controls" "main" {
      + bucket = (known after apply)
      + id     = (known after apply)

      + rule {
          + object_ownership = "BucketOwnerEnforced"
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_policy.main will be created
  + resource "aws_s3_bucket_policy" "main" {
      + bucket = (known after apply)
      + id     = (known after apply)
      + policy = (known after apply)
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_public_access_block.main will be created
  + resource "aws_s3_bucket_public_access_block" "main" {
      + block_public_acls       = true
      + block_public_policy     = true
      + bucket                  = (known after apply)
      + id                      = (known after apply)
      + ignore_public_acls      = true
      + restrict_public_buckets = true
    }

Plan: 6 to add, 0 to change, 0 to destroy.

Terraform plan for sec-prod:
Terraform will perform the following actions:

  # module.sec_resources.data.aws_iam_policy_document.cloudtrail_log_bucket_policy will be read during apply
  # (config refers to values not yet known)
 <= data "aws_iam_policy_document" "cloudtrail_log_bucket_policy" {
      + id   = (known after apply)
      + json = (known after apply)

      + statement {
          + actions   = [
              + "s3:GetBucketAcl",
              + "s3:PutObject",
            ]
          + effect    = "Allow"
          + resources = [
              + (known after apply),
              + (known after apply),
            ]
          + sid       = "AllowAccessByCloudTrailSvcPrincipal"

          + condition {
              + test     = "StringEquals"
              + values   = [
                  + "339712815005",
                ]
              + variable = "aws:SourceAccount"
            }

          + principals {
              + identifiers = [
                  + "cloudtrail.amazonaws.com",
                ]
              + type        = "Service"
            }
        }
    }

  # module.sec_resources.aws_cloudtrail.main will be created
  + resource "aws_cloudtrail" "main" {
      + arn                           = (known after apply)
      + enable_log_file_validation    = true
      + enable_logging                = true
      + home_region                   = (known after apply)
      + id                            = (known after apply)
      + include_global_service_events = true
      + is_multi_region_trail         = true
      + is_organization_trail         = true
      + name                          = "main-prod"
      + s3_bucket_name                = (known after apply)
      + tags_all                      = (known after apply)
    }

  # module.sec_resources.aws_s3_bucket_lifecycle_configuration.log["cloudtrail"] will be created
  + resource "aws_s3_bucket_lifecycle_configuration" "log" {
      + bucket = (known after apply)
      + id     = (known after apply)

      + rule {
          + id     = "delete-old-files-prod"
          + status = "Enabled"

          + expiration {
              + days                         = 1
              + expired_object_delete_marker = (known after apply)
            }

          + filter {
            }
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].data.aws_iam_policy_document.baseline_bucket_policy will be read during apply
  # (config refers to values not yet known)
 <= data "aws_iam_policy_document" "baseline_bucket_policy" {
      + id                      = (known after apply)
      + json                    = (known after apply)
      + source_policy_documents = [
          + (known after apply),
        ]

      + statement {
          + actions   = [
              + "s3:*",
            ]
          + effect    = "Deny"
          + resources = [
              + (known after apply),
              + (known after apply),
            ]
          + sid       = "RequireLatestTLS"

          + condition {
              + test     = "NumericLessThan"
              + values   = [
                  + "1.3",
                ]
              + variable = "s3:TlsVersion"
            }

          + principals {
              + identifiers = [
                  + "*",
                ]
              + type        = "*"
            }
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket.main will be created
  + resource "aws_s3_bucket" "main" {
      + acceleration_status         = (known after apply)
      + acl                         = (known after apply)
      + arn                         = (known after apply)
      + bucket                      = "devshrekops-demo-cloudtrail-logs-prod"
      + bucket_domain_name          = (known after apply)
      + bucket_prefix               = (known after apply)
      + bucket_regional_domain_name = (known after apply)
      + force_destroy               = false
      + hosted_zone_id              = (known after apply)
      + id                          = (known after apply)
      + object_lock_enabled         = (known after apply)
      + policy                      = (known after apply)
      + region                      = (known after apply)
      + request_payer               = (known after apply)
      + tags_all                    = (known after apply)
      + website_domain              = (known after apply)
      + website_endpoint            = (known after apply)
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_ownership_controls.main will be created
  + resource "aws_s3_bucket_ownership_controls" "main" {
      + bucket = (known after apply)
      + id     = (known after apply)

      + rule {
          + object_ownership = "BucketOwnerEnforced"
        }
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_policy.main will be created
  + resource "aws_s3_bucket_policy" "main" {
      + bucket = (known after apply)
      + id     = (known after apply)
      + policy = (known after apply)
    }

  # module.sec_resources.module.log_baseline_s3_bucket["cloudtrail"].aws_s3_bucket_public_access_block.main will be created
  + resource "aws_s3_bucket_public_access_block" "main" {
      + block_public_acls       = true
      + block_public_policy     = true
      + bucket                  = (known after apply)
      + id                      = (known after apply)
      + ignore_public_acls      = true
      + restrict_public_buckets = true
    }

Plan: 6 to add, 0 to change, 0 to destroy.

Terraform apply initially failed with the following error:
Error: reading CloudTrail Trail (arn:aws:cloudtrail:us-east-1:533266992459:trail/main-dev): operation error CloudTrail: DescribeTrails, https response error StatusCode: 400, RequestID: 069a20a9-db35-4710-82d0-01c9306f1873, InvalidTrailNameException: Trail ARN is not valid: arn:aws:cloudtrail:us-east-1:533266992459:trail/main-dev. Account number does not match caller's account.

Afterward, the Terraform plan showed the CloudTrail resource as being tainted and in need of replacement:
Terraform will perform the following actions:

  # module.sec_resources.aws_cloudtrail.main is tainted, so must be replaced
-/+ resource "aws_cloudtrail" "main" {
      ~ arn                           = "arn:aws:cloudtrail:us-east-1:533266992459:trail/main-dev" -> (known after apply)
      ~ home_region                   = "us-east-1" -> (known after apply)
      ~ id                            = "arn:aws:cloudtrail:us-east-1:533266992459:trail/main-dev" -> (known after apply)
        name                          = "main-dev"
      - tags                          = {} -> null
      ~ tags_all                      = {} -> (known after apply)
        # (6 unchanged attributes hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

The trail was successfully recreated upon running terraform apply a second time.
I suspect this error has to do with the org trail being owned by the management account, despite it being created from the security account, but I'm not sure yet why it successfully created the second time. More research required.


add more CSIP implementation detail

In section 13, CSIP is mentioned:
An additional CLIC software interrupt bit (csip) is provided. This is generally available for software use, but is usually used for the local background interrupt thread.
12  csip        CLIC software interrupt
it was mentioned in the meeting 4/14/2020 that csip bit was intended to be located at bit 12 in the xIE/xIP registers.  but if this statement is also true:
The xIE and xIP CSRs appear hardwired to zero in CLIC mode. In systems that support both original
basic and CLIC modes, the state bits in xIE and xIP retain their value when switching between modes.
if the xIE and xIP registers aren't visible, it doesn't seem possible to set the csip interrupt in clic mode.

This topic is being covered by issue #89.  closing here.


CHANGES: strip trailing whitespaces

This simply strips out all trailing whitespaces in the CHANGES file.
As mentioned in #4552 by @dot-asm .
Checklist

Merged thanks.

Thank you @paulidale !


Account Secrets functionality

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #6   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          23     26    +3
=====================================
+ Hits           23     26    +3

Impacted Files
Coverage Δ

lib/nexmo/lib/account.ex
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ec1085...b76cd61. Read the comment docs.


how to verify RS256 signing algorithm?

I met a problem when I try to verify the JWT returned from Auth0. In Auth0, I use the client credentials to ask the token, as the result, the Auth0 returned me a JWT. In this case, I do not know how to verify it.
I met an another problem about Auth0 that the front-end send me (back-end) a token to request an API, but I have to transmit this token to Auth0 to verify it again. So far, I think I need to form a JWT to Auth0, but I do not know how to parse the previous JWT (authorize me, which is the above question). Who knows that?

You can and should verify the token on the frontend. This library exposes validation functionality but is lacking an example for Parsing/Validating RS256 tokens.
Ref Parse HMAC Example

Hi Karl, Thank you so much. I have already figured this problem out. At that time, I did not understand the authentication workflow in our project. I did the back-end part, so I can not do it on the front-end. The library I used are
jose "gopkg.in/square/go-jose.v2"
"gopkg.in/square/go-jose.v2/jwt"

, which save me a lot of time.
I found it from here, which is amazing.
Anyway, thank you so much bro.


Translate english/vue/components to Portuguese

Created a index.md file containing Portuguese translation for guide/english/vue/components/index.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Congrats @darthHunterous on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Standardise formatting for UG

Codecov Report

Merging #328 (06ffe84) into master (65cd2a2) will not change coverage.
 Consider uploading reports for the commit 961a46d to get more accurate results

@@            Coverage Diff            @@
##             master     #328   +/-   ##
=========================================
  Coverage     54.22%   54.22%
  Complexity      802      802
=========================================
  Files           142      142
  Lines          3535     3535
  Branches        507      507
=========================================
  Hits           1917     1917
  Misses         1471     1471
  Partials        147      147

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


As an internship applicant I can categorize each company according to the level of difficulty of their technical interviews

...so that I know which one I should spend more preparing for

Not implemented.


Enhancement: Clean up ZfModule\Controller\IndexController

This PR

[x] adds tests for ZfModule\Controller\IndexController
[x] extracts ApplicationTest\Integration\Util\AuthenticationTrait for mocking authentication in integration tests, provides authenticatedAs($identity) and notAuthenticated()
[x] cleans up ZfModule\Controller\IndexController

@Ocramius
I apologize for the length of this PR, especially having had to push the last 30+ commits in one go - I had no internet connection on the flight, so I spent some time on this.
Not sure about the tests - as I'm mocking a lot, maybe these should be unit tests in the first place?

There is some serious testing effort in here, but also the tests seem to be way too complicated/long right now: I suggest looking into that before merging.

@Ocramius
Applied a few changes, please have a look if you can!

Hi @localheinz but are you thinking a squash of commits for the future? :bulb:

@gianarb
Sure, no problem - once @Ocramius is fine with what I've got here, I'm happy to squash any time! Personally, I prefer smaller commits, but sure!

I don't know :) But maybe this is a good point of discussion..
Thanks for these improvements!

No squashing please.

Merging: the minor nitpicking I found can be fixed later (just push directly)

Thanks @localheinz!

Thanks a lot for having a look at this, @gianarb and @Ocramius!

I hope to see all operate in production :pray: :weary:


/css/datepicker/datepicker3.css

Hi,
check  /css/datepicker/datepicker3.css inclusion in head. File is not found

http://almsaeedstudio.com/AdminLTE/css/datepicker/datepicker3.css
http://almsaeedstudio.com/AdminLTE/js/plugins/datepicker/bootstrap-datepicker.js
those two link are die.. could you please re-upload again


Switch any remaining http to https

The gh pages page wasn't functioning through https because of the use of jquery from an insecure source.

You right! Thanks! :)


Use RHSysEng elastic deploymnt in CI

@pavolloffay This looks good, but in my initial attempt to get it to run on my own minishift instance I got this error in the ElasticSearch pod:
ERROR: [1] bootstrap checks failed
| [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
Can you tell me what I need to do to get past this?

@pavolloffay Now this is failing on the CNCF CI because it considers "max virtual memory areas vm.max_map_count [65530] is too low" to be an error instead of just ignoring it.

Elastic requires this limit, @kevinearls could you please fix it as soon as possible?

Wohoo I got Jenkins to pass. I will merge as it is approved. If there are any more comments I will handle them in a separate PR


add some additional checks to work modal window

Why was this change made? 🤔
Fixes #2624 - Add some additional cypress tests for the work modal

I see that what you added is perfectly analogous, but I don't see how this description:
```it('requires 0 subtypes for text type'``
is satisfied by
cy.url().should('include', `/collections/${collection_id}/works/new?work_type=text`)

Is it a poor description, or a poor test, or is the test missing a comment explaining why?

I'll add a code comment.  Basically the explanation is that you cannot proceed to that URL (which is the form where you actually create the new work) unless you satisfy the requirements of selecting the type.  This test shows that do not need to select any sub types in order to proceed.  A previous test (for a different work type, e.g. mixed materials) shows that when you click submit you will instread see a validation message and does not proceed to the form) until you select subtypes.

Added a code comment and one more test verifying that you must select a work type to proceed.


Having trouple converting the messages.

Hi. I'm trying to get my 6k messages over on my android, but the cmd shows some errors. Am I doing it wrong? What I get is this one.
Thanks in advance! :)

Traceback (most recent call last):
File "C:\Users\Kjartans\Downloads\Convert\sms-wp-to-android-master\convert.py", line 13, in
e = ET.parse(file_path).getroot()
File "C:\Python27\lib\xml\etree\ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "C:\Python27\lib\xml\etree\ElementTree.py", line 656, in parse
parser.feed(data)
File "C:\Python27\lib\xml\etree\ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "C:\Python27\lib\xml\etree\ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: reference to invalid character number: line 867, column 1064

I read through some of the other issues and I believe that it worked now.
Thanks a lot!  And if I only could do the same with MMS...


Use this library without angular?

Is it possible to use this library without using angular?

It's not possible.


SocketPlugin: keep CORS flag per server

Currently we always try a direct request first, and the proxied one second. In some situations this leads to considerable delay (e.g. 2 seconds on source.squeak.org).
We might want to keep a table of hosts and their need-proxy flag. Whenever a request succeeds we put a flag for that host in the table. When another request comes in and we have a flag already then we use the order (proxy/direct first) given by the flag, otherwise we try direct first.

Wouldn't it be better if we check the URL if a proxy is needed in the first place?

There is no way to know in advance if a server is CORS-enabled or not, you can only try. We do not want to use the proxy unless it is necessary.

True, and keeping track of URLs as suggested here would certainly speed up requests.
I'm happy to take care of this...


Soften requirement on Lasagne version

We may have a newer version installed (maybe a local checkout) that already
satisfies the requirement.

Hi @dnouri, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thanks Daniel!


whatsapp-for-mac on aarch64-darwin does not build

Describe the bug
When adding the package pkgs.whatsapp-for-mac to your nix-darwin config, it throws an http error. I am guessing something on whatsapp's side broke the package, but I could have also just done something stupid. If someone can clear this up for me I would be grateful.
Steps To Reproduce
Steps to reproduce the behavior:

add pkgs.whatsapp-for-mac to your aarch64-darwin config
run darwin-rebuild switch --flake .#whatever
HTTP error

Expected behavior
I expect the program to be downloaded and installed and that I can use it.
Screenshots
here are the short logs:
building the system configuration...
error: builder for '/nix/store/3flg997m0nk18jwpsp8zcn3pbj7nlq1x-WhatsApp.app.drv' failed with exit code 1;
       last 16 log lines:
       >
       > trying https://web.whatsapp.com/desktop/mac_native/release/?version=<IP_ADDRESS>&extension=zip&configuration=Release&branch=relbranch
       >   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
       >                                  Dload  Upload   Total   Spent    Left  Speed
       >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
       > curl: (22) The requested URL returned error: 500
       > Warning: Problem : HTTP error. Will retry in 1 seconds. 3 retries left.
       >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
       > curl: (22) The requested URL returned error: 500
       > Warning: Problem : HTTP error. Will retry in 2 seconds. 2 retries left.
       >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
       > curl: (22) The requested URL returned error: 500
       > Warning: Problem : HTTP error. Will retry in 4 seconds. 1 retries left.
       >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
       > curl: (22) The requested URL returned error: 500
       > error: cannot download WhatsApp.app from any mirror
       For full logs, run 'nix log /nix/store/3flg997m0nk18jwpsp8zcn3pbj7nlq1x-WhatsApp.app.drv'.
error: 1 dependencies of derivation '/nix/store/5cyjhm9bn9hn7ymz6qwxwvxp1cc03aqj-whatsapp-for-mac-<IP_ADDRESS>.drv' failed to build
error: 1 dependencies of derivation '/nix/store/nci4h6fyf4k8kcp76mdd5kv2f1z9j2kc-system-applications.drv' failed to build
error: 1 dependencies of derivation '/nix/store/yyia9g87n26ihzr7s24imfsjblv2siif-darwin-system-25.05.20241208.dd51f52+darwin5.a35b08d.drv' failed to build

Metadata

warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
 - system: `"aarch64-darwin"`
 - host os: `Darwin 24.1.0, macOS 15.1.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.24.10`
 - nixpkgs: `/nix/store/rml4w5lj8jxsnlddmy0r1bd4389fkdh7-source`

Notify maintainers
@iivusly

Note for maintainers: Please tag this issue in your PR.

I'm seeing exactly the same error on x86_64-darwin.


Where are the Extensions Stored?

Type: Performance Issue
I need to know where are the VS Code Extensions stored.  It is not in the VS Code subdirectory.
 Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


PoC: Try to fix memory leak of RefMutContainer when using infinite loop

I tested this patch on just simple test like below example yet,
>>> import rraft
>>> c = rraft.Config()
>>> r1 = c.make_ref()
>>> r2 = c.make_ref()
>>> c = None
>>> r1
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
rraft.DestroyedRefUsedError: Cannot use a destroyed object's reference!
>>> r2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
rraft.DestroyedRefUsedError: Cannot use a destroyed object's reference!
>>> c = rraft.Config()
>>> r1 = None
Object removed: '1'
>>> r2 = None
Object removed: '2'
>>> c
Config { id: 0, election_tick: 20, heartbeat_tick: 2, applied: 0, max_size_per_msg: 0, max_inflight_msgs: 256, check_quorum: false, pre_vote: false, min_election_tick: 0, max_election_tick: 0, read_only_option: Safe, skip_bcast_commit: false, batch_append: false, priority: 0, max_uncommitted_size:<PHONE_NUMBER>3709551615, max_committed_size_per_ready:<PHONE_NUMBER>3709551615 }
>>> r1
>>> r2

The Object removed: statement is for debugging.
FYI, It could be printed later than expected, for seeing this in this time, we could use gc.collect() here.


Skip PoloniexLevel when adapting order book

and save big on memory consuption when running with XStream
NB: also remove PoloniexLevel class

ok, ad the commit that removes PoloniexLevel, its not used any ware else


💡 Participate in Gitcoin Grants and Bounties

We can participate in Gitcoin Grants (https://gitcoin.co/grants/) to raise funds that we later use with Gitcoin Bounties (https://gitcoin.co/bounties/funder) to incentivize people to contribute to the project.

See Predictably Irrational - Chapter 4 The Cost of Social Norms for more info


debug across files

I was just thinking, what if we add a feature to parse Wow error file
so that it will do the obfuscation in the background, take the line/variable, then look it up in the clean code and 'mark' the lines

Something like this maybe?

For now, it processes the file with the same seed and applies the stack trace to get all the line/variable info. After that it tries to find it back. Unsure as to how we should identify the error in the clear code as transformation does leave not many artifacts behind.

This got landed in #5 :)

New Debug flag can be used to obtain a mapping of variable names. The minifier is designed (poorly) to allow each variable name to be unique, we can take advantage of that and create a unique mapping like so:


Fix Bug in Learn Logic Design Button Homepage

Fixes #
Learn Logic Design button will be on new line on mobile devices and on same line on desktop.
Describe the changes you have made in this PR -
I have made Learn Logic Design Button inline-block for desktop view and block for mobile view.
Screenshots of the changes (If any) -

@nitin10s @aayush-05 please review it

Coverage remained the same at 84.266% when pulling 8a93b3c76ecd8b179956720e34d052ba3bd61e4a on harshgujrati:bug/homepage into 4872e6f5d4355054c383207a8ed9e10b6ff1db7e on CircuitVerse:master.

Good to be merged @satu0king @tachyons

Can u add the issue number near fixes in the PR description


Slow to start

Is your feature request related to a problem? Please describe.
Pipenv is slow to start even with no arguments.
I had to remove this line from my .bashrc because I found it takes 2.7 secs to run, and it seems to be due to the fact that pipenv with no arguments takes 1.3 secs to start and print the help text.
eval "$(pipenv --completion)"
Describe the solution you'd like
Hoping this is low-hanging fruit. Perhaps this is an easy fix to move some of the initial configuration and setup to after some of the command line processing.
Describe alternatives you've considered
no comment
Additional context
Thanks! Pipenv is super useful; but it's become so important in my toolchain that subtle issues like this are a performance hit to my whole development cycle.

Please run $ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.
pipenv --support
Error: no such option: --support
pipenv --version
pipenv, version 9.0.1

Please first update your Pipenv version to the latest. There was a significant improvement against the startup time.

Thanks. The 2.7 sec is under about 0.9 sec now.  Note for me "time python foo.py" is about 0.1 sec for me.
:::: fang 07:15:08 (cgt-pubsub) 0 cron; time eval "$(pipenv --completion)"

real    0m0.947s
user    0m0.792s
sys     0m0.149s
:::: fang 07:15:11 (cgt-pubsub) 0 cron; pipenv --version
pipenv, version 2018.11.26

~1 second is still too much for me.
I ended up solving this with this workaround
eval "$(cat ~/.pipenv_completion)"
$(pipenv --completion > ~/.pipenv_completion &)

@madacol That is a VERY bad idea. You're spawning python processes in the background and overwriting the file every time you launch a shell. Launching multiple shells would cause multiple processes to write to the file at the same time.
There's a much better way to do this. You've almost got it above.
Step 1. Write the autocompletion code to a file or your shell init script.
Step 2. Load the autocompletion code into your shell init script.
I decided to write it directly into the shell init scripts. This is what that looks like. I use both ZSH and Bash on my system:
echo '# Add pipenv autocompletion' >> ~/.zshrc
_PIPENV_COMPLETE=zsh_source pipenv >> ~/.zshrc

echo '# Add pipenv autocompletion' >> ~/.bashrc
_PIPENV_COMPLETE=bash_source pipenv >> ~/.bashrc

Run this ONCE. Never again. The code it adds to your shell init scripts is generic and simply says "when user presses tab to autocomplete a pipenv command, grab the result via pipenv". If pipenv ever refactors the autocompletion to use other environment variables, you'll have to refresh this code. But most likely never.


Apply low-pass filter to RTF display

🎉 New feature
Follow-up from https://github.com/gazebosim/gz-sim/pull/1942
Summary
This adds a more aggressive low-pass filter than what was in gz-sim such that the RTF display is more stable and reflects the RTF of a longer window of time.
Test it
Run gz sim camera_sensor.sdf. The RTF will display is much more stable than before. After a while, remove the image display and watch the RTF increase.
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@iche033 I've made the filter less aggressive than what I had https://github.com/gazebosim/gz-sim/pull/1942 so that it is responsive to changes like the image display being removed while still providing a stable RTF reading.


feat: updates card design for kits and homepage

Type of change

[x] Feature
[ ] Documentation change
[ ] Bug fix

Summary of change

This updates the homepage and kit pages to reflect the option 1 selection in the Figma designs found in the Slack PTA channel

Updates the homepage to include more icons with a layout of 3x4 and adds a title for the kit
Adds a showcase section to individual kits with a View Showcase option that navigates to the section on the page
Adds updated keywords and icons from https://github.com/thisdot/starter.dev/issues/1283
Updates packages to reflect which kits have showcases
Resolves 2 failing checks

Screenshots
Homepage

Individual kit

Checklist

[x] These changes follow the contributing guidelines
[x] This starter kit has been approved by the maintainers
[ ] Changes for this new starter kit are being pushed to an integration branch instead of main
[x] All dependencies are version locked
[x] This fix resolves #1284
[x] I have verified the fix works and introduces no further errors

Awaiting feedback to:

column/rows
Remove duplicate logos

Light mode title is too light

Feedback to address:

Container squares feel too skinny add more lr padding

Make plural

Doesn't look good in light mode and feels too cramped in dark mode. Add more padding

Skinny container feels really bad because it doesn't left align with the rest of the page

Mobile, this should probably take the full width

Header styles on mobile are off especially with CTAs


📃: Add Mini Calender

🔴 Title :Add Mini Calender
🔴 Tech stack :HTML: Structure the calendar with a header for month/year navigation and a grid for days of the week and individual days.
CSS: Style the calendar for layout, colors, and hover effects to enhance the user interface and ensure it's visually appealing.
JavaScript: Add interactivity by handling month navigation, dynamically calculating the number of days in each month, and rendering the days accordingly.
This combination allows for a functional and interactive mini calendar.
🔴 Objective : A  "mini calendar" typically refers to a small, compact version of a calendar that displays a quick overview of dates, usually for a single month. It is commonly used in web applications, productivity tools, or desktop widgets to allow users to quickly view dates, select a day, or navigate between months. Here are some common functions of a mini calendar
🔴 Summary :Date Display: Shows the current month with all days listed in a grid.
Day Highlighting: The current day is often highlighted, making it easier to see today’s date.
Navigation: Arrows or buttons allow users to move to the previous or next month.
Date Selection: Users can click on a date to select it, which is useful for picking dates in forms, scheduling apps, or booking systems.

Hey @amanver45 I can work on this.
Please add labels (gssoc-extd , level , hacktoberfest) and assign this to me

Hi @iamrahulmahato ,
please assign me this..

@iamrahulmahato  duplicate nhi h wo issue bhi maine raise kiya tha lekin bad m close kar diya tha


Use https links.

Contributor checklist

[x] I have read the CONTRIBUTING.rst
[x] My contribution is ready to be merged as is

Description
Small documentation update. When links to external resources are provided use https instead of http.

Thank you! :-)


Add pointid parameter in FCNPC_GoByMovePath

native FCNPC_GoByMovePath(npcid, pathid, pointid = 0, type = MOVE_TYPE_AUTO, Float:speed = MOVE_SPEED_AUTO, bool:UseMapAndreas = false, Float:radius = 0.0, bool:setangle = true, Float:dist_offset = 0.0);

If added, I think it should be added as ast parameter so nothing will break code, like this:
native FCNPC_GoByMovePath(npcid, pathid, type = MOVE_TYPE_AUTO, Float:speed = MOVE_SPEED_AUTO, bool:UseMapAndreas = false, Float:radius = 0.0, bool:setangle = true, Float:dist_offset = 0.0, pointid = 0);

This planned for the next big update (version 2.0), and in this case compatibility doesn't matter. And I want to make more comfortable syntax for functions.

Done.


Fix certifying a domain for the first time.

Description
In #1411 I added the route53 kwarg to core.Zappa.get_domain_name but when I
actually went to use the arg in cli.ZappaCLI.certify I added it to the next
line down... This was because I had originally made the change in my project's
venv, just to see if it was as simple as it looked, and when it worked I
cloned the Zappa repo and reimplemented it. Obviously I messed that up.
As reported by @tamiel on #1411 the call to core.Zappa.create_domain_name was
throwing a TypeError because of the unrecognized keyword argument. This was
not getting caught in the integration tests around certify because the
mocked functions were taking variable arguments.
This commit fixes the original mistake and changes the mock in
tests.TestZappa.test_certify_sanity_checks to use mock.create_autospec
instead of a custom class so that it actually has the same function signatures
as a real instance would.
GitHub Issues
No issue raised yet but the problem was reported here: https://github.com/Miserlou/Zappa/pull/1411#issuecomment-370967045

Coverage remained the same at 74.323% when pulling 0cafc073f2fb1e876a080349bd83c89ad071ff5d on paulclarkaranz:recertify_nonroute53 into 8b1c5b838747959acbe4bd4b4c584cc126065edb on Miserlou:master.

Thanks, it works with existing domain now


Discord Link Appears to be invalid

Hi I'm looking to get some support with rules to validate if they're setup correctly.
I tried to join the discord but it looks like the link is invalid / expired. Could this be updated?

Are you talking about the one linked under Issues here? That one is working fine for me: https://toolscord.com/invite#WP4ZW2QYwk

Are you talking about the one linked under Issues here? That one is working fine for me: https://toolscord.com/invite#WP4ZW2QYwk

I have verified that the link is valid, and not expired.


Clarity on documentation

Hi
I am using spotlight with movieLens dataset to build a simple recommender system. Finding it hard to understand what some of the functions actually returns?
For example -
mrr = mrr_score(model, test)
The documentation says "One score is given for every user with interactions in the test set". What does this score means? Is it predicting something?
When I print the result, I get
MRR Score
[ 0.04613095  0.01775374  0.02144497 ...,  0.00335534  0.04208428 0.01965703]

Also, what does model.predict(user_id) predicts?
Again when I print, I get below results:

User 3
[-21.33734512  22.07717514  12.95882034 ..., -13.99704361 -10.88421345 5.03288126]

As per the documentation, the models output recommendation scores for user-item pairs. The mrr_score function outputs mean reciprocal rank scores (as per the documentation).
Is there something that's not in the docs that could be clarified?

@maciejkula Thanks, I have seen those earlier. What is not clear to me is how to interpret the results. For example, if model.predict(user_id) outputs a negative number, does that mean the model will rank that movie lower than if the output were a positive number?
Similarly, for mrr_score I understand it outputs mean reciprocal rank scores. But beyond the math, is it predicting something?

The higher the score, the stronger the recommendation (within the context of one user's ranking), so (as you say) negative numbers are worse than positive numbers.
For the MRR scores: it's ranking every item for a given user, the computing the MRR of the positive items in the test set. In that sense, it is constructing a ranking for each user (making predictions) and then computing the performance metric.


New version: RvSpectML v0.1.2

Registering package: RvSpectML
Repository: https://github.com/RvSpectML/RvSpectML.jl
Created by: @eford
Version: v0.1.2
Commit: 47da2de47047d2338c446e6db07ccd33aa8edaf3
Reviewed by: @eford
Reference: https://github.com/RvSpectML/RvSpectML.jl/commit/47da2de47047d2338c446e6db07ccd33aa8edaf3#commitcomment-43468539

[noblock]
Submitted PR for a v0.1.1 to make JuliaRegistrator happy.
Not there are pending PRs for subsequent versions:  https://github.com/JuliaRegistries/General/pull/23742 https://github.com/JuliaRegistries/General/pull/23819


get pinned messages

It seems it's not possible to see if a media is pinned to an user or not

just added a pr , u can use it :
https://github.com/adw0rd/instagrapi/pull/1260


Eero integration fails to set up

My eero integration had been working for awhile but then I was getting errors so I tried deleting and re-adding the integration. When doing this, I get the message "Failed to set up" and I see the following in the logs.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/eero/__init__.py", line 333, in async_setup_entry
    if any([eero.is_eero_beacon for network in coordinator.data.networks for eero in network.eeros]):
AttributeError: 'NoneType' object has no attribute 'networks'

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 191, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 150, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/eero/__init__.py", line 185, in async_update_data
    return await hass.async_add_executor_job(api.update)
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/eero/api/__init__.py", line 157, in update
    activity_data[resource][activity] = self.update_activity(
  File "/config/custom_components/eero/api/__init__.py", line 177, in update_activity
    start, end, cadence = self.define_period(period=ACTIVITY_MAP[activity][2], timezone=timezone)
  File "/config/custom_components/eero/api/__init__.py", line 73, in define_period
    start = now.replace(day=now.day-(now.weekday()+1), hour=0, minute=0, second=0, microsecond=0)
ValueError: day is out of range for month

Seeing the same issue here. Anyone find a solution?

I believe this should be fixed now in 1.2 but let me know if there's still concerns.


Adds pinproc files for Python 3.9

Adds the pinproc files for Windows on Python 3.9

https://github.com/missionpinball/mpf/pull/1707 This PR has the fix for the 2 failing tests, and it passed without issue.  I don't know if we can rerun tests after that PR is pushed through, if you want to proceed, since it doesn't touch tests, or if you want to reject and I can resubmit with the rebase of the other PR.  Just let me know!
Also, this ties to https://github.com/orgs/missionpinball/discussions/80


feat: DEV-232 Update example app to use session management

Updates the sample app to use session management.

Session data is stored in local cookie
Session data is checked on every request
Logout

https://user-images.githubusercontent.com/89937743/133175851-43414abc-dcf0-49cb-b0b5-ae330de7ada2.mp4

@linear-app[bot] can you help set up my account?
Sent from my TECNO CD7 using FastHub

@Max-Stytch mind doing a once over on the current state of this PR and merging if it looks good to you? I tested locally after updating to port 3000 and thinks look good to go.

Closing pending new work on Sessions.


Contents of noscript rendered

https://jsfiddle.net/q4mo2cph/
If you check the Network panel, you can see the img inside the noscript is (incorrectly) loaded when rendered with preact.

I use this pattern to lazy load images while also serving images to users without js via server-side rendering.

Interesting. I'm not sure if there is a way around this...

The browser (directly given some html) actually sets the content of noscript as innerText
https://jsfiddle.net/r0fe9spz/

Right, but this is VDOM - JSX elements only ever represent elements, not inert strings. Does this work (and not issue network requests) when rendered with React?

I got it working by using preact-render-to-string:
const noscriptImg = __SERVER__ ? renderToString() : ''
return (

)

It appears to trigger network requests in React too, FWIW.

Ahh that makes more sense. Maybe this warrants building your solution as a library? It doesn't seem like something Preact should handle out of the box.

This solution is fine. Thanks for talking through.  Doesn't seem to affect rehydrating the ssr'ed content either.


Move contributor ladder from drafts to live

Move contributor ladder to main branch
Rename to CONTRIBUTOR_LADDER.md
Fix typos

This continues changes from #9 in a separate branch from drafts, which is essentially "live" and shouldn't be used for PRs.

The last change that I made was to address @geekygirldawn 's comment about the missing word.
https://github.com/cncf/project-template/pull/11/commits/5277186c62fbdc095d8583e51cbb99d72ebf9e1c


Remove extra period from translation file

It's added on component building so it shows twice :)

What is your obsession with single line commits & PR's

What is your obsession with single line commits & PR's

Hey, someone had to do it :p

Hey, someone had to do it :p

Thanks!

Thanks!


incorrect output

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: windows 11
- Continue: v0.8.40
- IDE: vscode / webstorm
- LLM Model: deepseek-coder-v2:latest

Description
Hey,
This morning, I was trying to set up Continue in WebStorm. I wanted to fix something else, and I messed around with the settings and invalidated all the caches using the WebStorm IDE.
I don't know if they are related or not, but after that, I've been receiving weird responses from the model like this both in vs code and webstorm:

restarting the computer or closing and opening ollama desktop app solves this issue, but it keeps happening for some reason after working for about half an hour.

@MhL5 it seems like there's likely a problem outside of Continue—are you able to make curl requests to Ollama successfully?

I can use the model with ollama run deepseek-coder-v2:latest in the terminal, and it works. However, in VS Code, the output is incorrect until I close the Ollama desktop app and reopen it.
i need to investigate this more, I'm not sure where this is coming from

Just wanted to add I'm experiencing the exact same thing.  If I ask ollama via openweb-ui "explain this code:" I get back a great response.  When I try it in IntelliJ IDEA with continue I'm getting back gibberish. Maybe there is something wrong with the prompt?

@jmagder @MhL5 this is good to know, thank you. Can you share what your config.json looks like? It sounds like using openwebui instead of requesting directly requesting to Ollama might be causing issues, but I'm not certain yet

hey
this is my config: i had this issue for more than a week and couldn't figure out how to fix it yet.
worst thing is that this happens randomly
{
  "models": [
    {
      "title": "Ollama",
      "provider": "ollama",
      "model": "AUTODETECT"
    },
    {
      "title": "deepseek-coder-v2:latest",
      "provider": "ollama",
      "model": "AUTODETECT"
    }
  ],
  "customCommands": [
    {
      "name": "test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    },
    {
      "name": "step",
      "prompt": "{{{ input }}}\n\nExplain the selected code step by step.",
      "description": "Code explanation"
    }
  ],
  "tabAutocompleteModel": {
    "title": "deepseek-coder-v2:latest",
    "provider": "ollama",
    "model": "deepseek-coder-v2:latest"
  },
  "allowAnonymousTelemetry": true,
  "embeddingsProvider": {
    "provider": "transformers.js"
  }
}

Continue responds incorrectly, but Ollama works in terminal


Is it possible to add additional menus in the top?

Is it possible to add additional menus in the top? if you can, can you show an example?

Yes, of course you can.
In config file here, add your menus as the below.
customMenus:
  - name: "Blog"
    Url: "/blog"

  # Your menus
  - name: "your title"
    Url: "https://example.com"

thanks


Different results in testing

Describe the bug
The metrics from testing (using the best model) after training and validation is different when the same best model is used loaded using the cli command kit4dl test
To Reproduce
Steps to reproduce the behavior:

Train a model, and then run the testing after the training.
Use the best model saved to run the test for the same dataset.
The results from the above two procedures would be different.

Expected behavior
The metric from the test performed immediately after training and validation using the best model to have the same result as when the best model is used with the kit4dl test command.
Screenshots
Sadly no screenshots.
Setup (please complete the following information):

OS: Linux
Python version  Python 3.10.11
Conda packages (conda list result)
PIP packages  (pip freeze result)
Other relevant information

Additional context
None.

@jamesWalczak  Could you please comment on this?

@ShazAlvi are you sure to:

[ ] use the same TOML configuration file?
[ ] use the same checkpoint?

The procedures are quite the same:

Set-up Trainer using the conf TOML file
Prepare Trainer
Run testing
Hence, unless there is some side-effect during fit phase, the results should be quite the same (provided pseudo-random seed is set and the pytorch is in deterministic mode.)

The configuration file was the same, and also the checkpoint (I also tried the cases where there was only one checkpoint in the saved folder so there can be no confusion). I looked through the code and the procedures seemed to be the same. My only guess is that something happens when trainer.prepare() is called, but I do not have an idea what can go wrong. Otherwise, running kit4dl test twice gives exactly the same results.

ok. so kit4dl test is reproducible as i understood? And what are differences in loss and metrics for running test immediately after training and when kit4dl test is run?


Update Hash#shift RBI

Motivation
As outlined in this Ruby Bug, fixed in this PR, Hash#shift has been updated to return nil when the hash is empty. Previously it would return the value returned from hash.default(nil) which depending on the default_proc could produce weird results. This PR updates the Hash RBI so that shift now reflects the returned value as of 3.2
Test plan

See included automated tests.

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