Change in behavior once step ca claims are changed

Good morning,
Thanks to your help and that of Carl @ smallstep, I got my internal CA to work with win-acme using TLS-ALPN. The default configuration worked flawlessly with y  windows NUC for several weeks - all remote desktop login sessions worked as expected and I got no more "this certificate cannot be verified errors".  The Root CA and the pulled certificates showed up in the trust stores of Windows.
I then modified the step ca configuration JSON file to allow for longer-than-default (24hr) certificate durations. Below is the relevant section in the small-step config file regarding ACME.
{ "type": "ACME", "name": "acme" "claims": { "minTLSCertDuration": "5m", "maxTLSCertDuration": "96h", "defaultTLSCertDuration": "48h", "disableRenewal": false } }
These modifications from default (24hr) work fine for the TrueNAS (running FreeBSD). One of the smallstep devs confirmed that the JSON config looked good. However, for my  Windows NUC, I have two errors to report:

the NUC no longer uses the certificate from the tinyCA. Instead, it uses a self-generated one that is not trusted. The root CA is still installed in the root CA trusted store (as it was before I made changes to the JSON file).  I also tried revoking the extant certificate, delete the self-signed one, etc. all to no avail.
The auto-renewal process is 55 days instead of a day or whatever fraction Win-ACME usually uses to choose its own renewal interval.

How would you suggest I start to trouble-shoot the issue?

Here is a sample session with win-acme run as a admin in CMD on a windows 10 machine:
`C:\Program Files\Win ACME>.\wacs.exe --baseuri https://tinyca.internal/acme/acme/directory --verbose
[VERB] Verbose mode logging enabled
[VERB] ExePath: C:\Program Files\Win ACME\wacs.exe
[VERB] ResourcePath: C:\Program Files\Win ACME
[VERB] PluginPath: C:\Program Files\Win ACME
[VERB] Looking for settings.json in C:\Program Files\Win ACME
[DBUG] Config folder: C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory
[DBUG] Log path: C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Log
[DBUG] Cache path: C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Certificates
[DBUG] secrets.json not found
[VERB] Arguments: --baseuri https://tinyca.internal/acme/acme/directory --verbose
[DBUG] Renewal period: 55 days
[VERB] Sending e-mails False
[INFO] A simple Windows ACMEv2 client (WACS)
[INFO] Software version <IP_ADDRESS>9 (release, pluggable, standalone, 64-bit)
[INFO] Connecting to https://tinyca.internal/acme/acme/directory...
[VERB] SecurityProtocol setting: SystemDefault
[DBUG] Send GET request to https://tinyca.internal/acme/acme/directory
[VERB] Request completed with status OK
[DBUG] Connection OK!
[DBUG] IIS not detected
[DBUG] Running with administrator credentials
[WARN] Scheduled task not configured yet
[INFO] Please report issues at https://github.com/win-acme/win-acme
[VERB] Unicode display test: Chinese/語言 Russian/язык Arab/لغة
N: Create certificate (default settings)
M: Create certificate (full options)
R: Run renewals (0 currently due)
A: Manage renewals (0 total)
O: More options...
Q: Quit
Please choose from the menu: m
[INFO] Running in mode: Interactive, Advanced
[VERB] Adding <IP_ADDRESS> as DNS server
[VERB] Adding <IP_ADDRESS> as DNS server
[VERB] Adding <IP_ADDRESS> as DNS server
[WARN] Target plugin IIS not available: No supported version of IIS detected.
Please specify how the list of domain names that will be included in the
certificate should be determined. If you choose for one of the "all bindings"
options, the list will automatically be updated for future renewals to
reflect the bindings at that time.
1: Read site bindings from IIS
2: Manual input
3: CSR created by another program
C: Abort
How shall we determine the domain(s) to include in the certificate?: 2
[VERB] No value provided for --host
Description:        A host name to get a certificate for. This may be a
comma-separated list.
Host: nuc.internal
[INFO] Source generated using plugin Manual: nuc.internal
Suggested friendly name '[Manual] nuc.internal', press  to accept or type an alternative:
The ACME server will need to verify that you are the owner of the domain
names that you are requesting the certificate for. This happens both during
initial setup and for every future renewal. There are two main methods of
doing so: answering specific http requests (http-01) or create specific dns
records (dns-01). For wildcard domains the latter is the only option. Various
additional plugins are available from https://github.com/win-acme/win-acme/.
1: [http-01] Save verification files on (network) path
2: [http-01] Serve verification files from memory
3: [http-01] Upload verification files via FTP(S)
4: [http-01] Upload verification files via SSH-FTP
5: [http-01] Upload verification files via WebDav
6: [dns-01] Create verification records manually (auto-renew not possible)
7: [dns-01] Create verification records with acme-dns (https://github.com/joohoi/acme-dns)
8: [dns-01] Create verification records with your own script
9: [tls-alpn-01] Answer TLS verification request from win-acme
C: Abort
How would you like prove ownership for the domain(s)?: 9
[VERB] No value provided for --validationport
After ownership of the domain(s) has been proven, we will create a
Certificate Signing Request (CSR) to obtain the actual certificate. The CSR
determines properties of the certificate like which (type of) key to use. If
you are not sure what to pick here, RSA is the safe default.
1: Elliptic Curve key
2: RSA key
C: Abort
What kind of private key should be used for the certificate?:
[VERB] Flag --ocsp-must-staple not present
[VERB] Flag --reuse-privatekey not present
When we have the certificate, you can store in one or more ways to make it
accessible to your applications. The Windows Certificate Store is the default
location for IIS (unless you are managing a cluster of them).
1: IIS Central Certificate Store (.pfx per host)
2: PEM encoded files (Apache, nginx, etc.)
3: PFX archive
4: Windows Certificate Store
5: No (additional) store steps
How would you like to store the certificate?:
[VERB] No value provided for --certificatestore
[VERB] Flag --keepexisting not present
[VERB] No value provided for --acl-fullcontrol
[VERB] No value provided for --certificatestore
1: [My] - General computer store (for Exchange/RDS)
2: [Default] - Use global default, currently My
Choose store to use, or type the name of another unlisted store:
1: IIS Central Certificate Store (.pfx per host)
2: PEM encoded files (Apache, nginx, etc.)
3: PFX archive
4: Windows Certificate Store
5: No (additional) store steps
Would you like to store it in another way too?:
[WARN] Installation plugin IIS not available: No supported version of IIS detected.
With the certificate saved to the store(s) of your choice, you may choose one
or more steps to update your applications, e.g. to configure the new
thumbprint, or to update bindings.
1: Create or update https bindings in IIS
2: Create or update ftps bindings in IIS
3: Start external script or program
4: No (additional) installation steps
Which installation step should run first?:
[VERB] Targeted convert into 1 order(s)
[VERB] Checking [Manual] nuc.internal
[VERB] Handle order 1/1: Main
[VERB] Creating order for hosts: ["DnsName: nuc.internal"]
[VERB] Constructing ACME protocol client...
[DBUG] Send GET request to https://tinyca.internal/acme/acme/directory
[VERB] Request completed with status OK
[DBUG] No account found at C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Registration_v2
[VERB] No account found, creating new one
[VERB] Terms of service downloaded
Enter email(s) for notifications about problems and abuse (comma-separated<EMAIL_ADDRESS>[DBUG] Creating new ES256 signer
[DBUG] Send HEAD request to https://tinyca.internal/acme/acme/new-nonce
[VERB] Request completed with status OK
[DBUG] Send POST request to https://tinyca.internal/acme/acme/new-account
[VERB] Request completed with status Created
[DBUG] Saving signer to C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Signer_v2
[DBUG] Saving account to C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Registration_v2
[VERB] ACME client initialized
[DBUG] Send POST request to https://tinyca.internal/acme/acme/new-order
[VERB] Request completed with status Created
[VERB] Order https://tinyca.internal/acme/acme/order/Iwk8YMYJSDHI6QxDdG6U75T3h1VR3otg created
[DBUG] Send POST request to https://tinyca.internal/acme/acme/authz/C16Nq4kr7d4aAzHMIumuiCjBsG8Vu46g
[VERB] Request completed with status OK
[VERB] Handle authorization 1/1
[INFO] [nuc.internal] Authorizing...
[VERB] [nuc.internal] Initial authorization status: pending
[VERB] [nuc.internal] Challenge types available: ["http-01", "tls-alpn-01", "dns-01"]
[VERB] [nuc.internal] Initial challenge status: pending
[INFO] [nuc.internal] Authorizing using tls-alpn-01 validation (SelfHosting)
[VERB] Starting commit stage
[VERB] Commit was succesful
[DBUG] [nuc.internal] Submitting challenge answer
[DBUG] Send POST request to https://tinyca.internal/acme/acme/challenge/ViJrRQT5LgrrhY6iz8d14O6dUZmzOdU9
[VERB] Request completed with status OK
[INFO] [nuc.internal] Authorization result: valid
[VERB] Starting post-validation cleanup
[VERB] Post-validation cleanup was succesful
[DBUG] CSR stored at hu8jJvCRWEiCAQ4yZqDiAw-6519dc6991122f1999ad7ee2a10fca03acbf31a2-csr.pem in certificate cache folder C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Certificates
[VERB] Submitting CSR
[DBUG] Waiting for order to get ready (1/15)
[DBUG] Send POST request to https://tinyca.internal/acme/acme/order/Iwk8YMYJSDHI6QxDdG6U75T3h1VR3otg
[VERB] Request completed with status OK
[DBUG] Send POST request to https://tinyca.internal/acme/acme/order/Iwk8YMYJSDHI6QxDdG6U75T3h1VR3otg/finalize
[VERB] Request completed with status OK
[INFO] Requesting certificate [Manual] nuc.internal
[DBUG] Send POST request to https://tinyca.internal/acme/acme/certificate/uOQkx3kk0ADmc4O0GWZPVHEw5L7oszkn
[VERB] Request completed with status OK
[DBUG] Certificate written to cache file hu8jJvCRWEiCAQ4yZqDiAw-6519dc6991122f1999ad7ee2a10fca03acbf31a2-temp.pfx in certificate cache folder C:\ProgramData\win-acme\tinyca.internalacmeacmedirectory\Certificates. It will be reused when renewing within 1 day(s) as long as the --source and --csr parameters remain the same and the --force switch is not used.
[DBUG] Certificate store: My
[INFO] Store with CertificateStore...
[INFO] Installing certificate in the certificate store
[DBUG] Opened certificate store My
[INFO] Adding certificate [Manual] nuc.internal @ 2021/7/16 17:33:57 to store My
[VERB] CN=nuc.internal - CN=Tiny Intermediate CA (E04CFA882DF085C017A0B1C5E25C460EAA508D91)
[DBUG] Closing certificate store
[VERB] CN=Tiny Intermediate CA - CN=Tiny Root CA (E63374508A3103FE91947B6B2E22AD91DB1B57D2) already exists in CA
[DBUG] Closing store CA
[INFO] Installing with None...
[INFO] Adding Task Scheduler entry with the following settings
[INFO] - Name win-acme renew (tinyca.internalacmeacmedirectory)
[INFO] - Path C:\Program Files\Win ACME
[INFO] - Command wacs.exe --renew --baseuri "https://tinyca.internal/acme/acme/directory"
[INFO] - Start at 09:00:00
[INFO] - Random delay 02:00:00
[INFO] - Time limit 02:00:00
Do you want to specify the user the task will run as? (y/n*) -
[DBUG] Creating task to run as system user
[INFO] Adding renewal for [Manual] nuc.internal
[INFO] Next renewal scheduled at 2021/9/9 17:33:43
[INFO] Certificate [Manual] nuc.internal created
N: Create certificate (default settings)
M: Create certificate (full options)
R: Run renewals (0 currently due)
A: Manage renewals (1 total)
O: More options...
Q: Quit`

