Update share-to-teams.md

Docs Build status updates of commit ae7462b:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit ae7462b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


AS2: support polls

API docs: entities, endpoints. would need to figure out how to represent them in AS1.

This might be higher priority now that we're rendering Mastodon posts in Bridgy Fed feeds.

Remaining work here is rendering in HTML and plain text, ie AS1 => HTML, RSS, Atom, JSON Feed.
Example post:

https://tech.lgbt/@nelson/110101971009516952
https://granary.io/url?input=as2&output=as1&url=https%3A%2F%2Ftech.lgbt%2F%40nelson%2F110101971009516952

The quick and dirty path here would be to add this to microformats2.render_content. The deeper path would be to figure out the mf2 for polls, add that to microformats2.object_to_json, then add the HTML rendering to json_to_html. I'd probably be ok with either.


get related model recursive error

For this error, I am able to install django-taggit==0.16.2 just fine. But when I attempt a migrate to a new database I get this error.
django-taggit==0.16.2
django-taggit-templatetags2==1.4.0
django-1.8.3
Running migrations:
Rendering model states...Traceback (most recent call last):
File "./manage.py", line 10, in
execute_from_command_line(sys.argv)
File "lib/python2.7/site-packages/django/core/management/init.py", line 338, in execute_from_command_line
utility.execute()
File "//lib/python2.7/site-packages/django/core/management/init.py", line 330, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/lib/python2.7/site-packages/django/core/management/base.py", line 393, in run_from_argv
self.execute(_args, *_cmd_options)
File "/python2.7/site-packages/django/core/management/base.py", line 444, in execute
output = self.handle(_args, *_options)
File  /lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 221, in handle
executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
File "/lib/python2.7/site-packages/django/db/migrations/executor.py", line 104, in migrate
state = migration.mutate_state(state, preserve=do_run)
File "/lib/python2.7/site-packages/django/db/migrations/migration.py", line 83, in mutate_state
operation.state_forwards(self.app_label, new_state)
File "/lib/python2.7/site-packages/django/db/migrations/operations/fields.py", line 51, in state_forwards
state.reload_model(app_label, self.model_name_lower)
File "//lib/python2.7/site-packages/django/db/migrations/state.py", line 122, in reload_model
related_models.update(get_related_models_recursive(rel_model))
File "//lib/python2.7/site-packages/django/db/migrations/state.py", line 57, in get_related_models_recursive
rel_app_label, rel_model_name = rel_mod._meta.app_label, rel_mod._meta.model_name
AttributeError: 'NoneType' object has no attribute '_meta'
(oneeight_v)

Exact same symptom, any hint on this subject would be greatly appreciated. No clues on the reason behind, for the time being.
Thanks in advance

Using a "through model" will resolve this error: https://django-taggit.readthedocs.org/en/latest/custom_tagging.html

Going to close this one, I think that this might have been related to related_name stuff from before but this is a hard issue to debug without more information (like the migrations itself). Please re-open if still valid (with some more info)


bug: No documentation of Prometheus metrics

Describe the bug
Several components in KubeStellar offer metrics for Prometheus scraping.  None of that is documented.
Steps To Reproduce
Try finding such documentation.
Expected Behavior
The metrics are documented.
Additional Context
No response

@dumb0002
@waltforme
@yana1205