Note how Win-ACME wants to renew in September, not tonight or tomorrow as suggested by the ACME settings I used for my CA. So, where do I start to hunt down this behavior? Many, many thanks and hope all the best, CvW

If I force a renewal, the renewal succeeds but the renewal date is still wrong. See below
`C:\Program Files\Win ACME>wacs.exe --renew --baseuri "https://tinyca.internal/acme/acme/directory" --force
A simple Windows ACMEv2 client (WACS)
Software version <IP_ADDRESS>9 (release, pluggable, standalone, 64-bit)
Connecting to https://tinyca.internal/acme/acme/directory...
Scheduled task looks healthy
Please report issues at https://github.com/win-acme/win-acme
Force renewing certificate for [Manual] nuc.internal
[nuc.internal] Authorizing...
[nuc.internal] Authorizing using tls-alpn-01 validation (SelfHosting)
[nuc.internal] Authorization result: valid
Cached certificate available on disk but not used due to --force switch.
Requesting certificate [Manual] nuc.internal
Store step 1/2: CertificateStore...
Installing certificate in the certificate store
Adding certificate [Manual] nuc.internal @ 2021/7/16 20:36:03 to store My
Store step 2/2: CertificateStore...
Certificate with thumbprint D59FCFAF4C01B5C4F3C3E568F03CE61E9803DF73 is already in the store
Installing with None...
Uninstalling certificate from the certificate store
Removing certificate [Manual] nuc.internal @ 2021/7/16 17:33:57 from store My
Uninstalling certificate from the certificate store
Next renewal scheduled at 2021/9/9 20:36:02
Renewal for [Manual] nuc.internal succeeded`

the NUC no longer uses the certificate from the tinyCA.

You haven't configured any installation steps for your renewal, so whichever piece of software is expected to use the new certificate has no way of knowing something changed. You typically either run some kind of script to reconfigure your application(s) or if your application happens to be IIS then you can also use the built-in installation step.

The auto-renewal process is 55 days instead of a day or whatever fraction Win-ACME usually uses to choose its own renewal interval.

The default interval between renewals is 55 days regardless of actual validity of the certificate or frequency at which you run the scheduled task at (default once a day). This is probably not the most desirable state of things, but that's how it is. You can configure the interval in settings.json in the program directory.

Hi Wouter and thank you for your response.
The curious thing is that in the past, the certificates seemed to not only renew themselves at the right interval (no longer triggering  the "no trusted certificate" warning I experienced) but also made themselves automatically available to MS remote desktop. Hence my surprise and inquiry.
Thus, I thought that  win acme respected the certificate duration expectations by the CA automatically and set the renewal period for something like 2/3 of the claimed  "defaultTLSCertDuration", if a defaultTLSCertDuration is claimed by the CA. Perhaps that feature could be added to your code?
Anyhow, I must have configured my  certificate differently in the past, so I will have to investigate where windows RDS looks for certificates in the trust store. Thank you again for your help!
Constantin

v2.1.19 introduces new behaviour to renew based on the date the certificate actually expires, rather than purely based on a pre-configured interval. I believe this addresses the problem you ran into with your shortlived certificates.


[TypeScript] Made ReactCookie's typings more accurate

Made typing more accurate.
The compilation will fail if ReactCookieProps is not part of the component props when withCookies HOC wraps around the component.

@Guymestef Please review :-D

I moved index.d.ts outside of lib dir, and removed the declare module wrap. Otherwise, it wouldn't work. I tested locally by manually placing the modified index.d.ts (as seen in this PR) to directly under node_modules/react-cookie/, and it worked, whereas if I put it under node_modules/react-cookie/lib, it didn't work.

@eXon When you have time, could you take a look at this? I just want to make the publishing of typings more reliable. Happy to discuss.

Should be fixed in v2.1.5


human readable tag selection.

According to the current scipy paper and I assume docs the logical operator to filter tags on a Bundle is the type of the object I'm passing. While need as code this is actually hard to read. I'd appreciate some logical operators with some DSL supporting only or, and and nand (not and). Then one could filter with
b.tags['(building and furniture) nand paper']

This will only select oak and maple in the paper example. The current equivalent is unreadable and I'm not sure mine is correct.
b.tags[{['building', 'furniture'], ['paper']}]

Doing "building and furniture" will get an empty bundle in the paper example, since there are no Treants with both "building" and "furniture" as tags. If you want both oak and maple, you could do

('building' or 'furniture') and not 'paper'

which can be written as a tag expression as:
b.tags[[('building', 'furniture'), {'paper'}]]

I agree that these are a bit to get used to (and @orbeckst doesn't like them, either). I think we could benefit from a DSL as you suggested. It shouldn't be too hard to do with something like pyparsing, or building one similar to that in MDAnalysis.
Anyone else have any thoughts? @datreant/coredevs?

I’ll state for the record that I think that the boolean tag selections are an abuse of syntax.
However, I encourage David to present it at SciPy and see what the reaction is.

On 1 Jun, 2016, at 21:47, David Dotson<EMAIL_ADDRESS>wrote:
Doing "building and furniture" will get an empty bundle in the paper example, since there are no Treants with both "building" and "furniture" as tags. If you want both oak and maple, you could do
('building' or 'furniture') and not 'paper'
which can be written as a tag expression as:
b.tags[[('building', 'furniture'), {'paper'}]]
I agree that these are a bit to get used to (and @orbeckst doesn't like them, either). I think we could benefit from a DSL as you suggested. It shouldn't be too hard to do with something like pyparsing, or building one similar to that in MDAnalysis.
Anyone else have any thoughts? @datreant/coredevs?

I'll have a look at it. I always wanted to implement a small parser

On 1 Jun, 2016, at 23:49, kain88-de<EMAIL_ADDRESS>wrote:
I'll have a look at it. I always wanted to implement a small parser

Have a look at pyparsing!

In the same order of idea, it would be nice to be able to do the same with categories. Right now, the following would change my life:
new_bundle = bundle.categories['force_field == gromos53a6 and target_concentration > 100]

Yeah these don't seem intuitive, someone could naively put in a set of what they want (because they used a set operation to reach that point) and end up with the opposite of what they wanted. +1 for readable strings and scrapping this.

https://gist.github.com/kain88-de/9728e5b76082d9c3336ce840cb3195b5
I wrote an example parser based on a example in the pyparsing book.  Should be easy enough as a drop. Just run the parser when we find in getitem that the object is a string

I noticed that a parser with not, and and  or isn't easily transferable to datreants nand construct. The nand is also a bit of a clutch when I want to translate it to a normal string. If I want to negate just one  word  then nand word just doesn't make much sense. In general being able to work with a normal not would be nicer. But them might require to rething the set, list, tuple selection syntax

Totally random comment and probably besides the point but I vaguely remember something from Boolean algebra/circuits that you can create any logic gate from NAND gates only.
--
Oliver Beckstein
email<EMAIL_ADDRESS>
Am Jul 6, 2017 um 04:13 schrieb Max Linke<EMAIL_ADDRESS>I noticed that a parser with not, and and or isn't easily transferable to datreants nand construct. The nand is also a bit of a clutch when I want to translate it to a normal string. If I want to negate just one word then nand word just doesn't make much sense. In general being able to work with a normal not would be nicer. But them might require to rething the set, list, tuple selection syntax
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes with NAND one can rebuild all logic gates. The problem I had is just that {a, b}' is not the same as [{a}, {b}]and I still don't really know why. So the{}` might not implement a real NAND?

BTW I now have a implementation that works correct for me. I updated the gist with it.


added helm repo

added helm repo

@b-shj We have most of those manifests in https://github.com/oam-dev/terraform-controller/tree/master/chart, and a chart can be generated by make chart. What we need to do is to push the chart to some Helm chart repository.


How does this work with Parse Local Datastore?

The README should be updated with this information, since the use of cache policies are not permitted when LDS is enabled.

+1

Apologies, but this repo is no longer maintained. We don't use Parse anymore.

If you don't mind me asking, why not ?

Slow performance, non-transactional data store, cloud function limitations, poor security.


Core CLR support

Ref https://github.com/kevin-montrose/Jil/issues/183
There are some bits that will need to be revisited as Core CLR iterates to RTM, but this should be a viable build.
If possible, would like to get the -beta1 out onto nuget (with Sigil) as some folks  seem keen to try it; I can supply nupkg if tooling / machine setup is a blocker.

appveyor will almost certainly hate this, as the project files have moved; will need to update the appveyor configuration when happy to merge


Extending Network Service API further to allow for creating new Network Service Endpoints Dynamically

This is an extension of #531 and #532 that allows for dynamic creation of Network Service Endpoints.
  - match:
    sourceSelector:
        app: firewall
    create:
      - networkServiceEndpointTemplate: firewallTemplate
        scope: {CONNECTION,CLIENT,NODE,CLUSTER,REGISTRY}
        destroy:
          idleTimeout: 10m
    route:
      ...

This prompts the creation of a Network Service Endpoint based on a template at a particular scope:

CONNECTION - create a new Network Service Endpoint for each new Connection
CLIENT - create a new Network Service Endpoint for each new NSC if ones does not already exist.
NODE - create a new Network Service Endpoint on the Node where an NSC requests a connection if ones does not already exist.
CLUSTER - create a new Network Service Endpoint somewhere in the CLUSTER if ones does not already exist.
REGISTRY - create a new Network Service Endpoint somewhere in the scope of the Network Service Registery if ones does not already exist.

destroy indicates the conditions under which the Network Service Endpoint should be destroyed.
Please note, this is at the early ideation phase.  Don't implement this yet, but do discuss it :)

It can generally be determined by context but there is some fuzziness as to whether "NSC" refers to Network Service Connection or Network Service Client.

@tfherbert Good point :)


minttyrc too specific

For a general-use distribution, I would suggest not to include your personal preferences in a minttyrc file for deployment.

I replaced it with an empty one.


Permission Error despite having proper IAM configuration

Hi, I am receiving below error
"An error occurred (UnauthorizedOperation) when calling the DescribeInstances operation: You are not authorized to perform this operation"
i have verified everything, policies, credentials.  it is able to verify password policies, IAM users but giving error in listing resources.
what could be the cause? please help.

I would say that still a problem of permissions. What managed policies are you using? Remember at least SecurityAudit and ViewOnlyAccess.

Yes I aded securityaudit, and viewonlyaccess. for test purpose i gave adminstrator access also to this user. but still receiving same error.

can you run aws sts get-caller-identity and aws ec2 describe-regions --query 'Regions[].RegionName'? also share how are you running Prowler?

I was able to successfully run scan .  there is an SCP policy which was preventing this. Thank You.

Glad to hear that you managed to make it work. Thanks for let me know. I close the issue.


"Request had an error. Retrying."

Hello!
I am having an issue scraping this file: https://gis.adem.alabama.gov/arcgis/rest/services/UST_SWAA_FieldOps/MapServer/3
The error is: "Request had an error. Retrying."
Thank you!

Interesting, from the rest service metadata, it doesn't support geojson as a scraping type so I would need to add a JSON only variant to allow scraping. I can take a look at that later today and get back to you

I added support for json queries with #18 and tested the service you provided which allowed for csv scraping. Let me know if other services provide you with issues.


[Physics] Fix warning on copying a mesh with physics body

We need to pass the transform node of the body when cloning it.
Related forum issue: https://forum.babylonjs.com/t/havoc-problems-with-parented-meshes/40584/18?u=carolhmj
Test PG: https://playground.babylonjs.com/#Z8HTUN#396
In master, it displays these warnings:

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13951/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13951/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13951/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13951/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13951/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13951/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13951/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13951/merge#BCU1XR#0


[#2PlaysAMonth]: React Cart Management

React Cart Management
Hey Everyone👋
In this React Play I'm going to make a Shopping Cart Application that contains Beautiful UI designs along with proper state management while moving the items from Home Page to Cart and Vice versa. Attractive icons and animations will also be there.
Hope it will create a little amount of value in the community
Thankyou✔
What ReactJS concept will be used to create this play?
In this React Play I'll use

ReactRouterDom 👉 For routing different pages

ReduxToolkit  👉 to enable the state management of the Project

ReactComponents  👉 for User Interface

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Great. @SoumyadeepOSD can you please update the title?

Great. @SoumyadeepOSD can you please update the title?

@atapas  I recently updated the title✌ Thanks for informing about it

@atapas  I got so many errors while making the project in the reactplay. Can I change the subject of this issue and make a new Play ?


AnimateDiff is running abnormally, can you please take a look? AttributeError: 'AnimateDiffProcess' object has no attribute 'text_cond'

** Error executing callback cfg_denoiser_callback for D:\stable-diffusion-webui\extensions\sd-webui-animatediff\scripts\animatediff.py
Traceback (most recent call last):
File "D:\stable-diffusion-webui\modules\script_callbacks.py", line 230, in cfg_denoiser_callback
c.callback(params)
File "D:\stable-diffusion-webui\extensions\sd-webui-animatediff\scripts\animatediff_infv2v.py", line 163, in animatediff_on_cfg_denoiser
cfg_params.text_cond = ad_params.text_cond
AttributeError: 'AnimateDiffProcess' object has no attribute 'text_cond'
---version: v1.8.0  •  python: 3.10.6  •  torch: 2.0.1+cu118  •  xformers: 0.0.20  •  gradio: 3.41.2

This is currently happening with me on SD webui 1.8.0 but only when I use animatediff in conjunction with controlnet.

same issue

same here

same, anyone know how to fix?

same here

Delete your version of animateDiff and install fork https://github.com/light-and-ray/sd-webui-animatediff-
No errors for me


LTS table issues

I was looking on LTS table and I have found there some confusions:

(the same versions and different end dates)
https://framework.zend.com/long-term-support

In the case of zend-component-installer, there's no problem - the two entries for 1.0 are both relevant due to the different contexts (ZendSkeletonApplication vs zend-expressive-skeleton).
However, that first one, for zend-stdlib, is problematic, so I'll take a look and see if I can find a solution.


added neocollege

added new folder neocollege
Description

[x] I have added a folder(Named it as my GitHub user id)
[x] I have added a Readme.md file inside the folder
[x] I understand the GitHub Forking Concept fully

hello @atapas, could you please review this?


[JS] fix word segmentation bug when used on zh-CN

Purpose

fix word segmentation bug when used on zh-CN

Pull Request Type
What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Please update the ThirdPartyNotices.

Please update the ThirdPartyNotices.

Ok, updated

/azp run


[feature] Support custom profile photo at the commits page

Gogs version (or commit ref):
<IP_ADDRESS>8 / in docker

Database:

[x] PostgreSQL

Description
It would be good to have custom profile photo support at the commits page in case when user chooses a custom profile photo. Currently it points to the gravatar.
Thanks!
P.S.
I am new to Gogs (just installed), I might have overlooked something.

Can you give screenshots for exmaple?

@Unknwon here you go:

I think you do not have same email address?

@Unknwon Humm... that explains everything!
Thank you very much for the great product! :-)


setClass sets classes once

What is the reasoning for storing the class string in the setClass function (line 267)?
if (setClass.str !== str) {
	$box.add($overlay).removeClass(setClass.str).addClass(str);
	setClass.str = str;
}

In my particular use case, I the className option to set classes that eventually trigger css transitions.  For example, I set the option className = 'from-the-left' and the callback onComplete does something like: $('.from-the-left').addClass('open').  In the css, .from-the-left hides the element on the left and .open brings it in from the left (all of this using css translate3d).  Finally, at the callback onClosed, I remove both of these classes.
This works great the first time I trigger colorbox, but, because of the logic in setClass, the colorbox script doesn't set the classes again when its triggered the second time.
My solution right now is to just uncomment this logic, but I am curious as to why we have the logic in the first place.
Thanks,
Oscar G

If you were to open Colorbox again, while it was already open, then the quoted logic would check to see if the new option has a different className, and if so, remove the old one.  Colorbox has persistence in the DOM, rather than being replaced each time it is opened with new content, so the old class needs to be removed if the option has changed.  I failed to anticipate this class being removed by another means.  You should be able to do something like this:
if (setClass.str !== str) {
    $box.add($overlay).removeClass(setClass.str);
    setClass.str = str;
}
$box.add($overlay).addClass(str);

Or you could probably use the onOpen callback to set your class instead.

Thanks for the response, @jackmoore
I'll use onOpen instead of modifying the source.


There should be an easy method to add extra kernel config in your configuration.nix file.

Soooo... It seems that the kernels are built without taking into consideration system.requiredKernelConfig. If I have a package which requires a certain non-standard kernel feature to be enabled, or want to disable unnecessary features for size/performance/security in my configuration.nix, I should be able to do it in a nice way.
Related to PR "[WIP] linux: translate kernel config to structured config" #12158

(triage) has this been added?

Related :

https://github.com/NixOS/nixpkgs/pull/55755
https://github.com/NixOS/nixpkgs/issues/41103

Doesn't #42838 solve this?

Ops' opening:

It seems that the kernels are built without taking into consideration system.requiredKernelConfig

is adressed by https://github.com/NixOS/nixpkgs/pull/55755 which is just a PoC. Hoping to get some feedback before cleaning up (now that the "koi" release is out, we may get more).

still care


Prepare release v2.5.0

Release for BCD 5.6.12. https://github.com/web-platform-dx/web-features/compare/v2.4.0...HEAD
As of 69d71c4a62cbc9797bafb74f3c4647a371974fd6:

7 new features
64.1% coverage of BCD

Superseded by https://github.com/web-platform-dx/web-features/pull/2194.


feature: support tapBackspaceKey and tapReturnKey

[X] This change has been discussed in issue #1039 and the solution has been agreed upon with maintainers.

This PR adds support for pressing the backspace and return keys on both iOS and Android. Although iOS support exists by using typeText and the \b and \n keys, this was unclear and not cross-platform. The pressBackspaceKey and pressReturnKey methods abstract these features for both platforms.
Note: I did try adding a numberOfTimes parameter as a shortcut for pressing the backspace or return key multiple times, however I wasn't able to figure out the simplest way for executing multiple actions:
For both Android and iOS, the addition numberOfTimes for pressReturnKey is pretty straightforward:
async pressReturnKey(numberOfTimes = 1) {
  if (numberOfTimes && typeof numberOfTimes !== 'number') { throw new Error('...') }
  return await new ActionInteraction(this, new TypeTextAction('\n'.repeat(numberOfTimes))).execute();
}

For pressBackspaceKey on iOS, it can be implemented the same way as return, replacing \n with \b. For Android, however, I'm not sure how to invoke multiple PressKeyActions. Either way, I think this can be added in a follow up PR if it's determined to be useful.
cc @LeoNatan

Fantastic, thank you!
Would I trouble you much if I ask to name them tap...? It was my fault with the press in the issue, but on iOS that has different meanings. Tapping is the agreed upon terminology for iOS and Android.

Done @LeoNatan.

Looks good to me. Let's wait for @rotemmiz review as well.

@rotemmiz Any idea when you'll be able to get to this? It's a blocker for my team moving to Detox (which we'd love to do asap)

Looks great! Let's just add a few lines of documentation in https://github.com/wix/Detox/blob/master/docs/APIRef.ActionsOnElement.md

Amaze!

@rotemmiz @LeoNatan Are we good to go?

Thank you!

Any timeframe on when this will be released?

After a few inconsistencies with lerna 3, and some faulty release, you can now find your changes in<EMAIL_ADDRESS>


[swift-driver] Make checked build-record paths in many tests insensitive to ./ prefix

The swift-driver normalizes relative paths with the effect that an input file "./main.swift" gets written to a build record entry as "main.swift", without the "./". Remove the check of that part of the path from those tests in Driver/Dependencies where it is easy to do so, in service of getting the new driver to pass.

@swift-ci please smoke test

@artem , Sorry for the bogus messages! The intended person has corrected me. Please forgive me. Thanks.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test linux platform


text-on-X-token isn't respected inside alert containers in dark-mode

Current Behavior
light-mode

dark-mode

Steps To Reproduce
Use the skeleton theme, and turn on dark-mode

Warning

Anything else?
It seems that .dark .variant-filled-warning doesn't set the text-color.
.dark .variant-filled-warning {
    --tw-bg-opacity: 1;
    background-color: rgb(var(--color-warning-500) / var(--tw-bg-opacity));

    /* Note that `color` is missing */
}

.variant-filled-warning {
    --tw-bg-opacity: 1;
    background-color: rgb(var(--color-warning-500) / var(--tw-bg-opacity));
    color: rgb(var(--on-warning));
}

This causes .dark .alert to override the text color
.dark .alert {
    color: rgb(var(--color-surface-50));
}

Note that this is not a blocker. A temporary workaround is to manually add text-on-X-token to the alert message

Warning

Here's the issue:
https://github.com/skeletonlabs/skeleton/blob/dev/src/lib/styles/variants.css#L48
Exactly as you described, it's setting the default text color, but not the dark: variant. Should be an easy fix.
Thanks for the heads up.

I've assigned this ticket to you per our discussion on Discord. Thanks!


Having trouble getting this to work

I tried to get this working by following the steps listed, but when its set up the only text displayed is [ TRANSLATING HERE ]
Is there something i missed?
If you could help i can be reached at<EMAIL_ADDRESS>if github doesnt give me a notification

Same here, did you find a solution?

Having the same problem. Does not recognize input.

You only need the google scripts information. Whatever is going on with the pinata thing is unnecessary and doesn't work. TRy this instead (from the original author/page), as it worked for me:
https://sayonari.coresv.com/ninshikiChan/text.html?recog=en&trans=ja&bgcolor=black&size=20&weight=900&color=white&st_color=red&st_width=2&v_align=bottom&gas_key=XXXXXXXXXXXXXXXXXXXX(YOUR GOOGLE APP SCRIPT CODE HERE)XXXXXXXXXXXXXXXXX
I don't think this guy knows what he was doing, and the 'demo' VOD has been removed. I used this YT video as a reference to find the solution: https://www.youtube.com/watch?v=DIQ6E74dbMA&t=242s
@ShoesCat @ablodi
hope this helps

You only need the google scripts information. Whatever is going on with the pinata thing is unnecessary and doesn't work. TRy this instead (from the original author/page), as it worked for me:
https://sayonari.coresv.com/ninshikiChan/text.html?recog=en&trans=ja&bgcolor=black&size=20&weight=900&color=white&st_color=red&st_width=2&v_align=bottom&gas_key=XXXXXXXXXXXXXXXXXXXX(YOUR GOOGLE APP SCRIPT CODE HERE)XXXXXXXXXXXXXXXXX
I don't think this guy knows what he was doing, and the 'demo' VOD has been removed. I used this YT video as a reference to find the solution: https://www.youtube.com/watch?v=DIQ6E74dbMA&t=242s
@ShoesCat @ablodi
hope this helps

Thank you so much! I'll try this !

does it work for you ?


Fix deprecated error: http://i.imgur.com/HKCk2JR.png

Have a look at #95 for a different solution.

Hey  @mosiyash first apologize for the delay.. I have accepted changes from #95 as it's slightly better. By the way appreciate your involvement, thanks!


Filter tasks by pid namespace

Following the idea of filtering tasks by cgroupv2 I'm writing this to explore the idea to add to bpftrace the ability to filter tasks based on their belonging to a specific namespace.
The easiest use case that comes to mind is the ability to use a pid namespace to determine wether a task should or should not be considered, let's see how it looks like when used in bashreadline.t
BEGIN
{
	printf("Tracing bash commands... Hit Ctrl-C to end.\n");
	printf("%-9s %-6s %s\n", "TIME", "PID", "COMMAND");
}

uretprobe:/bin/bash:readline /nspid == nspid("/proc/1234/ns/pid")
{
	time("%H:%M:%S  ");
	printf("%-6d %s\n", pid, str(retval));
}

What I expect as output from this is the actual list of executed bash commands in that container.
This should be doable on kernels > 4.8 by leveraging bpf_get_current_task to obtain the children and then traverse that until we find the matching internal  processes struct task_struct to get the pids  of the  processes contained in our pid namespace so that we can filter them and use the internal pid for the pid variable.
Adding this will also require to have a mechanism to figure out the binary to attach the uprobe from a namespaced point of view.

Yes @dalehamel that's very similar to what I have in mind, however I also wanted to explore a way to implement this completely in bpftrace since that is also how a number of bcc programs do that like:

https://github.com/iovisor/bcc/blob/b0bf04ac4042a6c004b15dcc5e40e12ae78020f9/tools/solisten.py#L104
https://github.com/iovisor/bcc/blob/b0bf04ac4042a6c004b15dcc5e40e12ae78020f9/tools/runqlat.py#L238

In the meanwhile, those that can enable cgroupv2 in their kubernetes cluster can do the filtering using the cgroupid function:
APP=front-end
POD=$(kubectl get pod -n sock-shop -l name=$APP -o jsonpath='{.items[0].metadata.name}')
NODE=$(kubectl get pod -n sock-shop -l name=$APP -o jsonpath='{.items[0].spec.nodeName}')
CGR=/sys/fs/cgroup/unified$(kubectl exec -ti -n sock-shop $POD \
                              cat /proc/1/cgroup|grep ^0:|cut -d: -f3|tr -d '\r\n')

kubectl trace run --attach --serviceaccount=kubectltrace \
          $NODE
          -e 'kprobe:do_sys_open* /cgroup == cgroupid("'$CGR'")/ \
                { printf("%s: %s\n", comm, str(arg1)) }'

kudos to @alban - he wrote that example down for his talk at fosdem, he also has a guide on how to enable cgroupv2 in a kubernetes cluster https://gist.github.com/alban/6b6eee36e042d947c0c550b0dacced52

Thanks for the tip regarding the cgroupid, but I was under the impression that cgroups mapped more or less 1:1 to container, and could (and often do) differ within a pod. I'll give this a shot though and check my assumption. I did a quick search of the docs:

The shared context of a pod is a set of Linux namespaces, cgroups, and potentially other facets of isolation - the same things that isolate a Docker container.

But the wording there is "set of namespaces". From my poking around /proc I seem to recall that the pid namespace (and network, unless using host networking) was the most reliable shared namespace to map 1:1 to a pod.
In your example, the inline call to kubectl exec there would not work if there are multiple containers in the pod, you would need to specify which to probe. This is how other kubernetes things work, and that is totally reasonable (you would just need to specify which container to probe), but the subtlety is that I think there is a lot of applications where you would want to probe all containers in a pod, and only narrow down to a particular container later in debugging.
I'm eager to try this out though, I recall from a bcc issue that Brendan Gregg suggested something similar (though he was talking about containers, and not pods), and I think it (at the minimum) can be used to build a reasonable workaround until something filtering directly on the pid namespace can be implemented.

under the impression that cgroups mapped more or less 1:1 to container, and could (and often do) differ within a pod

FWIW I did a spot check, two containers in the same pod, and they did use the same cgroup namespace. This could mean that as long as you default to the first container in the pod that you are ok to use cgroup as the identifier for the pod.
I'm not sure if this is enforced, or is a coincidence / luck for the pod workload I examined. Either way, this seems more promising than I initially thought.
And in fact, the pid namespace was different between these two pods : / perhaps cgroup is better for this after all

@fntlnz can work on cgroups v1?

Any progress here? I'm trying to use bpftrace to monitor activity inside containers but not on the host system. I've been able to achieve this with bcc by creating a bpfmap. Is it possible to do the same here?

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。

kubepro@kubepro:~/$ sudo bpftrace syscall_filter.bt
syscall_filter.bt:2:1-16: ERROR: syntax error, unexpected map, expecting {
@container_pids = {}; // Map to store container PIDs and their names
kubepro@kubepro:~/sentinel_786$
kindly help me to resolve this issue


[docs] add match documentation on how to use basic authorization with GitHub tokens

Checklist

[ ] (NOT APPLICABLE) I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] (NOT APPLICABLE) I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Currently it's really confusing how to use HTTPS Basic authentication with GitHub Personal Access Tokens. The most obvious way implied by the docs, inserting the personal access token as MATCH_GIT_BASIC_AUTHORIZATION doesn't work and generates the following error in CI environments:
fatal: could not read Username for 'https://github.com': terminal prompts disabled

Other people have been bit by this, such as https://github.com/fastlane/fastlane/pull/17737#issuecomment-739965958 and potentially https://github.com/fastlane/fastlane/issues/17347.
I spent 15–30 minutes investigating this; reading the RFC, the GitHub documentation, and using curl -v. It would be helpful if we actually included documentation on how to do this for the next person.
Description

Added instructions to the "Git Storage on GitHub" section of the match docs. I tested this with my own account.
Testing Steps

You can test this with your own account by creating a GitHub personal access token, running the base64 command as described, and providing it as the MATCH_GIT_BASIC_AUTHORIZATION environment variable or git_basic_authorization
parameter.
I imagine whomever wrote this must have gone through this exact same process and just not documented the steps because they seemed obvious to them; or they glossed over the details without testing them, assuming they could paste in the personal access token as "<YOUR KEY>".

@googlebot I signed it!

@googlebot I signed it!

Please merge this. I just followed these docs instead of the current ones and my github cloning finally works. Kinda ridiculous how wasn't in the docs in the first place!
I would also suggest:

Adding a link to the personal token creation guide: https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
Specifying which permissions need to be given to the token, mainly all the "repo" permissions

Great PR, saved my life!

Please merge this. I just followed these docs instead of the current ones and my github cloning finally works. Kinda ridiculous how wasn't in the docs in the first place!
I would also suggest:

Adding a link to the personal token creation guide: https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
Specifying which permissions need to be given to the token, mainly all the "repo" permissions

Great PR, saved my life!

FYI still not seeing it on the website.

It's updated on my end, probably just a caching issue?

Ah, you're probably right. I see it now. :)


Add await to bot.handler.propagate(message)

Description
bot.handler.propagate(message) was not awaited in the example in line 27 and does not work without it

Please fix all examples while you are at it

Please fix all examples while you are at it

Let me go through and check, but I think the other ones had it, and it was just that example

I checked through the rest of the examples and fixed it.
Didn't notice them before

Thanks for this.


[Feature Request] VIN/Serial Number Field for Vehicles (Besides Custom Fields)

Checklist
Please make sure you have performed the following steps before opening a new bug ticket, change [ ] to [x] to mark it as done

[x] I have read and tried the steps outlined in the Troubleshooting Guide
[x] I have searched through existing issues.

Description
Request to add a VIN/Serial Number Number Field for Vehicles. I know you can make a custom field for this but doing so does not show it on the Garage Homepage nor exempt you from entering a License Plate in the case of Mowers, ATVs, Tractors, Etc. Yes, you can enter it in the license plate field, but what if you want to enter both the VIN and the License for a car.
What I see it being is when editing/creating a vehicle there is two fields, one for the license plate and one for the VIN/Serial. It is mandatory to fill out one of the fields but doesn't give you an error when leaving the other blank, and if you enter both, you can select which one displays on the Garage Home page.
Screenshots(optional)

I will do you one better.
In the next release, there will be a dropdown that will let you select which field should be the identifier, you can choose from "License Plate" and any other extra fields you have set up.

If you select any field other than "License Plate" then the License Plate will be optional, BUT the selected field must not be emtpy.

If license plate is selected and VIN is not a required extra field

If license plate is selected and VIN is a required extra field

Anyways, once you have selected the field you want displayed, then it will display the value of that field everywhere license plate used to be displayed:
Garage:

Vehicle View:

Calendar:

Released.

Is this definitely done? I don't see this feature in the most recent windows version at all

@wkosmos it is, you need to have an extra field at the vehicle level for this to work


iphone simulator timeout fix

Fixes a bug in Xcode when the iPhone simulator times our after 120 seconds.
xcodebuild[54591:624937]  iPhoneSimulator: Timed out waiting 120 seconds for simulator to boot, current state is 1.
Changing xcodebuild test to xcodebuild build test fixes the issue. In that case the build time is not calculated into the boot time.
Related radar link: https://openradar.appspot.com/22413115
Repository to reproduce: https://github.com/bitrise-io/simulator-launch-timeout-includes-build-time

Nice catch ! Didn't know that was the cause, always started the simulator before running tests on slow machines after Xcode 6. You should fix the unit tests before @KrauseFx could approve your PR.

Thanks, it should work now :)

@KrauseFx I'll investigate #502 and remove the changes if it solves this.

Looks good, thanks for the pull request @birmacher :+1:


qemu: add support for pidfile option

Add input for -pidfile option of qemu, so that we can get pid of
qemu main process, and apply resource limitations to it.
Fixes #62
Signed-off-by: l00397676<EMAIL_ADDRESS>

Coverage increased (+0.01%) to 80.405% when pulling 10c36a13da29ba68405db0d7a103b723b6fd957c on jingxiaolu:add_pidfile into e82e8498c5a214b24ac75e0a05ace556bf91a9ab on intel:master.

Coverage increased (+0.01%) to 80.405% when pulling 10c36a13da29ba68405db0d7a103b723b6fd957c on jingxiaolu:add_pidfile into e82e8498c5a214b24ac75e0a05ace556bf91a9ab on intel:master.

Seems reasonable to me and quite useful.  Does --pidfile work in conjunction with --daemonize?
@sboeuf , @mcastelino any comments on this?

Thanks @markdryan and @mcastelino :+1:


Apply Putty Session Profiles to items within a folder

I think It would be great to be able to apply one profile to all items within a
folder.
i.e. I work with servers from a range of different customers and save my logs
to folders named after the customer. I also follow the same structure for the
hosts in SuperPutty. It would be great if I could apply a Putty Profile to all
of the hosts within a folder, at onece, for changes that affect all of them.
Thanks!

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 22 Aug 2012 at 9:12

Closing this issue but all hope is not lost! We still want to help.
See: https://github.com/jimradford/superputty/wiki/Legacy-Imported-Issues on how to help us to help you!


feat: pseudo code version

this is a first version of the code for the p2p trading.
The maker = the one creating the order
The taker = the one accepting the order
for now you have 3 systems:
(summarized by chatgpt)

CreateOrder: the maker can create an order by specifying the amounts of resources its willing to swap. An array of entities that will be used in the maker caravan needs to be specified as well. If not enough units for the total weight, free units are used.
AcceptOrder: a taker can accept the order by also specifying the units that will be used in the caravans. If not enough units for the total weight, free units are used. When taker accepts the order, both the taker and maker caravans can start travelling.
ClaimOrder: both the maker and taker can call this system in order to verify that the caravans arrived at the destination, if that's the case the swapped resources can be added to their balance.

CreateOrder

The function takes several input parameters, including the maker's ID, resource types and quantities, expiration time, and a list of entity IDs representing a caravan.
The function calculates the total weight of the maker's resources based on the provided resource type and quantity.
It generates a unique order ID using the commands::uuid() function.
The function iterates over the caravan entities and determines if they can carry the remaining weight of the resources. If a caravan unit can carry the weight, it is attached to the order entity.
If the capacity limit is reached, additional free transport units are created and attached to the order entity.
The order entity is created and filled with relevant information, including the maker's details, resource type and quantity, caravan count, expiration time, and order status.
The function asserts that the maker has enough resources in their realm balance.
The maker's realm balance is updated by subtracting the resource quantity of the order from the current balance.

AcceptOrder

The function takes several input parameters, including the taker's ID, the order ID, and a list of entity IDs representing a taker caravan.
The function performs various assertions to validate the inputs, such as checking if the taker is a realm entity and if the caller is the owner of the taker realm.
The function calculates the current block timestamp using the get_block_timestamp() function.
The function iterates over the taker caravan entities and determines if they can carry the remaining weight of the resources. If a caravan unit can carry the weight, it is attached to the order entity.
If the capacity limit is reached, additional free transport units are created and attached to the order entity.
The function calculates the average speed of the taker caravan units based on their total speed and quantity.
It calculates the arrival time of the taker at the maker's position and updates the taker caravan units' arrival times accordingly.
It calculates the arrival time of the maker at their own position based on the maker caravan units' speed and quantity.
The function updates the maker caravan units' arrival times accordingly.
It checks if the taker has enough resources in their realm balance to fulfill the order and updates the balance by subtracting the taker resource quantity.
The function updates the order entity with the maker's details, resource type and quantity, arrival times, taker details, and order status as "ACCEPTED".

ClaimOrder

The function takes two input parameters: entity_id and order_id.
The function performs various assertions to validate the inputs, such as checking if the caller is the owner of entity_id and if entity_id is a realm entity.
It retrieves the order details from the Order entity using the order_id.
The function retrieves the current block timestamp using the get_block_timestamp() function.
If the caller is the maker of the order, it verifies that the taker's resources have arrived at the maker's realm by checking the taker's arrival time.
It adds the taker's resources to the maker's resource balance by updating the balance of the specified resource type.
It sets the taker's resource quantity to 0 in the order entity to prevent the taker from claiming it again.
If the caller is the taker, it verifies that the maker's resources have arrived at the taker's realm by checking the maker's arrival time.
It adds the maker's resources to the taker's resource balance by updating the balance of the specified resource type.
It sets the maker's resource quantity to 0 in the order entity to prevent the maker from claiming it again.

simple trading system for fungible entities = entities that can be defined by only their entity_type (resource, food, coins) and their quantity.
Feats:

create and add caravans independently of the order creation
possibility to trade between 2 entities on the same position
can trade list of fungible entities against list of fungible entities


[install.sh] fix for azk's install script

Changed terminal output to be more concise
Fix some issues to fedora installation ( it was missing sudo ).
Supports fedora 21 ( just worked )

This close #301 and is referred to #248, #117 and #272.

LGTM on OS X \o/

LGTM on OS X


Minor fixes and enhancements

Fixed: Wrong flash error message shown when task is completed
Fixed: build assets command in README.md
Ignored: migrations schema-dump-default.lock file
Added: website links for each tech used

@markstory I tried to fix tests, but looks like there's some dependency issues. So I'll leave it to you to fix.

@markstory I tried to fix tests, but looks like there's some dependency issues. So I'll leave it to you to fix.

@ishanvyas22 The tests are totally not done yet. I only published the repo last night and checking github actions locally is hard. I will fix up the tests soon

@ishanvyas22 The tests are totally not done yet. I only published the repo last night and checking github actions locally is hard. I will fix up the tests soon


[BUG] Notebooks data grid on full screen gets hidden by OSD header

What is the bug?
Notebooks data grid on full screen gets hidden by OSD header.
How can one reproduce the bug?
Steps to reproduce the behavior:

Go to Notebooks Plugin in observability
Click on Add sample
Load sample notebook [Logs] Sample Root Cause Event Analysis click on any data grid table and select fullscreen option
You would see an overlap in the in table headers and sometimes even few rows.

What is the expected behavior?
There should be an overlap and all rows must by visible
What is your host/environment?

OS: 2.5.0
Version 2.5.0
Plugins Observability

Do you have any screenshots?

Do you have any additional context?
This is dependent on OSD issue: https://github.com/opensearch-project/oui/issues/1166

We have added a temporary fix for now until Oui is fixed or has a way forward.


i can not use the live share option so please help me out

Before filing a new issue, check that it's not already captured by one in this list
Product and Version [VS/VSCode]:
OS Version [macOS/Windows/Linux]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
What were you doing when you encountered the desync?
How often have you encountered desyncs?
Do the host and the guest have the same contents?
If yes, there's no need to answer the following questions
If you are using VS Code, the following will provide helpful information.
On both the host and the guest:

Enable the liveshare.diagnosticMode setting
Open the file that's out of sync
Run the liveshare.getCoeditingInformation command (ctrl+shift+p to open the command palette, then search for "Get co-editing information") and paste the results below

Host co-editing information:
Guest co-editing information:
To check that messages are being sent and received, open the Output view (ctrl+shift+u) and select "Visual Studio Live Share Coediting" from the dropdown. Type a character. On the sending end, you should see output like:
[2020-12-10 23:51:25.351 ] Post message: {"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644285349,"sendId":16}

On the receiving end, you should see output like:
[2020-12-10 23:51:27.713 ] Receive message: {"context":{"GuestSessionId":"31","IsOwner":"False"},"sourceId":"Coauthoring","eventId":45,"jsonContent":"{"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644427514,"sendId":25}","time":1607644427713}

Are messages being sent and received?

Hey @dheerajmehtaa , could you please fill out the issue template so we can help you out? Also it looks like your screenshot did not attach correctly.

Closing this due to inactivity. Please re-open this issue if you're still experiencing this bug. Thanks!


fixed: Discrepancies in announcement screens

https://openedx.atlassian.net/browse/MA-1001
@aleffert plz review

Instead of visibility:gone can we just get rid of those sections entirely?

I've used visibility:gone for the following reasons:

In future, if we'll need these views, we'll just have to set visibility to visible and use them in code.
Incase, there are references in code for such views, null pointers wont happen.
And since, visibility is set to gone, there isnt a drawing overhead on the cpu.

so what do u think ?

@miankhalid:

I think these views are going to be permanently removed from the design.
All the references should be removed as well.
Yes there is no drawing overhead, but the views still need to be resolved during inflating and layout, and they are retained in memory as well.

done .. @aleffert plz review

done .. plz review @aleffert

:+1:

I'll note that as a general policy, we prefer to delete code inactive code unless we're sure we're going to need it soon. You can always find it in version control and getting rid of it keeps the codebase cleaner.


cargo-edit: 0.1.6 -> 0.3.0-beta.1

I would do 0.2.0 since that's not a beta, but it appears to have a Cargo.lock that's out of sync.

Can you have a look at #39348, which seems to do 0.2.0 ?

@GrahamcOfBorg build cargo-edit

Failure on x86_64-darwin (full log)
Attempted: cargo-edit
Partial log (click to expand)
          clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)

error: aborting due to previous error

error: Could not compile `cargo-edit`.

To learn more, run the command again with --verbose.
builder for '/nix/store/vgz1250y68lbh06dmijffzwgqy7w8c9i-cargo-edit-0.3.0-beta.1.drv' failed with exit code 101
error: build of '/nix/store/vgz1250y68lbh06dmijffzwgqy7w8c9i-cargo-edit-0.3.0-beta.1.drv' failed

Failure on x86_64-linux (full log)
Attempted: cargo-edit
Partial log (click to expand)

failures:
    upgrade_prints_messages

test result: FAILED. 11 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '--test cargo-upgrade'
builder for '/nix/store/4l2zgrmjw7nh2x3ids7101n6qhld1b2w-cargo-edit-0.3.0-beta.1.drv' failed with exit code 101
error: build of '/nix/store/4l2zgrmjw7nh2x3ids7101n6qhld1b2w-cargo-edit-0.3.0-beta.1.drv' failed

Oh, right, I should've searched for this first. My bad.

Failure on aarch64-linux (full log)
Attempted: cargo-edit
Partial log (click to expand)
cannot build derivation '/nix/store/968786gqlsc9av3bhym3wfwslg51qssj-rust_serde_derive-1.0.18.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/0k6654nxy2nxwadgrpz5mqajqy0qdpbw-rust_crates-io-0.11.0.drv': 30 dependencies couldn't be built
cannot build derivation '/nix/store/dbxyfj2hgvq0nxy705k6xngxsahgmr0w-rust_docopt-0.8.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/sv160xq3bs691080ah2iwwqrg69h5z0f-rust_git2-curl-0.7.0.drv': 20 dependencies couldn't be built
cannot build derivation '/nix/store/fsaj8bh4akdi6d6wa9is5pvfnx7g6wd1-rust_ignore-0.2.2.drv': 18 dependencies couldn't be built
cannot build derivation '/nix/store/s2gmz1i9v4gsxlwg90p6i9fnvxzw9bcr-rust_cargo-0.22.0.drv': 78 dependencies couldn't be built
cannot build derivation '/nix/store/bjykj5a101hl72m7fj7fbx02b0w9f5hh-rust_cargo-vendor-0.1.13.drv': 79 dependencies couldn't be built
cannot build derivation '/nix/store/fh5ssbs1kkcnwbrmjhiisixqfxwzhahd-cargo-edit-0.3.0-beta.1-vendor.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/hf4hr7xw6px188rc1nr3wlgs9wq38s5m-cargo-edit-0.3.0-beta.1.drv': 3 dependencies couldn't be built
error: build of '/nix/store/hf4hr7xw6px188rc1nr3wlgs9wq38s5m-cargo-edit-0.3.0-beta.1.drv' failed


2.1 docs point at calicoctl/calico-node v1.1.0, not v1.1.1

Looks like we're pointing people to the older release (which had a blocking bug in the default endpoint to host setting).
Should be a trivial fix but I wasn't sure whether I should be modifying the existing value in the yaml or making  a new entry.

Fixed by #706


Backports "Fixes an issue with AppendableMemory that can cause MSQ jobs to fail" (#17369)

Backports https://github.com/apache/druid/pull/17369 to Druid 31

We know that the run is flaky for java 21. Going ahead and merging this.


Use single priority queue instead of a queue per token

Why
For plasma framework, the underneath layer should be agnostic and decoupled from the logic on top of it. "Which Token" is more or less a business logic of the transaction or the output/state. Especially we are able to abstract our contract to deposit, it is potentially possible to "deposit" something that is not even token based into plasma now!
The reason of priority per queue is because we want to make sure a bad external code (token contract) cannot break the "processExit" function for others.
Proposal
Use pull over push to secure the transfer. So we do not transfer while "processExit", instead, we just mark things as "transferable" and let user to do the real transfer in another call.
What to do

[x] Provide a pseudo code/POC for the pull over push solution and discuss whether this is applicable.

Rehashing old discussion on this topic - it can be done. Old discussion - beyond login wall.

We track funds that are ready for withdrawal in subaccounts governed by root contract (this operation does not involve calling token contract code). To guarantee that operator can't sweep those funds, we introduce a mapping (token -> amount) which will describe amount of funds in root contract that is not yet put aside for withdrawal. When fraudulent exit is finalized, it can steal up to that amount and funds that are put aside for withdrawals are safe.

This "not yet put aside for withdrawal" amount would need to be updated with every processed exit and every deposit.

And an old argument on queue-per-token superiority.

Better UX (just exit instead of exit+withdraw), less code (one additional mapping and using token function parameter here and there). No additional variables are needed in contract body. Even marginally cheaper priority queue processing (~log(N/3) due to some tokens being way more popular).

ok, I checked the previous discussion, my idea of pseudo code is the same as @pdobacz's. I will skip that then. (btw, reading the discussion, I am really impressed by how the isolation by queue idea comes up)

map a pair (exitor, token) to amount and allow to withdraw(token) that amount.

I think the main and biggest tradeoff of the pull over push is UX.
Less code and less variable, with a more single responsibility code structure, it is not really that much benefit (?). The cheaper processing of queue might be compensated by the fact that we do not need to run the real token transfer logic and only set a value in map.
I would like the discussion to focus on whether do we want to tradeoff UX for framework immaculacy.
A small win for pull over push is I think this as well solves: https://github.com/omisego/plasma-contracts/issues/77

If moving to single queue would help us to get rid of this complexity, that would be nice. Or to solve it in some other way. @boolafish @pik694
https://github.com/omisego/plasma-contracts/blob/master/contracts/RootChain.sol#L589

I will take the above discussion as a green light as moving forward a single priority queue with pull-over-push. If there is any objection please let me know.

Sorry for coming to this issue late.
What would the impact be to the UX change to a user withdrawing funds from Plasma? Does this have an impact on client libraries?
@Pongch and @Nikodemek18 could you please comment on possible side effects.

Yes, it will. Instead of user getting the fund directly after exit processed, user would need to send a transaction to withdraw fund from plasma.

Hey @boolafish just for clarification, please let me know if the steps I've described here is correct.
From the user side (given that he/she has a single UTXO ready to be exited), on this flow, the user will:

call startExit() with the details of the transaction as usual
wait for however long the challenge period is going to be
call a processExit() . Given that there is now a single queue, what are the values needed in this function ?
call a withdrawal() ? Again, not quite sure what is needed from the user. From what I've gathered this actual withdrawal call will be making calls to the smart contract to move the tokens.

Is this assumptions correct ? I would still like to see the full pseudo code for this if possible to see the potential impact it may have on our client library.

Another tangental question (but still related to exit UX regardless). The old problem we had with exits is that there is a potential for the exit queue to gets really clogged up (if in the case of mass exits and users are forgetting to processExits()). A user does not know if and where his exit is within the queue which means he/she could potentially pay a significant amount of gas to process exits for other users. I'm wondering if a single priority queue would worsen the problem ?

@Pongch this is a rough version of what is in my mind:

contract Erc20Vault {
    mapping(bytes32 => uint256) withdrawable;
    mapping(address => uint256) totalAmounts; // token -> amount

    function deposit(address token, uint256 amount) public {
        totalAmounts[token] += amount;
        // do the other deposit logic....
    }

    function processExit(uint256 amount, address token, address exitTo) public {
        // todo: require only by exit processor

        require(totalAmounts[token] - amount >= 0, "not enough fund in the vault");

        bytes32 key = keccak256(abi.encode(token, exitTo));
        withdrawable[key] = amount;
    }

    function withdraw(address token, address payable user) public {
        bytes32 key = keccak256(abi.encode(token, user));

        uint256 amount = withdrawable[key];
        require(amount > 0, "user does not have fund to withdraw");
        getErc20Contract(token).transferFrom(address(this), user, amount)
    }
}

processExit() would have all existing parameter aside from token
withdraw() depends on what ERC though. I guess ERC20 can be like above.
If we haven't solve that, then yes, especially for the less popular token users, it would worsen the UX there. For popular token I guess we are more or less the same situation. I think it should be watcher (?) auto monitoring/parsing the queue and monitor for user to process exit?

In require(totalAmounts[token] - amount >= 0, "not enough fund in the vault"); totalAmounts[token] -= amount; "amount" is the amount we are withdrawing?

yes! that is the amount per exit.

btw, I am not really insisting on this. I am totally fine to keep token per queue. Would just like to know whether it is a feasible path to move on with the UX tradeoff or shall I just keep existing mechanism.

Single queue costs the same in terms of gas for anyone running processExits as multiple queue solution, but it also introduces additional step of withdrawing the funds from the contract. I don't really see a benefit of introducing it. Yeah, it will simplify one part of the code (but that code was already written, reviewed and covered with tests). Anything else?

More of just being a idealist of not introducing the concept of “token”
because we can potentially deal with things not a token. Especially with a vault abstracted, we can define anything now. But again, I take this small and quite likely not useful win at this moment. That’s why I am not really insisting this one. Code complexity is not my main concern actually.

AFAIK plasma is fundamentally limited to things that can be ascribed value. Those are usually represented as tokens :)
But lets talk about this on Monday call. It's a very interesting topic.

@paulperegud I would really appreciate, if you could brief us after your call with @boolafish. I need to understand what is the exact benefit of having single queue. For now, it sounds like we are adding one additional step (which is an obvious disadvantage).

seconded what @Nikodemek18 has said, having single queue will add additional step for the user to run what is already a seemingly complex UX.

Haha, Thanks all you guys @Nikodemek18 @Pongch @paulperegud . I think I get enough down vote on this and it is not really useful anyway at this moment. Will still talk with Pepesza just to see the potential of none token-based plasma but would conclude this as a no-go.

Re-open this for discussion and with some latest discussion with @paulperegud a month ago.
With the solidity actually have the possibility to do try-catch it is possible to use single queue without the down side provided above. Actually as it is kind of proven that multi-queue does not provide us enough isolation (as we are already dosing some try-catch code in vault) and have caused some trouble in our interactive game: eg. https://github.com/omisego/security-issues/issues/13
With single queue, we can enqueue IFE during startIFE (instead of piggyback) and process the whole IFE-tx at once instead. Also, it removes the need to do addQueue as we only need one queue!

Never mind. It seems to have some gas issue: https://github.com/omisego/plasma-contracts/issues/224#issuecomment-548697364


feat: allow variable tensor dimension

Goals:

Implements https://github.com/docarray/docarray/issues/871
[x] Implement for TorchTensor
[x] Implement for NdArray
[x] check and update documentation, if required. See guide

Do we want to add an example usage in the docstrings?

Do we want to add an example usage in the docstrings?

Yes please!

First question, unfortunately not. Numpy and torch have slightly different api, particularly in this case, in the view vs reshape. And yep, the 'x' isn't shared.

cannot we abstract the reshaping part, somewhere ?

First question, unfortunately not. Numpy and torch have slightly different api, particularly in this case, in the view vs reshape. And yep, the 'x' isn't shared.

cannot we abstract the reshaping part, somewhere in the computational backend ?

I suggest the same


Use key committing AEAD or AES-CTR with HMAC-SHA512

Currently none of AEAD ciphers in cryptography package support key commitment , but key commitment is a good to have property
refer discussions on  https://crypto.stackexchange.com/questions/88716/understanding-the-impact-of-partitioning-oracle-attacks-on-stream-ciphers and https://crypto.stackexchange.com/questions/6075/is-encrypthmac-stronger-than-aead?noredirect=1&lq=1

After a long decision making process it has been decided to use AES-GCM with HMAC-SHA512 or HMAC-SHA256 instead of AES-CTR.

Seems current use of AES-GCM is better than rolling out my own implementation and more safer. I would reopen this when safer alternatives emerge.

I strongly believe its worthwhile to implement a key committing AEAD like AES-CTR with HMAC-SHA512 ,its unlikely to suffer major crypto mistakes if coded properly,  any future contributors may refer discussion here https://crypto.stackexchange.com/questions/101612/common-pitfalls-to-be-taken-care-of-while-implementing-encrypt-then-hmac-scheme and guidelines here https://github.com/samuel-lucas6/Cryptography-Guidelines to replace AES-GCM used in PQcrypt.


Add data-pipeline-ffi to nuget artifacts

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.84%. Comparing base (bc58fa5) to head (7d07584).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #650      +/-   ##
==========================================
+ Coverage   73.81%   73.84%   +0.02%
==========================================
  Files         257      257
  Lines       37309    37309
==========================================
+ Hits        27541    27549       +8
+ Misses       9768     9760       -8

Components
Coverage Δ

crashtracker
20.53% <ø> (+0.05%)
:arrow_up:

datadog-alloc
98.73% <ø> (ø)

data-pipeline
93.06% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
83.08% <ø> (ø)

ddcommon-ffi
69.52% <ø> (ø)

ddtelemetry
59.10% <ø> (ø)

dogstatsd-client
79.77% <ø> (ø)

ipc
83.58% <ø> (ø)

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
38.19% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
94.77% <ø> (ø)

trace-mini-agent
72.47% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.87% <ø> (ø)

👋 FYI, it's being taken into account in https://github.com/DataDog/libdatadog/pull/690


redundant padding in FluentMessageBarProvider component

#1017 is not fixed. The recommended solution was to put FluentMessageBarProvider at the end of MainLayout. All that does is move the redundant padding to the bottom of the page. The only way to fix this is by doing:
<FluentMessageBarProvider style="padding: 0px" />

or
.fluent-messagebar-provider {
    /* workaround for https://github.com/microsoft/fluentui-blazor/issues/1017 */
    padding-bottom: unset !important;
}

But why is this necessary? Please fix it

Is it possible to only have the margin when the message bar is being displayed?

No, because the provider is always there. But I don't understand what is the problem with just setting a Style parameter?

If I set the Style parameter then there would be no margin when the message bar is displayed, right? I would prefer it if there was no padding only when the message bar is not visible.

I'm adding a change for the next version. In FluentMessageBarProvider there will be checked if there are messages to show. If not the whole provider (ie the HTML div) will not be rendered anymore.
Think that solves your problem completely.


Add Durable Functions Distributed Tracing section

This PR adds information about Durable Functions Distributed Tracing V2. It's currently a draft PR since I'm adding sections based on feedback from other threads.

@cgillum

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@bachuv can you instead create this PR in the MicrosoftDocs/azure-docs-pr repo? That's where all internally developed doc content is supposed to go, and the build pipeline for that repo includes a bunch of other useful functionality, like preview URLs.

@cgillum, I opened a new PR in the MicrosoftDocs/azure-docs-pr repo - https://github.com/MicrosoftDocs/azure-docs-pr/pull/263303. I'll close this PR.


Spelling and Grammar mistakes corrected

There were few words that were spelled wrong, also few sentences were not structured well.

Can someone please review this contribution.
Thanks


issue-14: Allow for card highlighting in the For You page

If the user enters a link such as www.roomatefinder.github.io/foryou#UUID then it should highlight the profile with the user ID that is after the # sign.
The highlight means the map has everyone's pin, and it will take you to the For You Page with that user's pin highlighted.
Please do work for this task in a branch named issue-14.

No longer necessary


My Contribution to the Hello World Repository

What does the program do ?
The Program checks whether a number is even or odd.
In what programming language it is written?
Python 2.x

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


How to configure the certificates in config.yaml for the modules and downstream devices ?

Question Summary
How to configure the certificates in config.yaml for modules and downstream devices?
Detailed background
I have just started EFLOW and am able to deploy / provision the device using commands but wanted to configure the certificates so modules and downstream devices can be authenticated.
I have tried to find out the solution over google but was not been able to find out it. Do I need to manually update the path into the config.yaml and restart the service or is there any way I can do it using commands only?
As of now, my deployment uses self generated certificate which is valid for 90 days.

Hi @niravjprabtani,
I would recommend checking Eflow Utils and check the EflowUtil-SetEdgeCertificates cmdlet.   These cmdlets are sample codes, so feel free to download and edit them to your best convenience.
Thanks,
Francisco

Hi @fcabrera23
Thanks for the immediate reply, I really appreciate it


[traffic-gen-in-vm] Config: remove trafficGeneratorRuntimeClassName

Following the removal of the traffic generator pod, there is no longer a need to have the trafficGeneratorRuntimeClassName in the user-supplied configuration.
Remove it from:

Checkup configuration object
E2E test.
Makefile.

Tested against an OpenShift Virtualization 4.14 cluster.
Depends on PR #119, please review only the last two commits.

Change: Rebase

E2E tests passed after the rebase.


Update README.md

Some edits to the readme (although it's likely to need a bit more formatting). I can't get the hang of the line-breaks, and although Cut seems to work in the browser I'm editing this in, Copy and Paste do not. Feel free to make/undo changes as you see fit. In other news, having tracked down my specifications for the CSV files, I'm in the process of converting those to more generalised descriptions. I don't have any particular feel for where the resulting text should live, so I'll probably send it to you 'raw' and you can decide where you want it and what the formatting should look like. With luck, I'll get those descriptions tidied up in the next 24 hours (back at work tomorrow, first day since 19 August!).

I elected to copy your changes because I have also worked on the README and I think you were working on an older version.  Let me know after I merge my changes.


SIM Group and SIM(s) are made as OPTIONAL attributes for 5G full deployment

SIM Group and SIM(s) are made as OPTIONAL attributes for 5G full deployment
PR Checklist
Check these items before submitting a PR...
Contribution Guide
Best Practice Guide

[ ] - Please check this box once you've submitted the PR if you've read through the Contribution Guide and best practices checklist.

Changelog

SIM Group and SIM(s) are made as OPTIONAL attributes for 5G full deployment

Have validated the below use-cases:

Full deployment with SIM Group and SIM(s) => Success (SIM Group created with SIM(s))
Full deployment with SIM Group and NO SIM => Success (SIM Group created with NO SIM(s))
Full deployment without SIM Group and SIM(s) => Success (Both SIM Group and SIM(s) did not get created)
Full deployment without SIM Group and with SIM(s) => Success (Both SIM Group and SIM(s) did not get created. No error message will be thrown here, SIM Group and SIM(s) will be skipped)

@tomzhu1 I won't have time to review this before holiday. Can you review please?


CI for Node

  ✕ Initializes with two players (3 ms)
  ✕ Starts the game with a random player
  ✕ Sets the current player to be whoever it is not


Update Character “thaishin”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
5859047195906b64013d8629c9e708bf10d0e509

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/62ec010e4fc6d300094bdaac


IE9 video not buffering complete video duration

Hi,
I am having this issue:
On IE9 video is not completely buffered (for instance video duration is 30 sec and there is only 20 sec buffered ) then if I click somewhere (over those 10 sec missing) on the progress bar I got a javascript error ( DOM Exception: INDEX_SIZE_ERR (1))
Any ideas why is this happening?
Is there any workaround for this?
Any help is more than welcome
Thanks
PD: I am using version 2.16.3-6

I'm experiencing this as well using version 2.18.2 - using the same steps to reproduce as @jcoto4 mentions.

@jcoto4 Is this still an issue?

@ron666 I can't reproduce the issue on 2.18.2 anymore.


Improve colours of particles

The colours of the visualization currently don't show well on presentations and posters. We should improve the colours of the particles (and basemap: see #83)
Particles

[x] Increase size of particle lines?
[x] Particle colour

Review the result in the other issue.

Finalized in #115.


Grave not spawning in nether while in survival

As reported by Loki_BM, they died in the world survival_nether and their items just dropped, no grave spawn. There is no grave worlds defined in the config, however the player would have been in survival.
Need to investigate why the items dropped

Fixed in latest build


ML Challenge page text content

Add in all text content from this word doc into the page using the layout specified in the design. This ticket covers the content that is in between the banners.
Note: the source of truth for the copy is from the word doc, and not from the figma design

Image assets: https://drive.google.com/drive/folders/1kihiWYgKSU8Ff0XQx8ol85tmTDbna4M7?usp=drive_link


Connection options added to Connection string object

Hi All,
Initial connection string options object looks like below
let options = {
"user": ****,
"password": ****,
"server": ****,
"database": ****,
"port": ****,
}
after establishing a connection using  "new sql.Connection(options,callback)" same options object has been modified with additional properties having driver and connection info.
is this the normal behavior ??
{
"user": ****,
"password": ****,
"server": ****,
"database": ****,
"port": ****,
"driver": "tedious",
"options": {
"database": ****,
"port": ****,
"connectTimeout": 15000,
"requestTimeout": 15000,
"tdsVersion": "7_2",
"rowCollectionOnDone": false,
"rowCollectionOnRequestCompletion": false,
"useColumnNames": false,
"appName": "node-mssql",
"textsize": "2147483647",
"cancelTimeout": 5000,
"packetSize": 4096,
"isolationLevel": 2,
"encrypt": false,
"cryptoCredentialsDetails": {},
"useUTC": true,
"connectionIsolationLevel": 2,
"readOnlyIntent": false,
"enableAnsiNullDefault": true
},
"stream": false,
"parseJSON": false
}
Also help me in using same connection object across multiple modules - because i tried exporting an connection object like module.exports = new sql.Connection(options) and got "Connection closed exception" when i tried using this exported connection object.
Thanks

If you're re-using the connection for pooling, then you shouldn't be explicitly closing the connection.

closing as outdated


url stream with amplitudeJs

Question Checklist

[ x] I updated Amplitude.js to the latest version
[ x] I read the docs
[x ] I searched for existing GitHub issues

Question Description

AmplitudeJs is working with urlStream return from backend (mean stack in my case) ?

Are there any console errors or is it just not playing? Make sure to have your headers set correctly? See #401


[feature] workflow for publishing source code archives as release assets

Is your feature request related to a problem? Please describe.
Bazel recommends publishing source code archives as release assets – and Bazel Central Registry verifies stability by checking for …/releases/download/… in GitHub URLs. Using gh release download and gh release upload, GitHub Actions can automate this trivially, but OpenSSF punishes projects whose release assets lack signature and provenance.
Describe the solution you'd like
SLSA should provide a workflow for publishing source code archives as release assets with signature and provenance. Ideally, any project's release workflow could include a job specifying only permissions and uses keys and get .zip, .zip.intoto.jsonl, .tar.gz and .tar.gz.intoto.jsonl files attached to the release.
Describe alternatives you've considered
Letting N different projects implement this themselves in approximately N different ways. ;)
Additional context
N/A

Hi, thanks for the issue. You can achieve this today using the generator https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md and setting the upload-asset: true. Can you confirm this works for your use case?

I'm confident that it would, but the idea here is to spare every project the sha256sum … | base64 -w0 and base64-subjects dance and, moreover, to ensure that the gh release download and gh release upload dance is done by a trusted reusable workflow. It is – or it ought to be! – a common operation with approximately zero room for variations, so it should be made as convenient for every project as reasonably possible. Does that clarify the intention behind the request? :)

I understand the sha256sum … | base64 -w0.
I don't fully understand the gh release download and gh release upload. The generator I linked to does do the release upload by setting the upload-asset: true. Can you clarify this point?

Just to be clear, the idea is not to generate the source code archives manually. (GitHub already does that automatically.) The reason to do the gh release download and gh release upload dance is to take the source code archives that are available via …/archive/refs/tags/… and make them available via …/releases/download/….

ah, I missed this. Thank you. I'm not super familiar how …/archive/refs/tags/… are generated, and by whom. Are these the ones GitHub generates automatically? Are they not the same that are present in the release assets? Or are you merely saying that the API to download them is not consistent with other assets in the release (I've not verified if this is the case, just trying to parse your comment)?

As linked above, https://blog.bazel.build/2023/02/15/github-archive-checksum.html describes the situation quite well, I think, with the screenshot illustrating the difference between …/archive/refs/tags/… and …/releases/download/… in terms of the release assets. The problem that the gh release download and gh release upload dance solves is one of stability.
I should just clarify that the filenames in the …/archive/refs/tags/… URLs are not the filenames that GitHub actually serves. For the 2023-11-01 release of RE2, for example, GitHub will do the following:
https://github.com/google/re2/archive/refs/tags/2023-11-01.zip
-> location: https://codeload.github.com/google/re2/zip/refs/tags/2023-11-01
-> content-disposition: attachment; filename=re2-2023-11-01.zip
Likewise, gh release download uses the "real" filename, so the workflow that I'm proposing would not have to rename files. It's just about doing the gh release download and gh release upload dance and, in the process, generating signature and provenance.

Maybe this could be an option on the generic generator? I'm not sure we need a totally separate workflow. WDYT?

I had "do one thing and do it well" in mind, I think, when I suggested another workflow. generator_generic_slsa3.yml has a lot of knobs whereas this use case needs approximately zero knobs. Reusing the generic generator makes sense, of course, but I would argue that there's value in encapsulating/hiding its complexity.

In light of CVE-2024-3094, could this effort possibly be prioritised? ;)

In case it helps, I wrote https://github.com/google/re2/blob/main/.github/workflows/release.yml earlier today. :)

Hey, sorry for the late reply. Thank for putting an example together. We could easily support this using BYOB https://slsa.dev/blog/2023/08/bring-your-own-builder-github and https://github.com/slsa-framework/slsa-github-generator/blob/main/BYOB.md
We should be able to take your example and wrap it in a BYOB. This would let your users use the slsa-verifier to verify, out of the box. Would that work?

IIUC, yes, the PW would run gh release create (except using the API instead of the CLI) and then invoke the TRW, which would handle everything else. Although now I'm guessing that SLSA generating signature and provenance would make Sigstore signing superfluous. :)

IIUC, yes, the PW would run gh release create (except using the API instead of the CLI) and then invoke the TRW, which would handle everything else. Although now I'm guessing that SLSA generating signature and provenance would make Sigstore signing superfluous. :)

You would not need the sigstore signatures, but the SLSA builders use Sigstore too :) There are 2 (related) advantages to a common builder:

Other projects can use the same builder and inspect the code once
No need for users to read each project's workflow code to read how the tarball / zip files are created

If you're OK with all that, I can ahead and turn your example a SLSA builder

Note to myself https://docs.github.com/en/rest/repos/contents?apiVersion=2022-11-28#download-a-repository-archive-tar

If you're OK with all that, I can ahead and turn your example into a SLSA builder

SGTM. Thanks! :D

Hey, a few months ago GitHub made (then reverted) the tarballs non-deterministic, see https://github.com/orgs/community/discussions/45830. To avoid this sort of problems in the future, the builder could create the archives it self and upload them to the release. That also let us support other types or archive (if we need to) in the future. Wdut of this approach?

Downloading the source code archives and uploading them as release assets is sufficient, AFAIK, because that's what confers stability. I reckon that creating them (i.e. explicitly) wouldn't add value... but would add complexity. If somebody downloads a slightly different one later because they clicked or pasted the wrong link, I don't think it actually matters who or what created the one at the right link. Or am I misunderstanding a risk from a trust perspective here?

Downloading the source code archives and uploading them as release assets is sufficient, AFAIK, because that's what confers stability. I reckon that creating them (i.e. explicitly) wouldn't add value... but would add complexity.

Not super complicated I think. The BYOB framework already clones the repo, so code is available. We would just need to zip / tar it which does not seem too complicated.

If somebody downloads a slightly different one later because they clicked or pasted the wrong link, I don't think it actually matters who or what created the one at the right link. Or am I misunderstanding a risk from a trust perspective here?

stability requires that archives downloaded from GitHub (with the same link) to be deterministic. The link above shows that GitHub generates archives on the fly when they are requested (to save up storage space I think). This means the signature would fail if the archive is different at download vs when it was first signed.
Lmk what you think.

I think you might be confusing source code archives and release assets. The image below (taken from the Bazel blog) hopefully clarifies:

Note well that downloading the source code archives and uploading them as release assets makes them stable as release assets, not as source code archives. That's why I'm arguing that, at release time, it doesn't matter whether the source code archives are deterministic. If somebody ends up using a copy of a nondeterministic file, then it really doesn't matter how the deterministic file was created, does it?

My bad, I had not seen that you're re-uploading the source archives as release assets. I thought your example workflow only signed the downloaded source archives without re-uploading them. Re-creating or downloading existing source archives works. Is it fair to say that how the archive is created is an implementation detail you don't care too much about? Or you do care? I'll probably download them to simplify the first iteration, but would like to know if it makes a different for your use case, in particular security wise.

To date, manual manipulation of the source code archives is the big problem. Trusting their creation to GitHub seems no more risky than trusting everything else to GitHub, honestly, so obtaining them from GitHub – as opposed to creating them explicitly – suits me just fine.

note to myself https://github.com/actions/toolkit/tree/main/packages/artifact

Release artifacts are mutable. I think if we can guarantee the archives to be reproducible, we should try to do it.
https://www.gnu.org/software/tar/manual/html_section/Reproducibility.html

Draft PR is https://github.com/slsa-framework/slsa-github-generator/pull/3587. I think we need to tweak it to reduce permissions used and we're good to go


MMM-GoogleAssistant installation freezes

I'am trying to install MMM-GoogleAssistant on my Raspberry Pi Zero W without any luck.
The latest Rasbian is installed and i always preform a update & upgrade.
I have installed MM using this command: yes | bash -c "$(curl -sL  https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"
After that i follow this instruction.
I already fot some problems with: npm install At somepoint it freezes.
I did it "rest" for like a day and then rebooted it by just removing the power (i know.. not good...).
After that it seems like everything is installed ok.
But when i continue the instrunction i get stuck again at: cd ~/MagicMirror/modules/MMM-GoogleAssistant node auth_and_test.js (getting Google Assistant to work).
It gives me this error msg: Illegal instruction
the documentaion says to perfrom: npm rebuild.
It does it's thing and comes back without any error's. But when i try the "node" command again, i get the same error.
"npm rebuild" also sometimes get's my Pi frozen. I also tried: npm rebuild --build-from-source
but that will freeze my Pi as wel....
Note: If i follow these instructions, it will work without any problem... But i want it to get to work with MagicMirror.
Any solutions?

Moved to: https://github.com/bugsounet/MMM-GoogleAssistant/issues/62