Here is a summary of what I know now.
The kcp server is derived from the kube-apiserver, which offers a big pile of metrics.  The semantics of the kcp fork of kubernetes have a real impact on the metrics.  If I understand correctly, this is something that has developed over time in kcp.  I do not recall exactly what is available in kcp release v0.11.0, v0.20.0, or the current code.
The Kubernetes libraries used in building the KubeStellar controllers can easily produce Prometheus metrics, but it takes a tiny explicit effort to actually expose this on a port for scraping.  I took that effort for the mailbox controller (see https://docs.kubestellar.io/release-0.7/Coding Milestones/PoC2023q1/mailbox-controller/#usage) and the placement translator (see https://docs.kubestellar.io/release-0.7/Coding Milestones/PoC2023q1/placement-translator/#usage).  It would be a small matter to add this to the where resolver and to the syncer.  When the central controllers are running in a Kubernetes Pod, they can be reached at the Pod's IP address. The Kubernetes libraries used in each controller are just for a few specific purposes, the most interesting of which is the controller's workqueue.  We can and should define additional metrics that are related to the controller's specific mission (#959).


Login page not so appealing

Describe the feature
Login Page is the one where the user lands and log into the page to get the service. And if that particular sections fails to go well, the entire hard work will go in vain. Please assign me for login page updating and I am ready to update it to next level provided that rest everything is preserved well.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me for this issue.

Here we have a infinity scroll of different books and the left side grey area is for login this is just a rough wireframe final will be looking 10x better please confirm and i will start


CI: Ingress Conformance Test: An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred

CI failure
Name
Ingress Conformance Test (Without_XDP, true, false, disabled, dedicated, false): An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred
Logs
Scenario: An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred # features/path_rules.feature:174
    When I send a "GET" request to "http://mixed-path-rules/foo"                                                          # feature.go:94 -> iSendARequestTo
    timeout while waiting after 6 attempts, 0/3 sucessess
    Then the response status-code must be 200                                                                             # feature.go:102 -> theResponseStatuscodeMustBe
    And the response must be served by the "foo-exact" service

Sysdump
cilium-sysdump-out.zip
Link

Action: https://github.com/cilium/cilium/actions/runs/7545131415/job/20540072188#logs
PR: https://github.com/cilium/cilium/pull/29796

Hit a similar one in https://github.com/cilium/cilium/actions/runs/7631765783/job/20790487495 on  https://github.com/cilium/cilium/pull/30361
Sysdump: cilium-sysdump-out.zip

Hit in https://github.com/cilium/cilium/pull/30743 as well

Hit again: https://github.com/cilium/cilium/actions/runs/9267168012/job/25493004548

Hit in - https://github.com/cilium/cilium/actions/runs/9320255252/job/25656650072.

Hit again: https://github.com/cilium/cilium/actions/runs/9330022689/job/25683138209


The case of the disappearing VirtualService route (from Gateway after EnvoyFilter added)

Bug description
Applying an EnvoyFilter sometimes disappears virtual services from the route table of the gateway.
Maybe this is just me not understanding how to opt out of a filter via a MERGE operation; in which case I'd be happy take instruction. It's not really documented.
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
The VS:es should not just stop being routable
Steps to reproduce the bug
EnvoyFilter:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: ext-authz
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      istio: ingressgateway

  configPatches:
  - applyTo: HTTP_FILTER
    match:
      context: GATEWAY
      listener:
        filterChain:
          filter:
            name: envoy.http_connection_manager
            subFilter:
              name: envoy.router

    patch:
      operation: INSERT_BEFORE
      value:
        name: envoy.filters.http.ext_authz
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.http.ext_authz.v2.ExtAuthz
          failure_mode_allow: false
          # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#envoy-v3-api-msg-extensions-filters-http-ext-authz-v3-httpservice
          http_service:
            server_uri:
              uri: http://oauth2-proxy.auth.svc.cluster.local
              cluster: outbound|80||oauth2-proxy.auth.svc.cluster.local
              timeout: 5s
            # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#extensions-filters-http-ext-authz-v3-authorizationrequest
            authorization_request:
              # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#envoy-v3-api-field-extensions-filters-http-ext-authz-v3-authorizationrequest-allowed-headers
              allowed_headers:
                patterns:
                - exact: cookie
                - exact: authorization
                - exact: x-auth-request-redirect
                - prefix: x-forwarded
              # For some reason this field are not documented in the v2 schema docs at Envoy
              # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#envoy-v3-api-field-extensions-filters-http-ext-authz-v3-authorizationrequest-headers-to-add
              # kubectl sniff oauth2-proxy-867fd547fc-w6drx -n auth -f 'port 4180'
              headers_to_add:
              - key: x-auth-request-redirect
                value: "https://%REQ(:AUTHORITY)%%REQ(:PATH)%"
            authorization_response:
              allowed_client_headers:
                patterns:
                - exact: set-cookie
                - exact: authorization

  # Skip requiring Bearer tokens when logging in:
  # https://istio.io/latest/docs/reference/config/networking/envoy-filter/#EnvoyFilter-EnvoyConfigObjectPatch
  - applyTo: VIRTUAL_HOST
    # https://istio.io/docs/reference/config/networking/envoy-filter/#EnvoyFilter-EnvoyConfigObjectMatch
    match:
      # https://istio.io/latest/docs/reference/config/networking/envoy-filter/#EnvoyFilter-PatchContext
      context: GATEWAY
      # https://istio.io/latest/docs/reference/config/networking/envoy-filter/#EnvoyFilter-RouteConfigurationMatch
      routeConfiguration:
        gateway: istio-system/ingress
        # https://istio.io/latest/docs/reference/config/networking/envoy-filter/#EnvoyFilter-RouteConfigurationMatch-VirtualHostMatch
        vhost:
          name: accounts.example.com:443
          # route: ...
    patch:
      # https://istio.io/latest/docs/reference/config/networking/envoy-filter/#EnvoyFilter-Patch-Operation
      operation: MERGE
      # -------- Envoy record is merged with the value
      # https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#struct
      value:
        name: envoy.ext_authz_disabled
        # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/config/route/v3/route_components.proto.html?highlight=per_filter_config
        typed_per_filter_config:
          envoy.filters.http.ext_authz:
            "@type": type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthzPerRoute
            disabled: true

  # Our ingress should be accessible publicly
  - applyTo: VIRTUAL_HOST
    # https://istio.io/docs/reference/config/networking/envoy-filter/#EnvoyFilter-EnvoyConfigObjectMatch
    match:
      context: GATEWAY
      routeConfiguration:
        gateway: istio-system/ingress
        vhost:
          name: i.example.com:443
    patch:
      operation: MERGE
      value:
        name: envoy.ext_authz_disabled
        typed_per_filter_config:
          envoy.filters.http.ext_authz:
            "@type": type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthzPerRoute
            disabled: true

And then add a VS for accounts.example.com and another for i.example.com and run
$ istioctl pc route istio-ingressgateway-68dfd96487-5gz2s -n istio-system
NOTE: This output only contains routes loaded via RDS.
NAME                                             DOMAINS                  MATCH                  VIRTUAL SERVICE
https.443.https-default.ingress.istio-system     accounts.example.com     /*                     oauth2-proxy.auth
http.80                                          *.example.com            /*                     404
http.80                                          example.com              /*                     404
                                                 *                        /healthz/ready*
                                                 *                        /stats/prometheus*

^^ i.example.com is missing.
Now remove the EnvoyFilter, and this line is also visible:
https.443.https-default.ingress.istio-system     i.example.com            /*                     i-example-com.ingress

Background info, the gateway is standard:
apiVersion: v1
items:
- apiVersion: networking.istio.io/v1beta1
  kind: Gateway
  metadata:
    name: ingress
    namespace: istio-system
  spec:
    selector:
      istio: ingressgateway
    servers:
    - hosts:
      - '*.example.com'
      - examople.com
      port:
        name: http
        number: 80
        protocol: HTTP
      tls:
        httpsRedirect: true
    - hosts:
      - '*.example.com'
      - example.com
      port:
        name: https-default
        number: 443
        protocol: HTTPS
      tls:
        credentialName: example-com-tls
        mode: SIMPLE
        privateKey: sds
        serverCertificate: sds

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
$ istioctl version --remote
client version: 1.8.1
control plane version: 1.8.1
data plane version: 1.8.1 (27 proxies)

$ kubectl version --short
Client Version: v1.20.0
Server Version: v1.17.13-gke.2001

How was Istio installed?
istioctl operator init
Environment where the bug was observed (cloud vendor, OS, etc) GKE 1.17.x stable chan
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.
E-mail me at henrik at haf dot se

The only reason an EnvoyFilter like this should cause it to be complete removed is if the config is rejected entirely. Do istiod logs show anything like ACK ERROR? Its also in the proxy logs

Noticed you are using v2 ext_auth, change it to v3

No, no ACK errors at all. There's a bunch of warnings when this is applied that Failed to find port for service my-ns/my-app: no suitable port for manifest

Could you provide an example that works, perhaps? It would seem I'm not alone in trying to make this work on the latest istio?

@hzxuzhonghu You suggestion did not work:
    patch:
      operation: INSERT_BEFORE
      value:
        # https://www.envoyproxy.io/docs/envoy/v1.16.1/configuration/http/http_filters/ext_authz_filter#per-route-configuration
        name: envoy.filters.http.ext_authz
        typed_config:
          # https://www.envoyproxy.io/docs/envoy/v1.16.1/configuration/http/http_filters/ext_authz_filter#configuration-examples
          # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#envoy-v3-api-msg-extensions-filters-http-ext-authz-v3-extauthz
          # https://www.envoyproxy.io/docs/envoy/v1.16.1/api-v2/config/filter/network/ext_authz/v2/ext_authz.proto
          # "@type": type.googleapis.com/envoy.config.filter.http.ext_authz.v2.ExtAuthz
          "@type": type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthz

I get this warning message, but I'm not sure if it's relevant:
-5dcd995fdc-qwx67.app resources:21"}
istiod-7bfb849f9d-hpvhc discovery {"level":"info","time":"2020-12-22T12:24:54.090049Z","scope":"ads","msg":"Push Status: {\n    \"pilot_conflict_outbound_listener_tcp_over_current_tcp\": {\n        \"<IP_ADDRESS>:443\": {\n            \"proxy\": \"analytics-db-5dcd995fdc-qwx67.app\",\n            \"message\": \"Listener=<IP_ADDRESS>:443 AcceptedTCP=metadata.google.internal RejectedTCP=storage.googleapis.com TCPServices=1\"\n        }\n    },\n    \"pilot_vservice_dup_domain\": {\n        \"metadata.google.internal:80\": {\n            \"proxy\": \"analytics-db-5dcd995fdc-qwx67.app\",\n            \"message\": \"duplicate domain from  service: metadata.google.internal:80\"\n        },\n        \"storage.googleapis.com:80\": {\n            \"proxy\": \"rutta-79d8978dd8-2nxzv.ingress\",\n            \"message\": \"duplicate domain from  service: storage.googleapis.com:80\"\n        }\n    }\n}"}

Which comes from this:
# https://github.com/istio/istio/issues/5288#issuecomment-455600510
# https://istio.io/latest/docs/reference/config/networking/service-entry/
# https://github.com/istio/istio/issues/10951
apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
metadata:
  name: gcp-metadata
spec:
  hosts:
  # - "www.googleapis.com"
  - metadata.google.internal
  - storage.googleapis.com
  addresses:
  - "<IP_ADDRESS>/32" # metadata.google.internal
  location: MESH_EXTERNAL
  ports:
  - number: 443
    name: https
    protocol: TLS
  - number: 80
    name: http
    protocol: HTTP

But I don't see the link to rutta, the service behind i.example.com in my example above.

Will be improved in the future https://github.com/istio/istio/issues/27790

Perhaps https://www.paraesthesia.com/archive/2020/09/03/setting-up-oauth2-proxy-with-istio/ is a solution: with explicit opt-in per service as a workaround?

Trying the above doesn't work: 1) if I only use the request authentication — it still shows up without me authenticating first. 2) if I also try to set an AuthorizationPolicy I get https://github.com/istio/istio/issues/29747

Also, if I use
  - applyTo: HTTP_FILTER
    match:
      context: GATEWAY
      listener:
        filterChain:
          sni: jaeger.logary.tech
          filter:
            name: envoy.http_connection_manager
            subFilter:
              name: istio.metadata_exchange

The SNI doesn't seem to matter, but if I remove the sni "selector" from the above filter, all request have authn required!!!

So I've gone back to the filters, and it would seem that the moment you have two patches that it removes the last VIRTUAL_HOST patch. Also, I can't see the disabled filters with istioctl pc listener istio-ingressgateway-86f8d88f5d-2kl85 -n istio-system -o json --port 8443 — is there a better way?

@MischaWeerwag  which version of istio you are using?  Is there any way we can allow multiple sni?  I am using oauth2-proxy at ingress gateway layer.. So would like to allow only few hosts under oidc auth like for example (grafana,kiali,Jaeger,...)

spam

Either close as "we expect our users to bang their heads against a wall and lose requests without warnings" or stop the bot from berserking the issue ;)


add a new test to see when either sourceFields or targetFields is NOT NULL AND Foreign Key is ALSO present

add a new test to see when either sourceFields or targetFields is NOT NULL AND Foreign Key is ALSO present - we give precedence to the source and target fields specified in the config to perform the join.
Originally posted by @Aniruddh25 in https://github.com/Azure/data-api-builder/pull/707#discussion_r964283045

since, exactly one of either sourceFields or targetFields can't be null by design of CLI. we will add a test where both source and target fields are present in the config and it overrides the relationship fields defined in the DB.


feat(swap): add an option not to withdraw swapped ZRC20

@andresaiello this is a proposal to extend the swap example to handle a scenario where a user wants to keep the swapped ZRC-20 asset instead of immediatly withdrawing it. This might seem odd, but I'm building an example frontend where I want users to be able to transfer/swap/withdraw/deposit all tokens to all other tokens. One of the few operations left is "deposit and swap":

Want to know your opinion on this. Even though not withdrawing might seem odd (most users will want to withdraw), having this swap component talk to this example contract would make it component also a demo of the example contract.

@andresaiello another question I have is adapting bytesToAddress function to work with bytes memory:
https://github.com/zeta-chain/example-contracts/blob/7dab1a4888ab5e159c889e0bd274f651ac9aefbe/omnichain/swap/contracts/Swap.sol#L28-L39
Of course, we already have a helper for this, but it's only for calldata, not memory:
https://github.com/zeta-chain/toolkit/blob/a902bea0581b284a59d66a2c9ae547d3b0cdc93c/contracts/BytesHelperLib.sol#L15-L23
Would it be a good idea to add the bytes memory version as another helper (if so, do you have any suggestions on the name), and if not, what's the better way to handle this.

bytesToAddress

good idea. I didn't need it yet but looks like someone may need it. Let's just call it bytesMemoryToAddress

@andresaiello wdyt about the changes to contract in general? The ability to not withdraw tokens during swap may seem a bit niche, but it has a few advantages: it matches the requirements of the example frontend (to be able to swap gas/ERC-20 to ZRC-20 without withdrawing) and uses the same pattern of action as in staking. Maybe this means we even need to change the default template to use action, because it might be common for omnichain contracts to be able to execute different logic from the same onCrossChainCall.

We need to update this PR to be compatible with the code as it is in the main branch.

Going to implement this next as a third part of the swap tutorial:

Basic
With ZETA
With not withdrawals

To simplify things I'm probably not going to use an action integer prefix, but add it as an optional last argument in the message.


Add --config option

It would be interesting to pass a yaml file to the conda-press and it will configure it automatically (using the same options when we using the command line).
That might be interesting to be implemented after we refactor the code to use the object parameter pattern. (#35)
cc: @scopatz

Yep, I like this a lot

Closing in favor of #42


archiver.FileSystem() alternative that takes io.Reader

What would you like to have changed?
In addition to archiver.FileSystem("filename.ext") there should be a function that takes io.Reader or better io.ReaderAt and size. For example archiver.NewFsReader(r io.ReaderAt, size int64).
Why is this feature a useful, necessary, and/or important addition to this project?
This is necessary to use a file thats already open or for files that do not resize on OS filesystem and cannot be opened with os.Open(). For example afero or any other virtual/in memory file system.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
There are no alternatives, currently I can't use archiver.FileSystem with a file on a synthetic FS because archiver assumes the file can be opened with os.Open().
Please link to any relevant issues, pull requests, or other discussions.
Go archive/zip implements NewReader in addition to file Open.
https://pkg.go.dev/archive/zip#NewReader
Similarly SevenZip:
https://pkg.go.dev/github.com/bodgit/sevenzip?utm_source=godoc#NewReader
Thank you!

You want ArchiveFS -- simply specify the Stream field instead of the Path field.
Thanks for using archiver!

It worked, thank you! However it was pretty hard to figure out how to use this correctly. It was crashing on me until Format was specified from Identify() with a cast to archiver.Archival. Identify returns io.Reader to be used in further calls but I don't see an easy way to pass it directly to ArchiveFS which requires SectionReader. For this I used io.NewSectionReader from the opened file. But overall its little confusing. It could use an example. Thank you!

Oh... if you don't know the format ahead of time, I guess that can be a little tricky; because Identify() reads some of the bytes, so you have to use the new reader it returns. I didn't realize you had an unknown format.
Maybe we can add an exported API for calling FileSystem on a stream...

M'kay, I'll leave this open and give it some thought. I'd also accept a proposal to review for quicker turnaround!

Well, this is fantastic, thank you! But I have a more sophisticated case with which I'm, ahem, a bit stuck..

I have an .iso file, which I turn into fs.FS with (a tweaked version of) go-diskfs (after I've managed to mock https://github.com/diskfs/go-diskfs/issues/169)
... from which I get an ar file (debian package[1]) which I turn into fs.FS with archiver.ArchiveFS (plus ar implementation of archiver.Archival)
...from which (I'd like to) have a control.tar.gz and data.tar.xz turned  into corresponding fs.FS(again, with archiver.ArchiveFS) and pick files from there
...and serve all that with http.FileServer(http.FS(myCrazyStackableFs)) of net/http

So, on each layer of abstraction I have an fs.File, which is, unfortunately, not a io.ReaderAt which is expected as an argument of io.NewSectionReader
As a wild guess, I've made a breaking experiment. I've changed ArchiveFS to the following:
type ArchiveFS struct {
	// set one of these
	Path   string     // path to the archive file on disk, or...
	Stream *io.Reader // ...stream from which to read archive

	Format  Archival        // the archive format
	Prefix  string          // optional subdirectory in which to root the fs
	Context context.Context // optional
}

And surprisingly managed to reach up to point number 3 in my unusual journey, but not further, unfortunately.... Any hints would be appreciated!
The idea behind this is pretty simple: you navigate to a web resource which serves you a list of iso files from a directory on disk. You can dig into iso contents by clicking on corresponding name and navigate deeper and deeper, digging inside all known file types.
[1]: Debian binary package (a .deb file) is actually an ar archive, consisting of three files: control.tar.gz - Debian-specific data, data.tar.xz - actual package contents and debian-binary - a text file. Compression formats may vary.

@mholt I'm still new to go and some things seem unusual/unexpected, ha!

Any reason you can't make the Stream field an io.Reader (no pointer)?

Indeed, seems, that pointer type was another issue. I'll experiment more with it soon! Thank you for the hint!

What happened after that?

Seems, I've hit another issue, #371 may be. I can list the top-level dir of control.tar.gz but unable to .Open() files from there...

@aol-nnov Thanks for working on this, sorry for the late reply.
Do you want to update your PR with the latest changes? Then maybe we can focus on #371...

Hey, @mholt !

Do you want to update your PR

I do not have any as yet! I think you have me confused with someone else :)

My bad, you're right -- I guess I'd be curious to see the patch, though -- no guarantees it'll be merged, but curious what it looks like!

@mholt okay, I'll arrange it soon

Implemented in #426


support for encryption at host for virtual machines seems contradictory

Hi
At the top of the article, it says:

Restrictions
Supported for 4k sector size Ultra Disks and Premium SSD v2.

...a few lines down, it says:

Regional availability
Encryption at host is available in all regions for all disk types.

I understood the latter to be correct - i.e. e.g. I have it enabled on a Standard SSD (VM build using Terraform), doesn't require Ultra Disks or Premium SSD v2.

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

ID: ed4de54e-f544-0e42-5b0e-afe148b38667
Version Independent ID: 4220c38a-28ee-87bb-c270-b7fd3e97043b
Content: Enable end-to-end encryption using encryption at host - Azure portal - managed disks - Azure Virtual Machines
Content Source: articles/virtual-machines/disks-enable-host-based-encryption-portal.md
Service: azure-disk-storage
GitHub Login: @roygara
Microsoft Alias: rogarana

@kewalaka
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.

Thanks for your contribution to our documentation
We are moving to a new user feedback system. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Manga with apostrophe in title do not open.

Any manga in my collection that has an apostrophe in the name will not open.
Steps to reproduce the behavior:

Add an apostrophe to any title (or transfer a manga with an apostrophe in the title into the library directory).
Rescan library.
Attempt to open the affected title.
No response from page. (Preliminary window never opens.)

Manga that do not have ' in the title are unaffected. Brackets ( [ ] ), dashes ( - ), exclamation points (!), and parenthesis have no effect. Only apostrophies, so far. Will update report if more are found.

Good catch! I have identified the issue in code, and will probably make a bug fix release later today.

This issue is fixed in v0.1.1. Thanks for the bug report!


rm worker and reputer request retries

Closes: #XXX
What is the purpose of the change
Removes retries for worker and reputer nonces. This is to simplify and lessen operations.
Testing and Verifying
This change is already covered by existing unit and integration tests.
Documentation and Release Note

[x] Does this pull request introduce a new feature or user-facing behavior changes? NO

Where is the change documented?

[] Specification (x/{module}/README.md)
[x] Allora documentation site docs.allora.network source code at: https://github.com/allora-network/docs
[ ] Code comments?
[ ] N/A

This branch will not be merged for now.

We'll keep retries as they're used by reputers for this reason.


✏ fix: lower case "Remove"

This change removes the awkward capitalized "R" in "Remove" for the gitmoji "Add, update, or remove feature flags." This is consistent with gitmoji website https://gitmoji.carloscuesta.me/.

@kevtan Thank you for your PR, here seems to be a problem left over from before.


keyboard shortcut conflicts

Received Oct 2022
"do not use keyboard commands which can conflict with screen readers keyboard commands such as alt+ control+ left arrow and alt+ control+ right arrow are commands for navigation within table. When screen reader is on, user will not be able to navigate within section without pressing NVDA key+3"

Another tester mentions:
"I noticed that most of the keyboard shortcut clashed with the screen reader jaws table reading commands and some windows command."


refactor(Algebra/Module/Submodule/Lattice): increase the priority of Submodule.bot_ext

This PR is incorporated to #4393.


wsl --set-default-version 2 not working on Microsoft Windows [versão 10.0.18363.1016]

I can't run "wsl --set-default-version 2"
And my windows is 10.0.18363.1016
C:\WINDOWS\system32>ver

Microsoft Windows [versão 10.0.18363.1016]

C:\WINDOWS\system32>exit
PS C:\WINDOWS\system32> wsl --set-default-version 2
Opção de linha de comando inválida: --set-default-version
Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe [Argument] [Options...] [CommandLine]

Please check Windows update or install .1049 manually.
This backport has the minor build number: 1049. To summarize, if your minor build number is 1049 or higher on Windows builds 18362 or 18363, then you have the backport and the ability to run WSL 2 distros.
If hit issue #5837, please try KB4566116 manually

We added instructions to our docs to help fix this issue! @licanhua is right you need to update to the latest version.
Check out these instructions and they should resolve your issue. If not, please feel free to reopen. :)


feature request: make it possible to have Message prev/next at bottom

As the setting "Gestures" for next or previous message is still out of function, I think about a alternative.
As the menu within a message is on top, and the previous and next button are small and near together it works not as nice as could be.
So the Idea could be, to made the buttons avalible on bottom of the screen, and increase the size a little bit (or made some space between). After that they are more easyly reachable whith one hand.
This should be switchable (old behaviour and new one) via a switch in preferences.
This is just an Idea, maybe someone of the Devs think it will be helpfull.
It looks like there is a old similar Issue, but the link within is no longer reachable which was mentioned: #2655
BR MP

There's issue #585. We don't have any plans to implement an interim solution.


[Preview]: Deploy Dependency agent to be enabled on Windows virtual machines with Azure Monitoring Agent settings does not get triggered

Describe the bug
On a 2022-datacenter sku VM with the policy intitiative [Preview]: Enable Azure Monitor for VMs with Azure Monitoring Agent(AMA) assigned that gets the AMA agent deployed, does not get the dependency agent installation triggered.
The VM is not identified as an incompliant resource.
The Policy definition appears to be missing the 2022-* imagesku types
Steps to reproduce

Assign policy initiative [Preview]: Enable Azure Monitor for VMs with Azure Monitoring Agent(AMA) to a certain scope
Deploy marketplace VM of sku type 2022-datacenter
The AMA Agent, user assigned identity and DCR are deployed for the VM
However the Dependency agent is not although the assignment parameter  "Enable Process and Dependencies" are set to true.

Screenshots
Evidence that the policy does not produce any incompliant resource the deploy to

Hi @MarcelHeek. Please note we have little influence on built-in policies and cannot fix these. I would recommend you open a support ticket in Azure for this issue.
That being said, this is a known issue and impacts custom gallery images as well as migrated virtual machines, and as you've correctly identified an incomplete list of SKUs. There is an update to this policy on the way that will allow you to skip the OS/SKU check (a flag is provided), which should arrive very soon.

Hi @MarcelHeek FYI we are following up with the policy owners on this. Unfortunately, it isn't something we can fix on short notice, and this will probably take a while to resolve. Will keep you posted. Thanks for highlighting the issue!

Similar issue here, do we know when this might be resolved?

Hi @MarcelHeek, @cloxleywatkins, this has now been resolved as of a few weeks ago. Please use the new initiative https://www.azadvertizer.net/azpolicyinitiativesadvertizer/924bfe3a-762f-40e7-86dd-5c8b95eb09e6.html
Note: the parameter scopeToSupportedImages to skip the OS version check.


Allow empty directories with the same name as the new project to be used as the project directory

Should fix #214

Looking good, except for the one thing I commented on. Waiting for your fix on that before merging.

So, just split
if (Directory.Exists(targetPath) || File.Exists(targetPath))```

?

So, just split
if (Directory.Exists(targetPath) || File.Exists(targetPath))

Yep. Split and add your emptiness-check only on the directory part.

Alright, everything should work now.


add pyinstaller config

Fix #9

JaylyDev, Hi. I downloaded and put all files in to the right folders and named them the correct names. I installed python on to my pc. I went to the directory where nbt-to-mcstructure was located and from cmd shell typed in nbt-to-mcstructure>python . and it errored. Would you please tell me maybe where I should put the folder and how to get things going?


Release 0.16 - alignment with consolidated tooling wrt chain making

After consolidation of eris-cm and eris-pm into eris tooling; some technical debt had to be resolved.  This PR is necessary for this re-alignment in eris https://github.com/eris-ltd/eris/pull/1235 to complete.
checklist:

[x] clean up eris-db dependencies of permissions; merged in #499
[x] permissions utility to convert map[string]int into permissions type
[x] genesis: define constructors for Genesis types to contain explicit dependency on tendermint/go-crypto into tooling; enabling us to inject our own crypto package without coordination with tooling.
[x] genesis: introduce GenesisPrivateValidtor as an intermediary step to removing priv_validator logic from the stack
[x] genesis: provide genesis.GenerateGenesisFileBytes(chainName, []*GenesisAccount, []*GenesisValidator) for tooling
[x] final review

continued in #506


Example/static components

A demo showing a simple site built with (non stateful) components using SolidJS
Features:

CSS modules
Solid components (non stateful)
Global stying and custom props in src/index.css

Mind resolving the merge conflict please?


Not able to select menuitems.

Originally submitted to Google Code by savita.spatil2912 on 10 Dec 2009

Hi,
I am using Python2.6.1,Jython2.5.1,Robot2.1.2 and Selenium library2.2.
Here I am nt able to select menu itmes with any of the available keywords.
I used click element keyword and gave locator as menuid.
Bt still it doesn't work.
ERROR: Element menu1 not found
Can u pls help me in ths?
Regards,
Savita

Originally submitted to Google Code by @yanne on 3 Jan 2010

You need to take a look at the source code of the page that you are trying to test, to
see which kind of identifiers the elements have.
Which keyword are you trying to use? What HTML elements are you trying to manipulate?

Originally submitted to Google Code by @yanne on 3 Feb 2010

Closing this due to lack of information


Ensure configured serv_list is available when fetching slots

Previously, if a cached serv_list existed then these would be the only
servers consulted. However, it is possible that the config serv_list has
been updated which means any new addresses will not be considered.
In most scenarios this is not a problem - the cluster knows the current
active topology. But in the event that all nodes are suddenly lost (for
example, the entire cluster is brought up on new addresses), the cache
presumes itself to still be the source of truth.
This commit appends our configured serv_list to the cached list (if
present), and so if all cached servers fail, it will try from the
configured list.

Thanks for commit, just released 1.05.


Fixes issue with tweens not restarting when triggered in a row.

This PR

Fixes a bug

Describe the changes below:
https://labs.phaser.io/edit.html?src=src/tweens/restart.js
In this example just add an additional tween.restart(); under the existing tween.restart(); to see the issue.
This fix allows multiple restarts to work in a row.

I don't mind merging this, but why on earth would you ever restart a tween multiple times in a row? Sounds like a fix for a copy paste error in userland.

I am using websockets with my phaser game, which calls events to be ran in the game. If the game is minimized during the events, they stack and get called multiple times. I started noticing only events with tweens I restart fail. I do agree this might be a bit of a design flaw on my end.

Thanks for your PR. I have fixed this via another method, but you can now call restart multiple times without it messing up.


Black Screen when playing music from "Local Files"

I'm not sure how the Spotify API handles local files, since the music that you are playing does not come from Spotify. Note that this app doesn't connect with the local Spotify app on your computer, it uses the Spotify Web API


Documentation for disabled_rules in .editorconfig is outdated (as it should be ktlint_disabled_rules)

Expected Behavior
Documentation does not mention deprecated properties. It should mention ktlint_disabled_rules.
Observed Behavior
But it does:

https://pinterest.github.io/ktlint/rules/configuration-ktlint/#disabled-rules
https://pinterest.github.io/ktlint/faq/#how-do-i-globally-disable-a-rule

Steps to Reproduce
Use disabled_rules, get 15:19:37.547 [pool-1-thread-10] WARN com.pinterest.ktlint.core.api.UsesEditorConfigProperties - Property 'disabled_rules' is deprecated: Rename property 'disabled_rules' to 'ktlint_disabled_rules' in all '.editorconfig' files.
Your Environment
ktlint 0.47.0
[*.{kt,kts}]
disabled_rules=trailing-comma-on-declaration-site

Fixed via #1671

Thanks!


Bug: light and dark logos are always displayed

Hello,

Affected version is v0.18.2

I have encountered an issue where the logo I use was showing twice, see example.

Setting up a fresh and clean repo I didn't see the issue but it's still there, both icons are visible but the background hides one of them.

Oh, that must've happened when we switched to next-themes. Thanks for the report, will take a look.

Should be fixed in https://github.com/zuplo/zudoku/releases/tag/v0.18.3


helm/kube-prometheus: Bump alertmanager and prometheus dependency versions

This bumps the version of alertmanager and prometheus dependencies, resolving some errors.
Not sure if there are other implications to these bumps...
Fixes #498

This depends on #497, which has bumped the versions of alertmanager and prometheus charts.

lgtm! thanks!

I was just about to bump the versions again (since they have changed). I'm too slow... :(
At least this fixes the original issue, so it's all good.

Got it, feel free to open PRs as needed :)


feat: k8s clusters data source

What does this fix or implement?
Data source for retrieving a list of k8s clusters which match filtering criteria.

Checklist

[x] PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
[ ] Tests added or updated
[x] Documentation updated
[x] Changelog updated and version incremented (label: upcoming release)
[ ] Github Issue linked if any
[ ] Jira task updated

Let's change cyclo to 25.


feat(Nag Suppressions): granular suppressions

Related to #634
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Not sure why this failed, the read permission on my fork should be configured and it is marked as public?

The GitHub action is running from this repository and does not have permission (rightfully so) to push changes to the fork. In this case the API.md generated from the build process differed from what was pushed to the fork so it attempted to fix that by pushing the new documentation.
To fix that, run the npx projen build  command and push the new API.md to your fork.

You're right, I forgot to run the build, sorry. I've pushed an update.

Good idea! 👍

Update pushed:

I've simplified the rule validateSuppressions method a little. It's not actually necessary to return an array, as the array is either identical to the input or the method throws an error
An example on suppressing findings was already in the readme but I can add more if you want
Added a CFN example to the readme
The change to utils would have prevented us from checking for specific findings in unit tests so that would have broken some of the IAM5 unit tests that I had changed as part of this PR

I think we should have an explicit callout in the README here.  in addition to the examples you've added.
Somthing like the following

Example 5) Granular Suppressions of findings
Certain rules support granular suppressions of findings. If you received the following errors on synth/deploy
[Error at /StackName/rFirstUser/DefaultPolicy/Resource] AwsSolutions-IAM5[Action::s3:*]: The IAM entity contains wildcard permissions and does not have a cdk_nag rule suppression with evidence for those permission.
[Error at /StackName/rFirstUser/DefaultPolicy/Resource] AwsSolutions-IAM5[Resource::*]: The IAM entity contains wildcard permissions and does not have a cdk_nag rule suppression with evidence for those permission.
[Error at /StackName/rSecondUser/DefaultPolicy/Resource] AwsSolutions-IAM5[Action::s3:*]: The IAM entity contains wildcard permissions and does not have a cdk_nag rule suppression with evidence for those permission.
[Error at /StackName/rSecondUser/DefaultPolicy/Resource] AwsSolutions-IAM5[Resource::*]: The IAM entity contains wildcard permissions and does not have a cdk_nag rule suppression with evidence for those permission.

By applying the following suppressions
import { User } from '@aws-cdk/aws-iam';
import { NagSuppressions } from 'cdk-nag';
import { Construct, Stack, StackProps } from '@aws-cdk/core';

export class CdkTestStack extends Stack {
  constructor(scope: Construct, id: string, props?: StackProps) {
    super(scope, id, props);
    const firstUser = new User(this, 'rFirstUser');
    firstUser.addToPolicy(
      new PolicyStatement({
        actions: ['s3:*'],
        resources: ['*'],
      })
    );
    const secondUser = new User(this, 'rSecondUser');
    secondUser.addToPolicy(
      new PolicyStatement({
        actions: ['s3:*'],
        resources: ['*'],
      })
    );
    NagSuppressions.addResourceSuppressions(
      firstUser,
      [
        {
          id: 'AwsSolutions-IAM5',
          reason: "Only suppress AwsSolutions-IAM5 's3:*' finding on First User.",
          appliesTo: ['Action::s3:*'],
        },
      ],
      true
    );
    NagSuppressions.addResourceSuppressions(
      secondUser,
      [
        {
          id: 'AwsSolutions-IAM5',
          reason: "Suppress all AwsSolutions-IAM5 findings on Second User.",
        },
      ],
      true
    );
  }
}

You would see the following error on synth/deploy
[Error at /StackName/rFirstUser/DefaultPolicy/Resource] AwsSolutions-IAM5[Resource::*]: The IAM entity contains wildcard permissions and does not have a cdk_nag rule suppression with evidence for those permission.

* The change to utils would have prevented us from checking for specific findings in unit tests so that would have broken some of the IAM5 unit tests that I had changed as part of this PR

The changes to utils would only affect the TestType.COMPLIANCE tests, not the TestType.NON_COMPLIANCE tests. Without that change we might have some rules with findings that accidentally pass compliance tests because of how the [finding] changes the message output.

Update pushed:

Added the example to the readme
Made the change to the utils. You were right, when I tried it I made the change to both COMPLIANCE and NON_COMPLIANCE which broke it. I've now only changed COMPLIANCE which works.

Thanks for the contribution! 🥳


Version in the HTML title bar should reflect the current version.

The HTML title bar shows the version as 0.3 on the documentation pages : http://openebs.readthedocs.io/en/latest/
OpenEBS uses readthedocs and the source code is at : https://github.com/openebs/openebs/tree/master/documentation
The release version is hardcoded to - 0.3 here: https://github.com/openebs/openebs/blob/master/documentation/source/conf.py
The version should reflect the version of the documentation.

Hi :),
Do you want some automatic thing or just keep it hard coded with the current version?

@marceloabk - yes, that will be great. You can use this issue for fixing that : https://github.com/openebs/openebs/issues/582

Drop down is available for the latest (0.6) and the older version 0.5. When you click on 0.5 it goes to https://v05-docs.openebs.io/ and when you click on Latest it goes to https://docs.openebs.io/


Support modules

Meteor 1.3 supports modules. This means variables may be renamed during the import.
Should the plugin support this? Or should we require all variables to have their default name?
Example:
import Session from 'meteor/session'

// vs

import X from 'meteor/session'

or for non-default exports:
import { Blaze } from 'meteor/blaze'

// vs

import { Blaze as B } from 'meteor/blaze';

Of course the plugin should support this.

This question is more along the lines of whether it's worth the added conpexity and added development time for new rules, not the technical aspect of it

Specifying this in the ESLint config should do the trick nope ?
https://gist.github.com/ThomasCrevoisier/0ccf10961fb7715bbdf67bb8464be430

@ThomasCrevoisier This works already.
The issue is that previously Meteor provided globals (e.g. Meteor, Session) which didn't have to be imported and always had the same name.
Now, with ES modules somebody could do import Sess from 'meteor/session' and then the rules will stop working for Sess because eslint-plugin-meteor doesn't know it should check Sess.
As long as people keep the default names things still work. So far there hasn't been an issue of somebody reporting he needs to be able to use renamed variables.

@dferber90 Okay my bad, I didn't fully understand the problem here. Thanks for the explanation.

Decided not to support it for now.


Adjust the game to work on desktop too.

Check out this article:
https://web.dev/gopherwoord-studios-resizing-html5-games/


Need explanation of what case_col column is from column_metadata table

This is mentioned in the clinical data documentation: https://learn.canceridc.dev/data/organization-of-data/clinical
case_col is a Boolean which is true if and only if the referenced column contains the patient or case id, i.e. if this column is used to determine the value of the dicom_patient_id column

thank you - I did look at that page, but missed it


reverse function

Im using AngularFire2 on my ionic2 project but reverse function not working.

Seems to work here: https://vadimdez.github.io/ng2-order-pipe/

Tnx for your help. I was trying to use wrong way 🙈  Its working very well


[FEATURE] Add Events for native.keyboardhidden & native.keyboardvisible

Opening and closing the keyboard can seriously affect app performance, and it's often best to wait until after the keyboard animation is complete to perform some tasks.

Yeah right now iOS uses UIKeyboardWillHide and UIKeyboardWillShow and Android waits for the View to resize, so they technically aren't even the same thing. Definitely will be adding this for iOS, we'll see about Android.

ping

@tlancina still on your radar?

Yeah not forgotten, I'd like to update the method naming to be consistent as well, but unfortunately have had to prioritize other projects. PRs welcome on this!


Why are not all actions with different runner types executed as user stanley?

Taken from https://docs.stackstorm.com/install/rhel7.html:
"To run local and remote shell actions, StackStorm uses a special system user (default stanley). For remote Linux actions, SSH is used. It is advised to configure identity file based SSH access on all remote hosts. We also recommend configuring SSH access to localhost for running examples and testing."
Local and remote shell actions are executed as the stanley user. It was to my big surprise that another action of mine that uses runner_type python-script instead of shell, is executed as root user instead of stanley.
Why is that? And shouldn't this be consistent?

@pietervogelaar The actionrunner service (which is where all runners are "run") is run as root.  Things like core.local use the local-shell-cmd runner which will drop the user into stanley if sudo param isn't set to true. So it's not actually a runner difference, but rather a runner implementation difference. It might make some sense to spawn our python actions as stanley by default, but that might break existing actions. Could be something we can deprecate over time. Will let others add some input here as I wasn't part of ST2 when the decision to run actionrunner as root was made, so I've not given a lot of critical thought to the implications of running it as st2 user.
/cc @lakshmi-kannan @Kami @enykeev


TestTree to check the richness of a wallet

I would like to be able to state not only that the transaction validates, but also to check that the result is the one I expect, especially to check that a specific wallet has received the token I wanted to give them.

I currently often use variants of:
Tasty.testProperty @Bool
        "Comments here" $
          Cooked.testAllSatisfiesFrom
            (\state ->
              case state of
                Left _ -> False -- The transaction should validate, but refund one of the sender.
                Right (_, utxoState)->
                  let aliceVal = richnessOf utxoState alice
                      bobVal = richnessOf utxoState bob in
                  aliceVal `Plutus.geq` (euros 10_000 Plutus.+ dollars 10_000) ||
                    bobVal `Plutus.geq` (euros 5_500 Plutus.+ dollars 20_000)
            )
            initialDistrib
            theTraceToTest

This would benefit from being directly incorporated to Cooked.

Closing because it is outdated. We now see the full outcome of running a trace, including which wallet owns what.


Make version check for importlib.abc in grpcio-tools more stringent (backport of #24098 to 1.32)

Port of #24098 to 1.32:
@ericgribkoff noticed the following error:
+ python3 -m grpc_tools.protoc --proto_path=. --python_out=tools/run_tests --grpc_python_out=tools/run_tests src/proto/grpc/testing/test.proto src/proto/grpc/testing/messages.proto src/proto/grpc/testing/empty.proto
/usr/bin/python3: Error while finding spec for 'grpc_tools.protoc' (<class 'AttributeError'>: 'module' object has no attribute 'abc')

It appears that importlib.abc was not available in 3.4 (which is deprecated) and our distribtests are apparently not running grpcio-tools. (I've filed an issue for that.) No external users have complained about this yet and if they do, there's an easy fix (use python3.5+ in your build step, a single time), but I'd nevertheless like to get this fixed quickly.

CC @markdroth as release manager. I think this can wait a couple of days, but this is going to require a patch.

Failure:

https://github.com/grpc/grpc/issues/24100


[e2e]: generic push main upload-tag-name slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8181779191
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Trigger: push
Branch: main
Date: Thu Mar  7 02:17:29 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8197683414
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Trigger: push
Branch: main
Date: Fri Mar  8 02:23:54 UTC 2024
Tests are passing now. Closing this issue.


experimental: Makes regex customizable in text_splitter.py (SemanticChunker class)

Description: Currently, the regex is static (r"(?<=[.?!])\s+"), which is only useful for certain use cases. The current change only moves this to be a parameter of split_text(). Which adds flexibility without making it more complex (as the default regex is still the same).
Issue: Not applicable (I searched, no one seems to have created this issue yet).
Dependencies: None.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.

Optionally, i think it's a good idea to implement the same parameter in create_documents(), split_documents() and transform_documents(). Even if by the usage of kwargs.

@eyurtsev Thanks, that actually makes much more sense :D
I've updated the PR with a new commit, moving regex to init as sentence_split_regex.


Improve article 2203.14101

Exact location of issue
2203.14101
Example:
only half of pdf transformed

Since we updated to the latest article versions, 2203.14101 is no longer available. To quote from arXiv, the authors remark:

Comments: This report has been withdrawn by the authors due to critical issues in Section 2.3.1 of Article 2

So I will close with wontfix, even though we still can't convert the original well.


Multiple cover specs found

I've a question.
I'm running common tests using rebar:
rebar -v 1 ct skip_deps=true

rebar.conf contains:
{ct_extra_params, "-ct_hooks cth_surefire -logdir ct_result -cover test/cover.spec"}.

I see that rebar skips running ct in "deps", but still looking for "cover.spec" inside.
So I get an error:
ERROR: Multiple cover specs found
Could you please advise, how it can be resolved ?

This is most likely already fixed, similar to #525, could you please check with rebar 2.6.0 is this still happens?

Closing, please do re-open if issue still occurs


A suggestion: on the selection between element-wise operation and matrix-algebra operation

From the issues:

in scipy.linalg: sinm(2 * A) does not equal to 2 * sinm(A) * cosm(A), but equals to 2 * matrix(sinm(A)) * matrix(cosm(A))

in real applications, for sin(A), where A can be a number, a n-dim array, or a matrix. Given any expression of A, when we change A's type from a number into a matrix, we also need to replace in the expression all function names from sin() into sinm() correspondingly, which is inconvenient, and sometimes cause errors if the user is not familiar

functions like sin, cos, etc., have their element-wise version, sin() and the corresponding matrix version, sinm(), but for multiplication and division * and /, A * B is matrix multiplication, but A/B is element-wise division, which seems to be self-inconsistent

I would like to make the following suggestions:

keep the current versions of sinm, cosm, etc functions

overload the sin, cos, exp, etc functions such that: if the input is a number, return a number; if the input is a n-dim array, perform element-wise arithmetic and return a n-dim array; if the input is a matrix, perform matrix algebra (i.e. sinm, cosm, expm, etc) and return a matrix

the same rule applies to multiplication and division, where A/B should be A * inv(B) if A and B are both matrices. Currently, when A and B are both matrices, A * B is matrix multiplication, but A/B is an element-wise division, which is self-inconsistent. Element-wise arithmetic should apply only if at least one of A and B is an n-dim array

The main self-inconsistency lies in that, the selection between element-wise operation and matrix-algebra operation:

a) for functions like sin(), exp(), etc, it is done by appending a 'm' to the function name
b) for multiplication * and functions like pow(), etc, it is done by checking whether the input is an n-dim array or a matrix
c) for division, it is always element-wise regardless of input type

Thus, I feel that it is better to use the same rule (i.e. b) to perform the selection for all cases, that would make life easier.
Will this modification break too many existing packages?

The best way to avoid these inconsistencies is to avoid using np.matrix. To perform matrix multiplication, this means calling the dot function or ndarray method; in Python 3.5, you'll be able to use the @ operator.
I'd suggest taking this to the numpy discussion list.  There doesn't appear to by any actionable items here for scipy.  np.matrix is provided by numpy and all or essentially all of scipy.linalg returns arrays when given np.matrix.  I'm tempted to close this, but I'll hold off for a while if others wish to comment.

The only actionable thing currently on scipy side would be to be
consistent in returning np.matrix output for np.matrix input.

If afraid of breaking existing package dependencies, 1 possibility is to implement new functions under scipy.linalg, i.e., scipy.linalg.sin, scipy.linalg.cos, scipy.linalg.exp, which gives matrix-in-matrix-out under matrix algebra, array-in-array-out under element-wise algebra, and number-in-number-out under standard algebra.
This would minimize the chance of incompatibility.

The consensus in the NumPy/SciPy community is that np.matrix was a mistake and should not be used in new code. The confusion is real, but it can only get worse if we introduce more code that handles np.matrix specially.
I'm also not for @pv's suggestion. Existing code might rely on these functions returning ndarray even if the input is (inadvertently) an np.matrix.

@larsmans , @pv , I hope instead of complaining how bad is np.matrix or how bad is someone's suggestion, we should try to figure out a good solution, convenient to use. So, when the input is a nxn math object, how can existing operators and functions distinguish between element-wise operation and matrix operation?
By checking whether the input is an ndarray or matrix, or by checking whether the function name ends with 'm'? The existing solution, i.e. a), b), c) in the main post, is definitely not a good solution for users, because it is not consistent throughout, some use this, some use that, some use none. In particular, the * / operators cannot append a 'm'.
If you do not have time to implement, that does not mean you should try to reject others' suggestions. So what is the ideal solution in your mind?

@xuancong84: you are jumping into a discussion that has been discussed before. The current approach used by most is to use ndarrays only.

In principle, there could be room for a separate matrix object, but the user and developer experience so far with np.matrix has not been particularly good. The current design is however fixed in place due to backward compatibility issues, so the best option for new design would be to start from scratch. So far, nobody has made concrete suggestions, probably partly due to the fact that the ndarray-only works fine for most purposes.

Nothing is going to happen here, so closing the issue,
@xuancong84 if you want to know more about the history, look at the "deprecate numpy.matrix" thread from February 2014 on the numpy mailing list. Also, Python 3.5 introduces the @ operator which is a matrix multiplication operator for numpy arrays.


feat(platform): user info

Looks like when it's smaller than 992px, the user info callout won't show up ?

Looks like when it's smaller than 992px, the user info callout won't show up ?

Yes. If on a small screen, it will come to a separate page, perfsee.com/me


Cancelable.cancel() should return Unit and not Boolean

We've used Cancelable.cancel() for synchronization.
It's useful, but it imposes a synchronization burden on cancel (beyond the idempotency guarantee) and it's not compatible with other similar interfaces.

Done.


Cannot import build.zig on Windows

It looks like you can't import build.zig when building on Windows. It's maybe some file encoding issue going on because the error messages are really weird.
D:\a\capy\capy\vendor\zelda\zig-libressl\libressl\build.zig:449:26: error: expected ';' after declaration
        \\char {s}(void);
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
D:\a\capy\capy\vendor\zelda\zig-libressl\libressl\build.zig:450:34: note: invalid byte: 'a'
        \\int main(int ac, char* av[]) {{
                                 ^

Can you still reproduce this on zig HEAD?


Add full description to event in synchronized calendar

Fix #58

Task linked: UKIT-2 Suggestion : adding the classroom number on the calendar event info when synchronized


fix: fixing integration test

Description

Fix logs integration test

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

v1.11.1
GitHub release

Your semantic-release bot :package::rocket:


Conflicts with syslog_access and superuser=false

Hello.
I am trying to give an user syslog_access="UNRESTRICTED" while this user is not a superuser, since I know this is not a problem in Redshift but I am finding this error o the plan phase.
│ Error: Conflicting configuration arguments
│
│   with module....
│   on modules/.../main.tf line 4, in resource "redshift_user" "this":
│    4:   superuser       = var.superuser
│
│ "superuser": conflicts with syslog_access

There is a way to solve it? Thanks

Hello,
the conflict is due to how terraform handles conflicting fields, without taking the value into consideration. I will create a necessary change to allow use of syslog_access  and superuser and only do the validation when the later is set to true.


Inconsistent ChangeId format in Route 53

Describe the bug
When using the Route 53 client, you currently need to alter the change id coming out of the change_resource_record_sets() call when calling get_change(). The former returns change ids prefixed with /change/, while the latter expects this prefix to be omitted.
For example (pseudocode), this is what's required:
    let crrso = r53.change_resource_record_sets().hosted_zone_id(...).change_batch(...).send().await.unwrap();

    // orig_change_id is `/change/C01234567AAAAAAAAAAAA`
    let orig_change_id = crrso.change_info.unwrap().id.unwrap();

    // change_id is just the C01234... part
    let change_id = change_id.split_at(8).1.to_string();
    let gco = r53.get_change().id(change_id).send().await;

Expected Behavior
I expect to be able to pass the change id from one API call to the next unaltered.
Current Behavior
The call fails unless I remove /change/ from the change id.
The problem can be seen on line 518 of the attached run.log: it creates a URI of the form /2013-04-01/change/%252Fchange%252F<raw-id>.
In the call that succeeds, the URI is of the form /2013-04-01/change/<raw-id>.
I have redacted the hosted zone id from the logs.
run.log
Reproduction Steps
Attached is a small program that reproduces this issue. I've (again) redacted the Route 53 hosted zone id.
main.rs.txt
The output is:
Change ID: /change/C0472137U0LRYA30WCRM
Route 53 GetChange failed: NoSuchChange: Could not find resource with ID: /change/C0472137U0LRYA30WCRM
Route 53 GetChange: GetChangeOutput { change_info: Some(ChangeInfo { id: Some("/change/C0472137U0LRYA30WCRM"), status: Some(Pending), submitted_at: Some(DateTime { seconds:<PHONE_NUMBER>, subsecond_nanos: 486000000 }), comment: None }) }

I would expect the second line (Route 53 GetChange failed) to not be present, and the mutating logic on lines 32-35 to not be needed.
Possible Solution
Boto doesn't seem to have this problem; it looks like they have some custom logic in a hook to munge the ids.
Looking at the botocore model file, GetChange looks like this:
    "GetChange":{
      "name":"GetChange",
      "http":{
        "method":"GET",
        "requestUri":"/2013-04-01/change/{Id}"
      },
      ...
    }

So they're just passing in the raw part of the id.
Then, in a global list of API mungers, they inject fix_route53_ids into a step called before-parameter-build for Route 53.
Some quick skimming suggests this is already being generated (?!) for /hostedzone/ ids in hosted_zone_preprocessor.rs. Maybe something needs to be tickled to tell the Smithy generator to do this for change ids, as well?
Additional Information/Context
No response
Version
0.13.0
Environment details (OS name and version, etc.)
MacOS 12.4, M1 (uname -a: Darwin dacBook2021.local 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 arm64)
Logs
See above

It's buried in my wall of text above 😀, but this is the relevant bit from Boto3: https://github.com/boto/botocore/blob/develop/botocore/handlers.py#L621-L642

I'm working on tickling smithy to fix this and I should have a PR soon


Release balenaOS @ 2.68 for Intel NUC on production.

Need for balenaOS @ 2.68 for Intel NUC on production.

This is now in production


Is there an easy way to change language to english?

I really like your boilerplate here. I tried changing the locale in the app.php from chinese to english but it seemed to have no effect. All the menus are still in chinese. It would be great if you could switch between the two languages :)

I'm about to finish the translation

awesome!!

cool，I'll try my best to finish


How to change a misskey instance's domain?

Summary
Hi. I'm trying to change the domain for my instance. Is it OK to just modify .config/default.yml:url?
I've tried it but it seems another instance would respond 500 FAILED_TO_RESOLVE_REMOTE_USER

This is not possible because Fediverse does not handle domain changes. If you want to use a different domain, you will need to create a new separate instance.

This is not possible because Fediverse does not handle domain changes. If you want to use a different domain, you will need to create a new separate instance.

Got it. Thank you!
On Sat, Jan 30, 2021, 10:08 PM syuilo<EMAIL_ADDRESS>wrote:

This is not possible because Fediverse does not handle domain changes. If
you want to use a different domain, you will need to create a new separate
instance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/syuilo/misskey/issues/7137#issuecomment-770217863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBWKKDNV6K343O3ZNBJ4T3S4QHEPANCNFSM4W2KM2UQ
.

Got it. Thank you!
On Sat, Jan 30, 2021, 10:08 PM syuilo<EMAIL_ADDRESS>wrote:

This is not possible because Fediverse does not handle domain changes. If
you want to use a different domain, you will need to create a new separate
instance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/syuilo/misskey/issues/7137#issuecomment-770217863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBWKKDNV6K343O3ZNBJ4T3S4QHEPANCNFSM4W2KM2UQ
.


Issue 264 doco

Added comments to RowsCounter for auto-generated documentation
Shortened RowsCounter properties names
Fixed affected unit tests

#237 and #197 related

:+1:


Adds recommendations to help keep region-specific forks clean

These recommendations are intended to help region specific forks stay clean wrt code and changes in Covid Green while at the same time allowing for limited region specific changes where necessary.

I've opened this PR to begin the conversation about these recommendations. I'm sure they don't cover all cases and would love to get and incorporate feedback from other project contributors.

Just needs one additional sign off from anyone in @covidgreen/members to land


  The setup works just fine, but then the spout, tank, pipes, and item drain filled up and I get occasional crashes.  I wasn't sure at first what was causing it, but it seems like the item drain is the culprit per the crash report.
I'm not entirely sure how to reproduce the problem, but I can share a culled version of my world uploaded so that you can see it for yourself.  An annoying thing is that it doesn't always crash when the item drain is loaded, but it happens occasionally--not occasionally enough to be able to ignore it.
I am not using the latest version of the mod simply because my game won't run with it because of an incompatibility and subsequent crash on startup with a common dependency (or so I understand it) with the Twilight Forest mod which is also installed.  That is preventing me from testing it with the latest version of Create installed.  That also means that I can't verify if it's happening because of another mod or not.
Reproduction Steps

Load up the provided world
Spend time in the vicinity/loading the item drain in question (it's the only one so far)
The bug surfaces and the game crashes suddenly and without too much warning

Expected Result
It doesn't cause the game to crash.
Screenshots and Videos
No response
Crash Report or Log
https://1drv.ms/t/s!AtpBOFa0mPoVjN1c_wFTwGIssuwxtw?e=v9zDf6
Operating System
Windows 11
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods
Full list of CurseForge-installed mods:
appleskin-fabric-mc1.19-2.4.1.jar
architectury-6.4.62-fabric.jar
BetterAdvancements-Fabric-1.19.2-<IP_ADDRESS>.jar
BetterF3-4.0.0-Fabric-1.19.2.jar
bettermounthud-1.2.0.jar
betterstats-2.2.1+1.19.2.jar
Bookshelf-Fabric-1.19.2-16.2.17.jar
clickadv-fabric-3.0.jar
cloth-config-8.2.88-fabric.jar
Clumps-fabric-1.19.2-9.0.0+14.jar
Controlling-fabric-1.19.2-10.0+7.jar
create-fabric-0.5.0g-796+1.19.2.jar
Decorative Blocks-fabric-1.19.2-3.0.0.jar
fabric-api-0.73.2+1.19.2.jar
fabric-language-kotlin-1.9.1+kotlin.1.8.10.jar
freecam-1.1.6+1.19.jar
held-item-info-1.4.0.jar
indium-1.0.9+mc1.19.2.jar
InventoryProfilesNext-fabric-1.19-1.9.2.jar
iris-mc1.19.2-1.5.0.jar
Jade-1.19.1-fabric-8.7.3.jar
JadeAddons-1.19.2-fabric-3.0.0.jar
lambdynamiclights-2.2.0+1.19.2.jar
libIPN-fabric-1.19-2.0.2.jar
lithium-fabric-mc1.19.2-0.10.4.jar
malilib-fabric-1.19.2-0.13.0.jar
minihud-fabric-1.19.2-0.23.3.jar
modmenu-4.1.2.jar
MouseTweaks-fabric-mc1.19-2.22.jar
Oh_The_Biomes_You'll_Go-fabric-1.19.2-<IP_ADDRESS>.jar
openblockselevator-0.0.2-1.19.X.jar
reeses_sodium_options-1.4.9+mc1.19.2-build.67.jar
rer-2.6.0.jar
RoughlyEnoughItems-9.1.587.jar
RoughlyEnoughLootTables-1.19-1.0.jar
RoughlyEnoughProfessions-fabric-1.19.2-1.1.3.jar
RoughlyEnoughTrades-1.19-1.0.jar
sodium-extra-0.4.16+mc1.19.2-build.90.jar
sodium-fabric-mc1.19.2-0.4.4+build.18.jar
spark-1.10.17-fabric.jar
TerraBlender-fabric-1.19.2-<IP_ADDRESS>.jar
ToolStats-Fabric-1.19.2-12.0.2.jar
twilightforest-fabric-1.19.2-4.2.333.jar
worldedit-mod-7.2.12.jar
YetAnotherConfigLib-2.2.0-for-1.19.2.jar
youre-in-grave-danger-1.4.8.jar
Zoomify-2.9.0.jar
Additional Context
No response

Please install this and get it to happen again.

K.  The crash log I was given when the game crashed this time is here:
https://1drv.ms/t/s!AtpBOFa0mPoVjN1djrdWLpieZ-Nc1g?e=FskbNT

Looking again, I see the issue, it's just Create.


installing error

when i run the tool i get this error
[*] Running backdoor-apk.sh v0.2.4a on Thu 09 May 2019 05:39:05 PM EDT
./backdoor-apk.sh: line 134: $LOG_FILE: ambiguous redirect
[!] Check your environment and configuration. Couldn't find: msfvenom

@pretech86 Try this stackoverflow Q&A: https://stackoverflow.com/questions/2462385/getting-an-ambiguous-redirect-error
The following message is letting you know that 'msfvenom' is not in your path:
[!] Check your environment and configuration. Couldn't find: msfvenom


[bug] version 1.0.8 is mismatched

When I use the property "color" in the styled component, it is not working.
It was working fine in version 1.0.4. After upgrade to 1.0.8 something changed and it is not working anymore.

Need more info to debug as it’s working currently. There’s a compiler bug I think you’re referring to on native. Try turning off compiler on native. Fix is almost ready and will be out today.

I have problem with web. I will try to create small reproduction now

import { SizableText, styled } from 'tamagui';

export const StyledSizableText = styled(SizableText, {
  name: 'TextSizableText',
  variants: {
    muted: {
      true: {
        color: 'red',
      },
    },
  } as const,
});

Text is always black

@natew as I mentioned in previous example probably it is somehow connected to styled methods

One small improvement I also see font-family as element attribute. we should remove it.
TEST

Will check, thanks. I did notice that attribute is falling through too.

Thank you

It is probably related to this change:
https://github.com/tamagui/tamagui/commit/7d713b276c52e5099fca42e595637b8f4c1f4417#r96119380

That was fixed before release it uses name now, but found the issue, 1.0.10 going out now!


Move optional fields to CompleteBuilder

Part of #218
@nikitin-da PTAL

I'll update it, @nikitin-da don't merge please


Functionality Request: Cleanup for printing

I often get sent pictures of some pages taken with a phone (sometimes as single pictures or turned into a pdf), they are usually yellowish and sometimes skewed. Is there an automatic way to automatically rotate, skew and cleanup background noise on those so they can be printed more efficiently?
With cleaning up I mean to make the background white, clean dust, deskew, rotate, like this:

is this something viable?

yes it is viable and is a planned feature we want to add
Sadly it's just low priority over other improvements etc rn due to it being a less requested feature
But we do plan to add it!


not currently conda installable

What
Remove conda install steps until it's available in conda-forge and bump the version to prepare for release

do we wanna get rid of the conda stuff? https://github.com/conda-forge/staged-recipes/pull/14089 should probably be merged in pretty soon

@ryanSoley yea, it may take some time for it to become available on conda-forge still -- it'll be a quick update to switch it back


[vue3.x] Markers smush together if the value does not match the interval

Describe the bug
I am using the slider purely to display values (disabling the input). Many of the values I will display are a fraction of a number & have a similar min/max (E.G. 0.00003 with a min/max of 0.000012/0.003). If the interval doesn't match all of these values, then the component visually breaks
Is there a way to disable the interval since it is not useful for my usecase and manually generating an interval that matches all three values could be difficult with floating point weirdness.
Possibly related to #352
Additional context
Simple reproduction case: https://jsfiddle.net/hysnajgr/1/
You can see how most of the markers & value get pushed to the end despite the fact that they should be evenly spaced with the value nearer to the left hand side.
Environment

Vue version: latest
Component Version: latest

@Flambe You should set interval, otherwise it defaults to 1.
https://jsfiddle.net/p7Lswnz8/1/

There is no way not to use interval, the value of the slider always needs a precision.
Also I can't reproduce the problem: https://jsfiddle.net/yqgts5em/4/

I have figured out why you were unable to reproduce this issue. I am dynamically generating the min/max so the marks are always evenly spaced from either side. Floating point errors sometimes appear which I believe are causing this issue. https://jsfiddle.net/odjbxv5p/

Strangely the slider at the bottom is still working, despite having the same floating point issues so perhaps I'm wrong? https://jsfiddle.net/odjbxv5p/1/

@Flambe
There is no difference between internal and external calculations of components.
It is recommended that you use a third-party library to solve the accuracy problem, which should be fixed.

I've figured out a quick fix solution by just grabbing the longest decimal place and using that for the interval: https://jsfiddle.net/qwcdzyp0/
Though yeah, generating min/max more accurately is absolutely a better long term solution.
For now though, this issue appears to be fixed for me, thank you for the assistance!


Incompatibility with create ?

It might be because the mod updated to the newest version of create and I am at the one before it (0.5.0.i), but there seems to be an incompatibility at loading time with the mod.
Checking the crash log, it seems like this relates to the movement behaviour when on a contraption?
Here is my crash log

Did you try installing previous version of SootyChimneys? 1.1.1 will probably work only with Create 0.5.1.


EnvoyPatchPolicy JsonPath docs & fixes

What type of PR is this?

"fix: throw error if jsonPath returns no jsonPointers"
"fix: allow selecting properties in jsonPath with special chars"
"fix: generate jsonPointer and encode special chars"
"docs: improved api (property descriptions)"
"docs: added example"

Which issue(s) this PR fixes:
Fixes #4162
Fixes #4043

cc: @arkodg


Node 16 deprecation

Node16 will be deprecated on 09/11/2023 (link).
Node 16 is used by the action at the moment according to the source code: https://github.com/actions/setup-node/blob/5e21ff4d9bc1a8cf6de233a3057d20ec6b3fb69d/action.yml#L35-L36
Is there a plan to release a node version update soon?

Hello, @kinano! Thank you for creating an issue, we'll look into this :)

@dusan-trickovic
Based on the announcement GitHub Actions: Transitioning from Node 16 to Node 20 the current version of this JavaScript Action v3.8.1 will cause node16 deprecation notices to be generated starting on October 23, 2023.
So apart from the fact the Node.js 16 is already in end-of-life status, it will soon start to visibly affect GitHub Action workflows using actions/setup-node if no steps are taken to provide an updated release running on node20.
Please release a new version supporting node20 as requested by @kinano!

Hello @MikeMcC399! Thank you very much for your input, we are looking into this :)

Hello @dusan-trickovic

Thank you very much for your input, we are looking into this :)

Do you have any result from looking at the issue? Have you got plans to implement now?
Deprecation notices are supposed to start being displayed today.

This issue is resolved through PR #866 and release of<EMAIL_ADDRESS>

Hello everyone. The new version with support of node20 was released in v4.0.0. For now I'm going to close the issue.

@dusan-trickovic sorry to tag but I updated my workflows like node-version: 20 or even as 'latest', and in the logs it downloads the .tar or gets from cache correctly. But on the workflow run's page I still get 'Node 16 deprecated' flooded warnings. Is there anything I'm missing?

@rwader-swi
You need to change actions/setup-node@v3 to actions/setup-node@v4 in your workflow.


[SIP] Your Title Here (do not add SIP number)

Please make sure you are familiar with the SIP process documented
here. The SIP will be numbered by a committer upon acceptance.
[SIP] Proposal for ...
Motivation
Description of the problem to be solved.
Proposed Change
Describe how the feature will be implemented, or the problem will be solved. If possible, include mocks, screenshots, or screencasts (even if from different tools).
New or Changed Public Interfaces
Describe any new additions to the model, views or REST endpoints. Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed.
New dependencies
Describe any npm/PyPI packages that are required. Are they actively maintained? What are their licenses?
Migration Plan and Compatibility
Describe any database migrations that are necessary, or updates to stored URLs.
Rejected Alternatives
Describe alternative approaches that were considered and rejected.

This looks like an accident, since there's no content. Closing... but happy to reopen/review it if you fill out the pertinent details!


Add d100 support in diceFont

ADdded in #3197, Dicefont has a d10, but not a d100, that is not a problem since they use the same shape, just add numbers from 00 to 99. we use less, so use a loop if you can.

Hey there, first time contributing to open source. I think I was able to implement this, please check the PR when y'all have time. Lmk if there's another/better way to go about doing this.


ViewPagerAndroid is not rendered under ScrollView

ViewPagerAndroid does not render anything when it is used under a ScrollView. I submit a question on StackOverflow about it. Any idea whats the problem is?
http://stackoverflow.com/questions/36014191/viewpagerandroid-is-not-rendered-under-scrollview-using-react-native
Thanks

Commented on your SO question. Let's discuss there. Thanks for using Stack Overflow for questions!

@facebook-github-bot stack-overflow

@cubbuk Did you manage to fix your problem? I have the same issue. removeClippedSubviews={false} seems to fix the issue, but that's a horrible fix. Any thoughts?

Nope @ramilushev , I stopped using it under scroll view.

Adding height to the View pager kind of works

It is an old question but I also faced simmilar issue and solved it by adding contentContainerStyle={{ flex: 1 }} to scrollview tag. E.g.
<View style={{ flex: 1 }}>     <ScrollView style={{ flex: 1 }} contentContainerStyle={{ flex: 1 }}>         <ViewPagerAndroid style={{ flex: 1 }} initialPage={0}>             <View><Text>View 1</Text></View>             <View><Text>View 2</Text></View>             <View><Text>View 3</Text></View>         </ViewPagerAndroid>     </ScrollView>     {/*some other views*/}     <View style={{ height: 20, width: null, flex: 1 }}/> </View>

Adding flex 1 makes it so viewpagerandroid has no height or trimmed to the height of the screen height thus no scroll. How do I have viewpagerandroid under scroll view under android?


Need a more flexible environment.yml file

I did the most recent pull but failed to find the environment. Can we have a more flexible environment (e.g. compare with everyone's package version and determined the necessary ones?
conda env create -f environment.yml

Collecting package metadata (repodata.json): done
Solving environment: failed
ResolvePackageNotFound:
xorg-libxdmcp==1.1.3=h27ca646_0
keyring==24.2.0=py311h267d04e_0
ncurses==6.4=h7ea286d_0
libjpeg-turbo==<IP_ADDRESS>=h1a8c8d9_0
libcblas==3.9.0=17_osxarm64_openblas
libdeflate==1.18=h1a8c8d9_0
libbrotlienc==1.0.9=h1a8c8d9_9
pyyaml==6.0=py311he2be06e_5
astropy==5.3.1=py311hb49d859_0
lerc==4.0.0=h9a09cb3_0
liblapack==3.9.0=17_osxarm64_openblas
libopenblas==0.3.23=openmp_hc731615_0
openssl==3.1.1=h53f4e23_1
libffi==3.4.2=h3422bc3_5
xorg-libxau==1.0.11=hb547adb_0
libgfortran==5.0.0=12_3_0_hd922786_0
readline==8.2=h92ec313_1
libpng==1.6.39=h76d750c_0
libzlib==1.2.13=h53f4e23_5
pthread-stubs==0.4=h27ca646_1001
freetype==2.12.1=hd633e50_1
libblas==3.9.0=17_osxarm64_openblas
tornado==6.3.2=py311heffc1b2_0
yaml==0.2.5=h3422bc3_2
matplotlib-base==3.7.2=py311h3bc9839_0
tk==8.6.12=he1e0b03_0
pandas==2.0.3=py311h9e438b8_1
openjpeg==2.5.0=hbc2ba62_2
libcxx==16.0.6=h4653b0c_0
matplotlib==3.7.2=py311ha1ab1f8_0
pyerfa==<IP_ADDRESS>=py311h4add359_0
pillow==10.0.0=py311h095fde6_0
lcms2==2.15=hd835a16_1
libwebp-base==1.3.1=hb547adb_0
numpy==1.25.1=py311hb8f3215_0
kiwisolver==1.4.4=py311hd6ee22a_1
libxcb==1.15=hf346824_0
scipy==1.11.1=py311h93d07a4_0
llvm-openmp==16.0.6=h1c12783_0
bzip2==1.0.8=h3422bc3_4
libexpat==2.5.0=hb7217d7_1
python==3.11.4=h47c9636_0_cpython
libgfortran5==12.3.0=ha3a6a3e_0
brotli-python==1.0.9=py311ha397e9f_9
libtiff==4.5.1=h23a1a89_0
libbrotlidec==1.0.9=h1a8c8d9_9
libsqlite==3.42.0=hb31c410_0
ca-certificates==2023.5.7=hf0a4a13_0
xz==5.2.6=h57fd34a_0
contourpy==1.1.0=py311he4fd1f5_0
fonttools==4.41.1=py311heffc1b2_0
brotli-bin==1.0.9=h1a8c8d9_9
libbrotlicommon==1.0.9=h1a8c8d9_9
brotli==1.0.9=h1a8c8d9_9
zstd==1.5.2=h4f39d0f_7

I learned from the sciware forum:

use the top-level packages, and only put version restrictions if I know there's an issue (e.g., I updated matplotlib to use a newer feature).
grep -h 'import' dir/*py | sort | uniq will generate a list of all your unique import statements, which is an easier place to start then going through all your .py files manually

@chihchunhsu , Why don't you take a stab at generating us a new, simpler environment.yml file.

Progress was made in #105 but I think we may still need add git-lfs to it.


Improve Batch output instructions and add README to login node

This change:

Adds more explicit instructions about created Batch job template and instance template
Adds a README.md file to the folder generated on the login node
Renames Google Cloud Batch to Batch in documentation

Example output:
instructions_batch-job = <<EOT

A Batch job template file has been created locally at:
  /***/hpc-toolkit/simple-batch/primary/cloud-batch-simple-batch.json

An instance template was created for your Batch job & referenced in the above file:
  https://www.googleapis.com/compute/v1/projects/***/global/instanceTemplates/simple-batch-instance-template-20221011005718936600000001

Use the following commands to:
Submit your job:
  gcloud alpha batch jobs submit simple-batch --config=/***/hpc-toolkit/simple-batch/primary/cloud-batch-simple-batch.json --location=us-central1 --project=***

Check status:
  gcloud alpha batch jobs describe simple-batch --location=us-central1 --project=*** | grep state:

Delete job:
  gcloud alpha batch jobs delete simple-batch --location=us-central1 --project=***

List all jobs:
  gcloud alpha batch jobs list --project=***

EOT

Submission Checklist

[x] Have you installed and run this change against pre-commit? (pre-commit install)
[x] Are all tests passing? (make tests)
[x] Have you written unit tests to cover this change?
[x] Is unit test coverage still above 80%?
[x] Have you updated all applicable documentation?
[x] Have you followed the guidelines in our Contributing document?

(A) we are probably relying alphanumeric order of module ID and output name (B) we are relying on the user to explicitly add the outputs in the blueprint.
Re: (A) it is a better solution than the primary alternative (nothing at all)
Re: (B) I assume our cloud-batch example only adds instructions for the cloud-batch-login-node because they would be duplicative of the cloud-batch-job instructions?

I agree there are some deficiencies with this pattern but I do not know a better way to go about this. We have used this pattern elsewhere, for example in the dashboard module. I especially do not like that the instructions do not print when there is a failure, for example if you add a wait for startup and it fails then you never see the instructions.
For (B) you are correct, the information is basically duplicate but environment specific so they only need to print one.
I don't think there is any action here, LMK if you have ideas.

No action needed, I just think we need to be sure we understand the limits of output instructions and understand the particular choices in our Batch module.


A question about the SSD training

Hi, albanie,
Thanks a lot for your work.
Recently, I'd like to use SSD. To make sure the SSD work fine, I first tried to train the SSD on the provided VOC. I did not change anything. However, in training, the loss becomes weird as follows:
ssd_pascal_train
Experiment name: ssd-pascal-0712-vt-32-300-flip-patch-distort
Training set: 0712
Testing set: 07
Prune checkpoints: 0
GPU: 1
Batch size: 32
Train + val: 1
Flip: 1
Patches: 1
Zoom: 0
Distort: 1
Learning Rate Schedule:
0.001 0.001 (warmup)
0.001 for 73 epochs
0.0001 for 35 epochs
Run experiment with these parameters? y or n
y
Warning: The model appears to be simplenn model. Using fromSimpleNN instead.
In dagnn.DagNN.loadobj (line 19)
In ssd_zoo (line 29)
In ssd_init (line 28)
In ssd_train (line 19)
In ssd_pascal_train (line 213)
Warning: The most recent version of vl_nnloss normalizes the loss by the batch size. The current
version does not. A workaround is being used, but consider updating MatConvNet.

Thanks

By the way, I trained it on Windows 10 using MatConvNet-25. I do not know if this will affect the training.

This was already pointed out in previous issues. The default values for learning rate are too high, which leads to your problem, try lower values.

Hi,
I have the same problem with training in which the loss values become NaN. I traied lower values for "steadyLR" and "gentleLR" parameters, but the problem still exists.

Hi, @mnnejati ,
You may try to change steadyLR to 0.0001 and gentleLR to 0.00001 to train the SSD. I did so, and the training process seems normal so far.
Best,


Add return to Integration creation and fix typo

The return statement was missing for the create() method.
If I was an over-achiever I would also add tests to reflect this change, however, I just wanted thing to work.
Also, I believe that the word incident was used where service was appropriate.

lgtm

Awesome, thanks @ashleyabrooks!
When might we expect a release to PyPI?


Avoid render empty div for component

Using  renderSync with jsx
async function Button(this: SeqflowFunctionContext) {
	this.renderSync(<button id="increment">hi</button>);
}

export async function Main(this: SeqflowFunctionContext) {
	this.renderSync(<Button />)
}

start(document.getElementById("root"), Main, undefined, {});

produces div#root => div => button#increment.
This happends inside createDOMElement function.
Is this behavior wanted?

Hi!
Currently, the div is required because SeqFlow always needs a valid HTML element for children. With it, the parent can easily attach events to children.
Otherwise, it could be challenging to handle edge cases like:

the child waits for a while to render their content.

async function Button(this: SeqflowFunctionContext) {
        await new Promise(res => setTimeout(res, 1000)) // just wait for a while
	this.renderSync(<button id="increment">hi</button>);
}
export async function Main(this: SeqflowFunctionContext) {
        const button = <Button />
	this.renderSync(button)
	const events = this.waitEvents('click', { el: button }) // <--- we can do this?
	for await (const ev of events) {
		console.log('new event', ev)
	}
}

the child replaces its content with a new one. What should happen to the attached handlers?

async function Button(this: SeqflowFunctionContext) {
	this.renderSync(<button id="increment">hi</button>);
        await new Promise(res => setTimeout(res, 1000)) // just wait for a while
	this.renderSync(<button id="increment">hello</button>);
}
export async function Main(this: SeqflowFunctionContext) {
        const button = <Button />
	this.renderSync(button)
	const events = this.waitEvents('click', { el: button }) // <--- What happen here when `Button` re-render itself?
	for await (const ev of events) {
		console.log('new event', ev)
	}
}

The above list is just an example. There are also other edge cases.
SeqFlow allows to put classes on that div to customize the look and feel. For instance, you can write something like:
async function Button(this: SeqflowFunctionContext) {
	this._el.classList.add("another-class") // put a class generically valid, independent where this component is put
	this.renderSync(<button id="increment">hi</button>);
}

export async function Main(this: SeqflowFunctionContext) {
	this.renderSync(<Button  wrapperClass="myclass" />) // `wrapperClass` allows to specify classes that depend on the parent, like width or positions.
}

Some examples of the usage:

https://github.com/search?q=repo:allevo/seqflow-js wrapperClass&type=code
https://github.com/search?q=repo:allevo/seqflow-js this._el.classList&type=code

It' true.
But maybe to ensure consistency it better to add a div also for renderSync with non component method?
Thank for excellent explanation. I will close it :)


Asciidocj integration

Hi,
You will find my contribution to make asciidocfx generates pdf with asciidocj for backend instead of FOP.

Thanks @triaubaral for the initial changes. Our requirements are:

Migration from asciidoctor.js extensions to asciidoctorj extensions
** chart plugin, math plugin, plantuml plugin, ditaa plugin, tree plugin
supporting reveal.js with asciidoctorj
pdf plugin customization in UI
switching option from  asciidoctorj-pdf to fop by user


Article does not align with "Account permissions and security settings in SP Servers"

This article does not align with the naming conventions used in https://docs.microsoft.com/en-us/sharepoint/install/account-permissions-and-security-settings-in-sharepoint-server-2016. For more information about naming conventions for accounts see #319
Also see #810 and #811 for more details on this issue

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

ID: d92c42e5-2016-b7d7-a232-d2a16b098892
Version Independent ID: 9b03a07a-5056-d33f-fc4f-8a6f3c3e14cc
Content: Account permissions and security settings in SharePoint 2013
Content Source: SharePoint/SharePointServer/install/account-permissions-and-security-settings-in-sharepoint-2013.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: kirks

Closed as this is related to #810.