feat(client): improve handling status code types

The PR will improve the handling of TypeScript types of status codes in the Response returned by the client.
Fixes #2719
Fixes https://github.com/honojs/middleware/issues/580
Allowing number for res.status
Imagine the following application which throws the HTTPException in the handler:
import { HTTPException } from 'hono/http-exception'
import { Hono } from 'hono'

const app = new Hono()
const flag = {}

const routes = app.get('/foo', (c) => {
  if (flag) {
    throw new HTTPException(500, {
      message: 'Server Error!',
    })
  }
  return c.json({ ok: true }, 200)
})

You will create the client with the types:
import { hc } from 'hono/client'

const client = hc<typeof routes>('/')
const res = await client.foo.$get()

The current pain point is it can't infer the response having 500 status correctly.
if (res.status === 500) {
  const data = await res.json()
}

The error showing in your IDE:

It should be fixed. However, handling the response content and status with an HTTPException  or Error  object is impossible. So, I've found the solution to enable accepting number for res.status.
if (res.status === 500) { // res.status can be `number`. **No** error!
  const data = await res.json()
}

Accept generics for res.json()
That solution solves the problem of the error of res.status, but the content returned from res.json() will not be typed:
if (res.status === 500) {
  const data = await res.json() // never. not typed
}

Also to set the correct types is impossible for it. So, I'll introduce res.json() accepting generrics. You can write the following:
if (res.status === 500) {
  const data = await res.json<{ message: string }>()
}

This method does not allow automatic inference, but it avoids type errors.
Other improvements
I added some modifications since other tests failed with the changes.
The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

Hey @m-shaka @NamesMT
Can you share your opinion on this PR and review it?

Ok, I can see that later!

The idea seems good to me,
If possible, I think adding a way to define a default type for unknown/certain status codes would be greatly appreciated, I'll try to bring up some PoC later tonight when I got back home.

generic typed json looks nice!
However, number type status may cause some problems.
First, users of the client can't know which status they should handle from status type.
For example, users can understand 200 and 400 should be handled from the type of status, without reading the server code.

import { Hono } from './src/'
import { hc } from './src/client'

const app = new Hono()
    .get('foo/:id', c => {
        if (c.req.param('id') === '1') {
            return c.json({ res: 400 as const }, 400)
        }
        return c.json({ res: 200 as const }, 200)
    })

const client = hc<typeof app>('')

client.foo[':id'].$get({ param: { id: '1' }}).then(async res => {
    switch (res.status) {
        case 200:
            return await res.json()
        case 400:
            return await res.json()
    }
})

Second, projects using @typescript-eslint/switch-exhaustiveness-check will be broken. You need to add default case even if you needn't.
As @NamesMT said, a default unknown status type possibly works

I pushed a sample for the DefaultResponse support at NamesMT/hono@9248417,
I don't know if this is most optimal way though cause DefaultResponse was added to many types.
Also, now that we have a DefaultResponse type, we could potentially mark this PR's feature (default response routes) as opt-in: NamesMT/hono@2d0bfa7, this would prevent possible breaking of some projects that is currently using switch or if/else on the res.status, as well as prevent spam when user hovers on res.status.
src/_demo.ts for testing:
// server
import { HTTPException } from './http-exception'
import { Hono } from './hono'

const app = new Hono()
const flag = {}

const routes = app.get('/foo', (c) => {
  if (flag) {
    throw new HTTPException(500, {
      message: 'Server Error!',
    })
  }
  return c.json({ ok: true }, 200)
})

// client
import { hc } from './client'

type HCDefaultResponse = (
  {
    code: 'unknownErr'
    message: string
    detail: any
  } |
  {
    code: 'validationErr'
    message: string
    detail: string[][]
  }
)

const client = hc<typeof routes, HCDefaultResponse>('/') // Remove `HCDefaultResponse` to test the opt-in of default routes.

async function demo() {
  const res = await client.foo.$get()

  switch (res.status) {
    case 200:
        return await res.json().then(data => data.ok)
    default: {
      const data = await res.json() // Should be typeof `HCDefaultResponse`

      console.error(data.code === 'validationErr'
        ? { message: data.message, errorCount: data.detail.length }
        : { message: data.message })

      throw new Error(data.code)
    }
  }
}

@m-shaka @NamesMT Thank you!
As you said, we should support the default response type.
I like @NamesMT 's implementation. My proposal is to pass the default type generics into client.foo.$ge() instead of hc:
const res = await client.foo.$get<DefaultResponseInFoo>()

How about this?
It includes diff for styling, but we can implement it with the following:
diff --git a/src/client/client.ts b/src/client/client.ts
index 13641299..512e7675 100644
--- a/src/client/client.ts
+++ b/src/client/client.ts
@@ -134,17 +134,16 @@ class ClientRequestImpl {
   }
 }

-
 /**
  * @param baseUrl The base URL of the Hono instance.
  * @param options The options for the client.
  * @returns A hono API client instance.
- *
+ *
  * **Typedoc**: <Hono, DefaultResponse>
- *
+ *
  * - Hono: The type of the Hono instance.
- *
- * - DefaultResponse: This is used in cases where the response is unknown,
+ *
+ * - DefaultResponse: This is used in cases where the response is unknown,
  * e.g. checking for an unknown status code:
  * ```ts
  * // The response of status code 400 is processed by a middleware and not explicitly defined in the router type flow.
@@ -153,7 +152,7 @@ class ClientRequestImpl {
  * }
  * ```
  */
-export const hc = <H extends Hono<any, any, any>, DefaultResponse = {}>(
+export const hc = <H extends Hono<any, any, any>>(
   baseUrl: string,
   options?: ClientRequestOptions
 ) =>
@@ -229,4 +228,4 @@ export const hc = <H extends Hono<any, any, any>, DefaultResponse = {}>(
       return req.fetch(opts.args[0], args)
     }
     return req
-  }, []) as UnionToIntersection<Client<H, DefaultResponse>>
+  }, []) as UnionToIntersection<Client<H>>
diff --git a/src/client/types.ts b/src/client/types.ts
index ef54e1fe..664fb4a5 100644
--- a/src/client/types.ts
+++ b/src/client/types.ts
@@ -25,12 +25,18 @@ export type ClientRequestOptions<T = unknown> = {
       headers: T | (() => T | Promise<T>)
     })

-export type ClientRequest<S extends Schema, DefaultResponse = {}> = {
+export type ClientRequest<S extends Schema> = {
   [M in keyof S]: S[M] extends Endpoint & { input: infer R }
     ? R extends object
       ? HasRequiredKeys<R> extends true
-        ? (args: R, options?: ClientRequestOptions) => Promise<ClientResponseOfEndpoint<S[M], DefaultResponse>>
-        : (args?: R, options?: ClientRequestOptions) => Promise<ClientResponseOfEndpoint<S[M], DefaultResponse>>
+        ? <DefaultResponse = {}>(
+            args: R,
+            options?: ClientRequestOptions
+          ) => Promise<ClientResponseOfEndpoint<S[M], DefaultResponse>>
+        : <DefaultResponse = {}>(
+            args?: R,
+            options?: ClientRequestOptions
+          ) => Promise<ClientResponseOfEndpoint<S[M], DefaultResponse>>
       : never
     : never
 } & {
@@ -66,8 +72,8 @@ type ClientResponseOfEndpoint<T extends Endpoint = Endpoint, DefaultResponse = {
   ? F extends 'redirect'
     ? ClientResponse<O, S extends RedirectStatusCode ? S : never, 'redirect'>
     : Equal<DefaultResponse, {}> extends true
-      ? ClientResponse<O, S extends StatusCode ? S : never, F extends ResponseFormat ? F : never>
-      :
+    ? ClientResponse<O, S extends StatusCode ? S : never, F extends ResponseFormat ? F : never>
+    :
         | ClientResponse<O, S extends StatusCode ? S : never, F extends ResponseFormat ? F : never>
         | ClientResponse<
             DefaultResponse,
@@ -158,33 +164,27 @@ export type InferRequestOptionsType<T> = T extends (
   ? NonNullable<R>
   : never

-type PathChaining<
-  Path extends string,
-  E extends Schema,
-  DefaultResponse = {}
-> = PathToChain<Path, E, Path, DefaultResponse>
+type PathChaining<Path extends string, E extends Schema> = PathToChain<Path, E, Path>

 type PathToChain<
   Path extends string,
   E extends Schema,
-  Original extends string = Path,
-  DefaultResponse = {}
+  Original extends string = Path
 > = Path extends `/${infer P}`
-  ? PathToChain<P, E, Path, DefaultResponse>
+  ? PathToChain<P, E, Path>
   : Path extends `${infer P}/${infer R}`
-  ? { [K in P]: PathToChain<R, E, Original, DefaultResponse> }
+  ? { [K in P]: PathToChain<R, E, Original> }
   : {
       [K in Path extends '' ? 'index' : Path]: ClientRequest<
-        E extends Record<string, unknown> ? E[Original] : never,
-        DefaultResponse
+        E extends Record<string, unknown> ? E[Original] : never
       >
     }

 // eslint-disable-next-line @typescript-eslint/no-explicit-any
-export type Client<T, DefaultResponse = {}> = T extends Hono<any, infer S, any>
+export type Client<T> = T extends Hono<any, infer S, any>
   ? S extends Record<infer K, Schema>
     ? K extends string
-      ? PathChaining<K, S, DefaultResponse>
+      ? PathChaining<K, S>
       : never
     : never
   : never

This is just my opinion, but server side should accept the default response type instead of client methods like $get, because server side is supposed to know which status code it returns.
It' best that you can know which status you have to handle from the type
However, I have a feeling that adding this functionality to server side requires much more effort than adding to client 🤔
The default response type on client works like an escape hatch and resolves the pain point you mentioned first so I think it's ok atm

@m-shaka Thank you for your comment!
@NamesMT What do you think of this API? https://github.com/honojs/hono/pull/3292#issuecomment-2295778823

Hi @NamesMT
It looks good! We should consider the naming if we go with $withDR or get other names, but I like the idea (I think withDR is not bad).

Hi @yusukebe
Just wanna say that I'm super busy until October so I cannot work on this yet, holiday, trips and presenting a new project that I'm leading at work for September.

@NamesMT
Okay! Enjoy your time!


MSDKUI-1811: [Android] Route result item icon alignment

Removed extra padding from top
Signed-off-by: Vijay Yadav<EMAIL_ADDRESS>

Codecov Report

Merging #98 into master will increase coverage by 1.62%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #98      +/-   ##
============================================
+ Coverage     73.05%   74.68%   +1.62%
+ Complexity     1640      995     -645
============================================
  Files           129       69      -60
  Lines          5657     3935    -1722
  Branches        871      436     -435
============================================
- Hits           4133     2939    -1194
+ Misses          856      749     -107
+ Partials        668      247     -421

Impacted Files
Coverage Δ
Complexity Δ

...e/msdkuiapp/routing/RoutingInstructionsFragment.kt

...java/com/here/msdkuiapp/common/PermissionsUtils.kt

.../com/here/msdkuiapp/routing/OptionPanelFragment.kt

...ere/msdkuiapp/routing/RouteManeuverListFragment.kt

.../here/msdkuiapp/routing/SubOptionPanelPresenter.kt

...m/here/msdkuiapp/routing/SubOptionPanelFragment.kt

...msdkuiapp/guidance/GuidanceNextManeuverFragment.kt

...com/here/msdkuiapp/routing/OptionPanelPresenter.kt

...m/here/msdkuiapp/position/AppPositioningManager.kt

...ain/java/com/here/msdkuiapp/about/AboutActivity.kt

... and 51 more

Continue to review full report at Codecov.

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


What is __ci_base and __ci_pr?

When looking at the entrypoint.sh source, I noticed refspecs containing __ci_base and __ci_pr (https://github.com/13rac1/block-fixup-merge-action/blob/master/entrypoint.sh#L26), but I cannot find any documentation on these tags (I assume they're tags). I'm noticing issues where the git log __ci_base..__ci_pr command is returning a list of commits farther back than the base ref.

To answer my own question, these branches are created on lines 18 and 19 (https://github.com/13rac1/block-fixup-merge-action/blob/master/entrypoint.sh#L18).

Can this be closed? Seems like it. 😉

Sure, this can be closed. Though I resolved a problem that was in my fork of this project: https://github.com/samholmes/block-wip-pr-action/pull/2 Perhaps it’s relevant here as well. The problem was that if the base branch was ahead of the PRs merge base, then the depth wouldn’t be large enough to get to the merge base, and the fetch for the PR branch would go to init. If there are any fixup/squash commits in the trunk (accidental commits prior to adding the action to protect), then the action would fail.

Ah interesting, that is a problem. Oh edge cases...
Increasing the depth to 500 as you've done will (can?) result in significantly more data transfer on some repositories and therefore longer run times:
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=500 origin "${BASE_REF}:__ci_base"

This solution works, but I wonder if there's a more efficient process? 🤔

Start with a lower depth and increase it until git merge-base __ci_pr __ci_base is not a merge commit? Just idea I haven’t tried yet.
On Sun, Jul 11, 2021 at 12:51 PM Brad Erickson @.***>
wrote:

Ah interesting, that is a problem. Oh edge cases...
Increasing the depth to 500 as you've done will (can?) result in
significantly more data transfer on some repositories and therefore longer
run times:
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=500 origin "${BASE_REF}:__ci_base"
This solution works, but I wonder if there's a more efficient process? 🤔
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/13rac1/block-fixup-merge-action/issues/23#issuecomment-877851729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD6KXN2LU2HDEFAPSQTGKDTXHY27ANCNFSM475IKBEA
.


Cannot import BibliographicRecordServiceConfig following 'Change the permissions' docu

Package version (if known):
invenio-cli, version 0.22.0
Describe the bug
A clear and concise description of what the bug is.
Following the instructions given here:
https://github.com/inveniosoftware/docs-invenio-rdm/blob/e9b1bcfe0b34594a4acbdc0a2add3c19d8db52fa/docs/develop/make_it_your_own.md#modify-inveniocfg
I get the following error:
ImportError: cannot import name 'BibliographicRecordServiceConfig' from 'invenio_rdm_records.services' (/home/chriz/rz/git/invenio/icli-0-22-0/venv/lib/python3.7/site-packages/invenio_rdm_records/services/__init__.py)

Steps to Reproduce

Follow the steps here: https://inveniordm.docs.cern.ch/develop/ until you can run it (invenio-cli run).
Then follow the steps here: https://inveniordm.docs.cern.ch/develop/make_it_your_own/#modify-inveniocfg - that is:

adjusting the invenio.cfg
rerun invenio-cli run

See error

ImportError: cannot import name 'BibliographicRecordServiceConfig' from 'invenio_rdm_records.services' (/home/chriz/rz/git/invenio/icli-0-22-0/venv/lib/python3.7/site-packages/invenio_rdm_records/services/__init__.py)

Expected behavior
invenio-cli run goes through without errors and permissions are set as described.
Additional context
BibliographicRecordServiceConfig was recently renamend (and moved?). Possible fix:
from invenio_rdm_records.services import RDMRecordPermissionPolicy
from invenio_rdm_records.services.config import RDMRecordServiceConfig
from invenio_records_permissions.generators import SuperUser

class MyRecordPermissionPolicy(RDMRecordPermissionPolicy):
    can_create = [SuperUser()]

class MyBibliographicRecordServiceConfig(RDMRecordServiceConfig):
    permission_policy_cls = MyRecordPermissionPolicy

RDM_RECORDS_BIBLIOGRAPHIC_SERVICE_CONFIG = MyBibliographicRecordServiceConfig

I'm preparing a PR.

fixed by https://github.com/inveniosoftware/docs-invenio-rdm/pull/117


Change screen size for the same monitor

Microsoft PowerToys version
0.63
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
When I change screen size for the same monitor
Fancy zones change their size accordingly which is very annoying
✔ Expected Behavior
Give the option or stop automatically change fancy zones size and position when I change the screen size for the same MONITOR
❌ Actual Behavior
No response
Other Software
No response

Do you use canvas or grid layout?
/needinfo

Canvas

CANVAS @SeraphimaZykova


Only works after restarting sketch

This is probably my most used plugin, so thank you. I though I should let you know that it generally only works if I use it as soon as I open up a project, after the project has been open for a while and I've done a fair bit of editing it stops working, i.e. an error message pops up saying no objects are selected, or I run the plugin and nothing happens. It works again after restarting sketch.

Hi! It sounds like you could be using an old version of the plugin. There is a bug in Sketch 3.4.2 that trips up some plugins when the user has more than one Sketch document open (would explain why it works after restart). I uploaded a version that dodges this bug the other day. Please try updating and let me know if it helps or not. I'm all ears!


Update help_text in group forms.

Coverage remained the same at 89.492% when pulling 130c6ec61a4d2bcac5a2b1222eb0d765efca5cf3 on akatsoulas:fxa-help-text into 12e55a3a3f7b5166f440aef0978c7d4dfa6924ff on mozilla:master.


Missing gslc_ElemXProgressSetGaugeCol()

Was looking for a way to change the gauge color of a XProgress control.
I found this function in the reference gslc_ElemXProgressSetGaugeCol() but it's not present in the library (not defined in elem/Xprogress.h).

Nevermind, I just saw you added it in the HEAD, not sure why it was published in the 0.16 reference.


luci-mod-network: Expose 802.11k settings.

Tested on: 21.02.1
Signed-off-by: Paul Dee<EMAIL_ADDRESS>

Could this PR get some love, @jow- @hnyman

@hnyman @jow- Any chance we can get this PR merged? It would be very helpful :)

Does this actually work as intended?
I applied the patch to my system, and I think that it has got the default value wrong (0) for the two sub-options.
The default in the OpenWrt hostapd init script is actually 1 if 80211k is enabled.
See
https://github.com/openwrt/openwrt/blob/master/package/network/services/hostapd/files/hostapd.sh#L859-L867
	json_get_vars ieee80211k rrm_neighbor_report rrm_beacon_report
	set_default ieee80211k 0
	if [ "$ieee80211k" -eq "1" ]; then
		set_default rrm_neighbor_report 1
		set_default rrm_beacon_report 1
	else
		set_default rrm_neighbor_report 0
		set_default rrm_beacon_report 0
	fi

I enabled 80211k and then checked that both "enabled" and "disabled" for the two rrm suboptions actually enabled the two rrm suboptions.

"enabled" --> there is a config item 1 that is harmless, as the underlying default is enabled in any case

root@router1:/www# grep rrm /etc/config/wireless
        option rrm_neighbor_report '1'
        option rrm_beacon_report '1'
root@router1:/www# grep rrm /var/run/hostapd-phy0.conf
rrm_neighbor_report=1
rrm_beacon_report=1

"disabled" --> causes LuCI to remove the option from etc/config/wireless as LuCI thinks that is now reverted to default disabled and should be removed as unnecessary.

root@router1:/www# grep rrm /etc/config/wireless
root@router1:/www# grep rrm /var/run/hostapd-phy0.conf
rrm_neighbor_report=1
rrm_beacon_report=1

I think that both suboptions should have statements defining default as "enabled".

@systemcrash I know this is a little forgotten, but I hope this will be merged sometime... I think this needs a rebase, and verify what @hnyman says. Thanks!

Does this actually work as intended?
...
I think that both suboptions should have statements defining default as "enabled".

That they can be configured separately, is as intended. hostapd might do well to allow granularity for the settings.
802.11k is a standard, and for a device to be operating 'compliantly', both settings should be on. But there may exist scenarios when disabling one is desirable.
But neither of the two suboptions are active without the main k option.
Unfortunately, I do not remember the design decisions that were based on testing, as I did this a year ago. I added the default on options as suggested.

Thanks for fixing the defaults to be in line with OpenWrt behavior.

@systemcrash  @jow-
There are now quite a lot of WLAN roaming related settings. Mainly in the Advanced tab, but 802.11r related stuff in "Encryption".
I wonder if we should define a new tab "WLAN roaming" and move these 802.11r, k and v settings there.

I'm okay with that.
As long as some organization system is logical for people looking for the
settings and an expert alike.
Apple support lumps k r and v together. Their implementations are good for
client devices.


feat: filter by empty type script

resolve https://github.com/nervosnetwork/ckb-indexer/issues/47
this PR allows user to filter empty type script cells:
echo '{
    "id": 2,
    "jsonrpc": "2.0",
    "method": "get_cells",
    "params": [
        {
            "script": {
                "code_hash": "0x86a1c6987a4acbe1a887cca4c9dd2ac9fcb07405bbeda51b861b18bbf7492c4b",
                "hash_type": "type",
                "args": "0xb728659574c85e88d957bd643bb747a00f018d72"
            },
            "script_type": "lock",
            "filter": {
                "script": {
                    "code_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
                    "hash_type": "data",
                    "args": "0x"
                }
            }
        },
        "asc",
        "0x64"
    ]
}' \
| tr -d '\n' \
| curl -H 'content-type: application/json' -d @- \
http://localhost:8116

stale pr, close it


Icon size fixes

@dbatiste, @awikkerink thoughts?
This does 2 things:

Adds a variable to let the size of the icon be overridden, which subsequently just sets the iron-icon-width/height variables. This was needed in case you ever wanted to change the size of the default D2L tiers, or just create your own icon.

Fixes #73 (height being affected by line-height/font-size) by using the same alignment/display properties as iron-icon.

Looks good to me.

LGTM


Envoy possibly generating messages with invalid compression for GRPC JSON transcoding

Title: Envoy possibly generating messages with invalid compression for GRPC JSON transcoding
Description:
I'm trying to use the gRPC JSON transcoder with Envoy. This is working as intended to proxy GRPC requests, but when making requests with curl, it fails. See repro for more.
Repro steps:
First off, here is the envoy config: https://gist.github.com/banool/273a97009de2366de158e822e934b17e.
See here the logs of envoy on startup:
So when I make this request with grpcurl, it works as expected:
grpcurl -plaintext -proto crates/aptos-protos/proto/aptos/api/v2/api.proto -import-path crates/aptos-protos/proto -d '{"account_address":"0x1","module_names":["coin"],"raw":true}' <IP_ADDRESS>:51052 aptos.api.v2.ApiV2/GetAccountModules

Output: https://gist.github.com/banool/d1e56670ad7eb5b13e5f6c69ed42163d.
However when I make a request with curl, I get this:
$ curl -H "Content-Type: application/json" -d '{"account_address":"0x1","modules":["coin"],"raw":true}' -v localhost:51052/aptos.api.v2.ApiV2/GetAccountModules
*   Trying <IP_ADDRESS>:51052...
* Connected to localhost (<IP_ADDRESS>) port 51052 (#0)
> POST /aptos.api.v2.ApiV2/GetAccountModules HTTP/1.1
> Host: localhost:51052
> User-Agent: curl/7.86.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 55
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< content-type: application/grpc
< grpc-status: 13
< grpc-message: protocol%20error:%20received%20message%20with%20invalid%20compression%20flag:%20123%20(valid%20flags%20are%200%20and%201),%20while%20sending%20request
< content-length: 0
< date: Mon, 20 Mar 2023 14:47:14 GMT
< x-envoy-upstream-service-time: 1
< server: envoy
<
* Connection #0 to host localhost left intact

As you can see, the upstream server (Tonic) says that the request passed through by the proxy uses an invalid compression flag, implying that the message being formed is missing the necessary bytes at the start of the message.
Unfortunately envoy_collect.py doesn't seem to work:
$ python envoy_collect.py --envoy-binary `which envoy` --output-path /tmp/debug.tar -c ~/envoy-grpc-gateway.yaml
Traceback (most recent call last):
  File "/private/tmp/googleapis/envoy_collect.py", line 243, in <module>
    sys.exit(envoy_collect(*parser.parse_known_args(sys.argv)))
  File "/private/tmp/googleapis/envoy_collect.py", line 168, in envoy_collect
    modified_envoy_config_path, access_log_paths = modify_envoy_config(
  File "/private/tmp/googleapis/envoy_collect.py", line 82, in modify_envoy_config
    envoy_config = json.loads(f.read())
  File "/Users/dport/.pyenv/versions/3.9.13/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/Users/dport/.pyenv/versions/3.9.13/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/Users/dport/.pyenv/versions/3.9.13/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Admin and Stats Output:

Include the admin output for the following endpoints: /stats,
/clusters, /routes, /server_info. For more information, refer to the
admin endpoint documentation.

Stats: https://gist.github.com/banool/dae2e9d4f6c4e0e5435163d91027eeb2
Clusters: https://gist.github.com/banool/0cc0afbe6f57bc2600a13a0aa3195839
Routes: https://gist.github.com/banool/ea6b63bd50480b6e6adc5bbdac7ddcbb
Server_info: https://gist.github.com/banool/c2e293b759aa11339ae8757b39766774

Config:
See above.
Logs:
See above.

I don't think that Envoy does any compresion unless you explicitly configure it on?  ccing transcoder owners,  @qiwzhang @lizan

I've tried my experiment again and I'm still hitting this problem, any advice?

Also having the same problem where the first bit (compression flag) is not 0 or 1.

I'll check again soon to see if this problem still occurs with that auto_mapping flag.


[Backport 2.x] Start replication checkpointTimers on primary before segments upload to remote store. (#8221)

Start replication timer before segments upload.

Addressed comments

Description
This backports https://github.com/opensearch-project/OpenSearch/commit/32e72619251957cc3e045b29d13f4e3c190a5008 from #8221
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ankitkala @Bukhtawar @sachinpkale Suggest we please merge this as-is for consistency and open new PRs to main first with any changes.


Cannot enter tilde '~' character in terminal window anymore, w/ Belgian Keyboard

Issue Type: Bug
When trying to type tilde ('~') character in the terminal window, I get this strange behaviors:

Hitting AltGr+Tilde -> displays "="
Hitting AltGr+Tilde, Space -> displays "=~"
Hitting AltGr+Tilde, AltGr+Tilde -> displays "==~"

It is not possible to issue a single Tilde character.
(Using a Belgian Keyboard, where the tilde key is labeled "+ = ~", and is located immediately left before the right shift key.)
In other windows, the tilde works correctly.
It used to work normally in the terminal windows a few weeks ago.
Tested on at least 2 separated computers.
 Download links at the top of https://code.visualstudio.com/updates/v1_31

Same issue with that version:
Version: 1.31.1 (user setup)
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

But, the issue is not present with the version before:
Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.17134

Note for clarity:

in the title of the issue, "terminal window" meant the terminal panel of the VScode window
in the description, "other windows" meant any other panel in the VScode window (e.g. editor, search box, etc.)

As a quick hotfix, pressing down Ctrl and Alt at the same time, then the corresponding key, works as expected. For example, Ctrl+Alt+4 inputs a tilde (~) properly using my ISO Spanish keyboard while AltGr+4 does not work (inputs a 4). Version 1.33.1, not sure when it stopped working but it was recently.

I think this is a duplicate of #68262


[Question] Is it possible to add hyperlinks to logs?

In the test log, I have links to an external system, it would be nice to have the ability to render them as hyperlinks so that I don't need to copy quite a lengthy link, but I can simply click on it to open.

It works! Thanks!


Update: jsimlo.tednotepad version 6.2.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


Wanted: Slick solutions for dynamically adding operators to Observable

So right now we're kind of hacking together the core operators on Observable in the Rx.ts output file.
Ideally, people would be able to use just the operators they care about in their app, and not at all include any of the operators they don't need.
There are a ton of possible solutions for this, but I'd love to hear any and all ideas around this.

Idea: Build-Time Plugins
One option would be to create some sort of TypeScript and/or Babel plugin/addon that statically analyzed operator use, and included or excluded those operators from the output Observable build. Something like RxJS specific tree-shaking... but it's more like "operator-shaking", because it wouldn't be general.

Another idea is similar to ESLint configurations: allow people to publish a subset of RxJS operators they like most. Then include that as import Rx from 'myFavoriteRxFlavor;.

@blesh - I really like the tree-shaking idea. A consuming app could have something like rx.json, which could allow them to build out their particular rx flavor(s) however they want. It also buys shippable configurations similar to what we already know/use in RxJS such as Main Libraries, Lite Libraries, Core Libraries.

I saw something similar with lodash: https://github.com/megawac/lodash-modularize
It can detect which lodash functions you are using and then output a custom build.

There's a related discussion here: https://github.com/angular/angular/issues/4543#issuecomment-145955252
It's talking about rollup, specifically. I think that would work for the ES6 build of RxJS, but not for other usage.

@blesh I've been writing a local rx module that imports just the operators (and Subjects, Schedulers, etc.) I need in my app:
// src/rx.js
import Rx from<EMAIL_ADDRESS>// a minimal empty namespace to share
import Observable from '@reactivex/rxjs/dist/cjs/Observable';
import { of as ofStatic } from '@reactivex/rxjs/dist/cjs/observables/ArrayObservable';
import mapProto from '@reactivex/rxjs/dist/cjs/operators/map';
Observable.of = ofStatic;
Observable.prototype.map = mapProto;
export Rx;

Then in my index module, require my rx module first.
// src/index.js
import Rx from './rx';
/* import everything else */

Then in the rest of my modules, I can just import the specific type I need instead of pulling in the whole Rx namespace (alternatively, I could import the Rx.minimal namespace since I seeded it in my local rx module):
// src/foo.js
import Observable from '@reactivex/rxjs/dist/cjs/Observable';
Observable
  .of("x", "y", "z")
  .map(x => x + " says hello")
  .subscribe(message => console.log(message));


MessageImpl is out of sync with the documented behavior of Message

Describe the bug
MessageImpl is out of sync with the documented behavior
public interface Message<T> {
...
    /**
     * Get the unique message ID associated with this message.
     *
     *
The message id can be used to univocally refer to a message without having the keep
     * the entire payload in memory.
     *
     *
Only messages received from the consumer will have a message id assigned.
     *
     * @return the message id null if this message was not received by this client instance
     */
    MessageId getMessageId();

note return the message id null if ...
and then check
public class MessageImpl<T> implements Message<T> {
...
    @Override
    public MessageId getMessageId() {
        checkNotNull(messageId, "Cannot get the message id of a message that was not received");
        return messageId;
    }

note checkNotNull
Expected behavior
Actual behavior to match documented behavior (one of these has to change).

@codelipenghui could you please help confirm which behavior is correct? Thank you.

@Jennifer88huang The document is correct, @dlg99 already push out a PR #10025  to fix the code part,

@codelipenghui thank you for your confirmation.
@dlg99 thank you for fixing it.


Select List web element is not recognized correctly with IExplorer

https://developer.mozilla.org/es/docs/Web/HTML/Elemento/select
The select> element is used to create a drop-down list.
select name="select">
option value="value1">Value 1/option>
option value="value2" selected>Value 2/option>
option value="value3">Value 3/option>
/select>
Internet Explorer:
The container element of the list is recognized, but when it is open TESTAR doesn't detect the child elements.
Using the Windows inspect.exe application, I have seen that the list is created in the OS but not like a part of the web page. Instead, it is created as a new descent list from the desktop.
Chrome:
With Chrome it has a strange behavior, detects the elements of the list but they are all overlaped with each other in the parent container.
Firefox:
Works fine with Firefox

Support for multiple processes has been implemented, but it has not been merged. Probably a generic solution should be implemented.

#68 duplicate


arch: x86: Use precalculated symbol offsets

Current design:
Assembly code for each of the architectures need to know the offset of various fields in various kernel structures so that they can be properly manipulated. At the current time, these offsets are generated at build time via the GEN_OFFSET_SYM() macro--this requires a separate build step to generate those values--every time stuff gets built.
Proposed design:
The need for the offsets in assembly does not go away. However, these proposed changes are a significant step towards eliminating the need for that separate built step. It does this by doing two things for the x86 architecture:

Using a variable to identify the offset of key fields within the k_thread structure--arch and callee_saved.
Applying pre-calculated offsets instead of the offsets generated from a separate build step.

This set of commits does not yet completely eliminate the need for the GEN_OFFSET_SYM() derived macros for x86, as there are still some generic kernel ones that are still needed (for now). It is also acknowledged that there will be some minor runtime performance impacts here as extra addition and subtraction operations are required to switch the base register used in memory accesses between the base k_thread address, the _callee_saved_t  address and the _thread_arch_t address.
I would ultimately like to see this style of change done to the rest of the architectures, but I figure it is best to "test the waters" with one before investing additional time and effort with the remainder.

My impression is that we are trying to get rid of a compilation step at the cost of code readability, maintainability, size and performance. Is it worth it?
About readability and maintainability.  We have now all the offsets manually hard-coded in header files. That means not only that when we change something in a struct we have to fix all the offsets but this is generally a bad idea when you have for example nested structs (offsets of offsets of offsets ...). Also, architectures like RISCV not even have a fixed / standardized struct for the ESF for example, so all the offsets became platform and not arch dependent anymore.
@peter-mitsis is there a very fundamental reason you want to do this? I don't want to step on your toes but I feel like this should be at least discussed (again?) and agreed in the arch meeting.

@carlocaione - I appreciate the valuable feedback. The readability and maintainability are definitely potential issues with the approach. I also agree that manually pre-calculated offsets are often (with good reason) viewed with suspicion.
From what I can tell, most of the structures for which we need assembly offsets are relatively straight-forward and/or only need to be coded up once. I may have missed some cases, but a historical reading seems to suggest that those structures are quite stable. Using the past as a predictive model for the future, it seems reasonable to assume that they won't be changing often in the future. (I don't see the RISCV esf offsets as insurmountable.)
That still leaves the nested structures (such as k_thread->arch and k_thread->callee_saved) to deal with. Admittedly,  this draft came out rather ugly, which naturally leads to your other point relating to readability, maintainability, size and performance. I'm going to mark this PR as "Do Not Merge"--I've got a couple more ideas that I would like to try to explore.

I'm rather confused by this PR.
Hardcoding numeric value in the code compared to having those values
automatically computed can never be a good thing. This is prone to mistakes,
especially if some common structure is changed and then all architectures
have to be adjusted. This is true regardless how unlikely such changes may
be.
Furthermore, this PR as presented does regress code size and runtime.
Even if minuscule, this is not a tradeoff that should be made in favor of
better build time. If the build is too slow for you then get a bigger
build system or find a better way to achieve the same build result.
The build system ought to be smart enough with proper dependencies to
determine when those offsets don't have to be regenerated anyway.
So this is a -1 from me.

@npitre - The approach I've been trying of hard-coding the offsets and storing key offset values within a minimal set global variables is looking less likely to pan out ... especially as I had originally envisioned. It is not looking so bad for the architectures that use CONFIG_USE_SWITCH (such as x86/intel64), as they only need a couple of variables to store key offsets in the k_thread structure. However, those that use the old swap method (such as x86/ia32), the resulting changes have a much more significant negative impact on speed, size, and complexity.
I have explored a little along the lines of restricting such changes to those platforms that use CONFIG_USE_SWITCH, but I suspect that that is going to result in more longer term problems as that would result in two parallel build systems where some platforms could use GEN_OFFSET_SYM() and some could not. This is certainly not ideal, and is very likely a headache in the making.
Most likely, I am going to be putting this idea back into storage.

The GEN_OFFSET_SYM() concept is sane. If its implementation has issues
then that is what should be fixed. Offsets don't have to be
regenerated on every build if the source for those offsets didn't
change.


Add domain for Poznan University of Economics

website : https://poe.edu.pl

@f2xx I am sorry, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Make static-web.yml work for 2+ IPs

Currently if you try to use this ops file when you have more than 1 static IP it does not process correctly.
This edit fixes that and allows you to specify your static IPs in your params file like:
web_ip:
- <IP_ADDRESS>
- <IP_ADDRESS>

Won't this break existing deploys, which set web_ip to one IP? This should probably be a different ops file, for backwards-compatibility, with a web_ips var instead.

@eamonryan i would argue that this is something user should bring on their own (it's ok for operators to have custom ops file for their envs).

@cppforlife If this folder of ops files is intended to be useful ops files for common production patterns then why shouldn't it be provided here? In production we are almost always recommending more than 1 concourse-web server for redundancy/scale. We provide an ops file to scale the number of web servers but not a valid one that actually lets you deploy that many since it requires more than one static IP.
@vito Happy for this to be in a separate ops file if it needs to be...hadn't realised this breaks with just one

We normally just set our static IPs variable to an array in our vars file, leaving the value in the ops fold as just the variable (rather than variable inside array brackets).
It lets the operator specify the static IPs as a single IP, an array of one IP, or an array of multiple IPs.

@geofffranks Yeah, to be honest we probably should have just made the whole array settable, but the current ops file is primarily for dev/test where only one web node is the norm.
I kinda see @cppforlife's point though. If we go down to this level of detail then just about every job might have a static IPs ops file. Would that clutter be annoying?
@eamonryan I don't feel strongly tbh, so if you still want it merged in I'm game, but I would prefer a separate ops file with a web_ips (plural) var for backwards-compatibility.

@vito I think it comes down to what you want these ops files to be used for.
Ideally, I'd think we'd want users to be able to deploy not just a dev/test concourse instance, but a full fledged production instance, which is why a number of the ops files were committed by you with the comment: "extract all our prod use cases as ops files".
To that end, should there not be a combination of ops files that gets you everything you need to lay out a production grade Concourse deployment? That way we can have documentation that just says "Use this deploy command with these N ops files" instead of having users write custom ops files for extremely common use cases, or having a bunch of custom-ish vars-file stuff.
On the clutter comment - doesn't only the web server need a static IP anyway? I don't see it extending to other jobs really. Or if it's not strictly required and you'd have a LB in front of a multiple-web configuration anyways maybe there's room to explore more here before making a decision.
Separate ops file is alright, though it sounds like we need maybe some comments inside that describe that "this one is for when you have multiple web servers".

@eamonryan Personally, I think there's a very quick drop the value of ops files (or any form of templating) as there are more and more sitting around, and that things can very quickly get out of hand if the people maintaining them drink a bit too much kool-aid and provide an ops file for every little thing. Similar to how Spiff and other templating tools just masked complexity in the releases they were used for, making it impossible for anyone to just write a manifest by hand and understand what it's doing.
I think as maintainers of these ops files we should be careful not to bring in too many things that are only ever used by individual operators, as these operators shouldn't be relying on this repository as their 100% single source-of-truth. The Concourse release is intentionally kept simple enough that you shouldn't even really need a full blown templating toolchain in the first place.
So I'm going to close this (sorry). We may have been hyprocritical in the past when we extracted stuff from our prod deployment. But we had to start somewhere, and our deployment seemed fairly realistic. We'll keep an eye out for things like this in the future.


Easily create Litellm modelfiles via the web UI and not only Ollama

Is your feature request related to a problem? Please describe.
When I try to create a model file with a model that is store not on the ollama server but on the litellm server in my openwebui configuartion files, the oepn webui interface try to download it "pull model manifest: Get "https://ollama.com/token?nonce=PVU8K_tursrhgMstjAboFw&scope=repository%3Alibrary%2Fmixtral-8x7b%3Apull&service=ollama.com&ts=1714223332": EOF"
i do confirm the litellm model is accessible through the open webui
in my case I am using litellm > vllm > mixtral 8x7b
Describe the solution you'd like
It should be possible to create a model file for a model accessible through the litellm server.

Duplicate #665


Bug Report: In-Place Operation Causes Gradient Error in conv1d_step Function

Bug Report: In-Place Operation Causes Gradient Error in conv1d_step Function
Issue Description:
While training the model, I encountered a runtime error related to gradient computation caused by an in-place operation in the conv1d_step function. The error message pointed out that one of the variables needed for gradient computation was modified in-place, which broke the backpropagation process.
Here is the detailed error message:
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [6, 4, 512]], which is output 0 of torch::autograd::CopySlices, is at version 38; expected version 36 instead.

Upon investigation, I found that the issue stems from two in-place operations within the conv1d_step function, specifically in the following lines:
conv_state.copy_(torch.roll(conv_state, shifts=-1, dims=1))  # In-place modification
conv_state[:, -1:, :] = x  # In-place modification

These in-place operations cause the gradient computation to fail in certain scenarios, especially when torch.autograd.set_detect_anomaly(True) is enabled for debugging.

Steps to Reproduce:

Implement the conv1d_step function with the original code.
Enable anomaly detection in PyTorch using torch.autograd.set_detect_anomaly(True).
Run the training process and observe the runtime error during backpropagation.

Proposed Fix:
The issue can be resolved by avoiding in-place modifications to the conv_state. Below is the modified version of the conv1d_step function, which eliminates the in-place operations and instead uses non-in-place operations for state updates.
def conv1d_step(
    x: torch.Tensor,
    conv_state: torch.Tensor,
    conv1d_weight: torch.Tensor,
    conv1d_bias: torch.Tensor = None,
) -> tuple[torch.Tensor, torch.Tensor]:
    """
    B: batch size
    S: sequence length
    D: feature dimension
    KS: kernel size
    Args:
        x (torch.Tensor): (B, S, D)
        conv_state (torch.Tensor): (B, KS, D)
        conv1d_weight (torch.Tensor): (KS, D)
    """
    assert (
        x.shape[0] == conv_state.shape[0]
    ), f"x has batch size {x.shape[0]} but conv_state has batch size {conv_state.shape[0]}"
    assert (
        x.shape[2] == conv_state.shape[2]
    ), f"x has feature dimension {x.shape[2]} but conv_state has feature dimension {conv_state.shape[2]}"
    assert x.shape[1] == 1, f"x has sequence length {x.shape[1]} but it should be 1"

    # Use non-in-place operation for rolling the state
    conv_state = torch.roll(conv_state, shifts=-1, dims=1)
    conv_state[:, -1:, :] = x  # This is now safe as conv_state is newly assigned

    y = torch.sum(conv_state * conv1d_weight, dim=1, keepdim=True)

    if conv1d_bias is not None:
        y += conv1d_bias

    return y, conv_state

This solution replaces the in-place copy_() operation with a non-in-place torch.roll(), which ensures that the gradient computation is not interrupted.

Environment Details:

PyTorch Version: [2.2.2]
CUDA Version: [12.2 for os cuda；12.1 for torch cuda]
Python Version: [3.12.3]
Operating System: Ubuntu 20.04]

Please let me know if any further details or testing are required!

Additional Context:
This error was encountered while training an xLSTM model for pedestrian trajectory prediction. The training process failed during the backward pass due to in-place operations within the convolutional component of the xLSTM block.

same problem and same solution, great to see someone reported already


Training on Telugu-english corpus

Hey,
I wanted to train the model on a corpus of my own.It would be great if you could walk me through the procedure.I have a lot of telugu text in latin script i.e (english script).I was wondering how to generate the bpe encodings and the vocab files for this particular language and how to use them.It would be of great help if you could guide me
Thanks.

The process is described here
If you already have your text prepared then you need to start from concat.sh. Then proceed with createspmodel.sh to create three files with dictionary and model hyperparameters, copy them to /models/<modelname>. After that use encode.sh <concatenated.txt> <modelname> <encoded.npz>, you should get that <encoded.npz> file in the model directory. Then all you need is to run PYTHONPATH=src train.py with parameters set accordingly, you'll need --dataset, --mode_name, --learning_rate at least but some others may also be of use. For example, my run line was PYTHONPATH=src ./train.py --dataset models/Books50k_2/clean.npz --model_name=Books50k_2 --sample_every 1000 --save_every 300 --learning_rate 2.5e-4 --average_steps 1000 --run_name run3. You can monitor the learning progress with tensorboard.
(it should be obvious but still, use actual filenames and model name instead of those <...>, they're just an example)
Sorry for long answer, it seems I was not watching my own repository and was not notified of new issues.

Hello,
I tried this, but I am not sure if hparams.json is correct. I followed your instructions and get a file:
{
  "n_vocab": 1024,
  "n_ctx": 1024,
  "n_embd": 768,
  "n_head": 12,
  "n_layer": 12
}

The example models have n_vocab = 50257 and 1024 looks like this parameter should only belong into n_ctx, but not to n_vocab. I am not sure about the implications, but I guess n_vocab should be the number of different words in the input text, shouldn't it?

n_ctx is the context window size, it defines how many tokens the model takes as input to predict the next token (from what I understood), n_vocab is indeed the dictionary size. The model creation script will create that hparams.json file for you according to the dictionary size you specify. Read issues #3 and #4 for details.


Service down?

I'm getting 500 errors willy-nilly from the service.

PS: Also getting timeouts from the dependency endpoint.
Anything, that I can help out figure/resolve this issue?

Update: It's working now, But i'm quite certain the willy-nilly behaviour will show back up again. If there's a stack trace, I may have cycles to help out.

Seems to be down right now.

It is intermientent. Sometime it works sometime it isn't :(

Duplicate #195

Not Again???


add Ford Adapter

RE-CHECK!

Automated adapter checker
ioBroker.ford

[ ] :heavy_exclamation_mark: [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: npm owner add bluefox iobroker.ford
[ ] :eyes: [W400] Cannot find "ford" in latest repository

ioBroker.nissan

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "nissan" in latest repository

ioBroker.wmswebcontrol

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "wmswebcontrol" in latest repository

Add comment "RE-CHECK!" to start check anew

Hi,
Review Feedback:

Please update testing lib, else all your tests will fail
Please set connecion state to false in unload :-)
really setting timeout only new in https://github.com/TA2k/ioBroker.ford/blob/master/main.js#L378 ? What about deleting an existing one first?

Only last needs to be checked and pot fixed, rest optional

Issues fixed

RE-CHECK!

Automated adapter checker
ioBroker.wmswebcontrol

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "wmswebcontrol" in latest repository

ioBroker.nissan

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "nissan" in latest repository

ioBroker.ford

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "ford" in latest repository

Add comment "RE-CHECK!" to start check anew

Thank you, please poke again when new verison is released on npm

Done

Hm why there are 3 adapters in this PR? Are Nissan and waren’s also published after issues addressed in PR were fixed, then I would just merge this one @TA2k

No only 1 adapter in this PR see also file changed but the branch was created after commiting the other this leads to this wrongly added checks.
This can be ignored


Issue 2 credits to New Media Gallery

Issue 2 credits to @NewMediaGallery

 Follow up
On Tuesday, 03-Dec-24 18:17:01 UTC by Gov4Git dev
Could not issue 2 credits to member @newmediagallery. Reopen the issue to retry.
Because: file does not exist


Vickel: Watch PLUSG7DHW

Vickel requests the watch of the watch_keyword PLUSG7DHW. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

PLUSG7DHW has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Remove empty [b]Example:[/b] lines from the class reference

This is part of a personal gripe that is relatively simple to address in one sweep.
To make it brief, here's a snippet of something I've been steadily writing to explain my writing style for the class reference:

DO NOT introduce a codeblock example with [b]Example:[/b] and no further explanation. If there's no need for an additional statement, don't write it. Preferably make the example understandable on its own (without comments!). Every new line is important!

To reiterate, there's no point in preceding a codeblock with "Example:" if there's nothing to say. What else could it be there for?
For the built-in class reference, this does not even look good in practice, as these do not use h1 or similar tags.
A good chunk of these came from https://github.com/godotengine/godot/pull/68120 f7c611ab71d292d64a6d4db8db8e36aaf0e2330b.
For the descriptions affected, additional tweaks have been made to justify a whole translation string change.

I found a few more with Examples: instead. I decided to keep some of these as it feels like their introduction is necessary, although the actual codeblock examples they introduce should really be improved upon, so that they can be removed.

For the record, I prefer not to cherry-pick such changes for stable releases, as it breaks translations. We should only break translations if the docs are wrong (bugfix), not for cosmetic changes.

There's many "unspoken" rules that are entirely missing in there. There's so many that the Class reference primer may not be a good place to document them all, as the page mostly serves to describe how the XML and BBCode formatting works.
I did say, I am trying to keep track of my own writing style guide. Maybe someday they can all be polished up and made into one big, less subjective style guide.

Thanks!

Oh dang, I had found a few more. Oops! I'll do it next time.


Output logs even in the case of success

Currently I'm running MSTest through Azure Pipelines using a VSTest@3 task. I observe that the test output is only done in the case of a failure, but omitted completely in the case of a success. Is there a way to output the logs for a successful tests too?
And is there a way to get the live output of a test instead of only at the end?

Is there a way to output the logs for a successful tests too?

Yes, dotnet test --logger:"console;verbosity=detailed".
 dotnet test --logger:"console;verbosity=detailed" -tl:false
  Determining projects to restore...
  All projects are up-to-date for restore.
C:\Program Files\dotnet\sdk\9.0.100-preview.2.24127.10\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierIn
ference.targets(314,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support
-policy [S:\t\mstest115\mstest115.csproj]
  mstest115 -> S:\t\mstest115\bin\Debug\net9.0\mstest115.dll
  Passed TestMethod1 [3s 2ms]
  Outputs:
    Standard Output Messages:
   Hello,
   World

  Passed! - Failed: 0, Passed: 1, Skipped: 0, Total: 1, Duration: [3s 453ms]

And is there a way to get the live output of a test instead of only at the end?

Not yet, there is this env variable: VSTEST_EXPERIMENTAL_FORWARD_OUTPUT_FEATURE=1 which will forward the output from the process, but it depends on the test framework whether or not the output will reach console. In MSTest at least there is no way to suppress capturing the managed (via Console.Write or Console.WriteLine), so only native output would reach that forwarding.
The ability to disable capturing output was added MSTest and will be released in 3.4.0  https://github.com/microsoft/testfx/issues/349


What is the correct way to validate() a schema containing an AutoValue key?

Every time I validate(), it throws an error because the AutoValue key doesn't exist (because the client doesn't run AutoValue functions I'm guessing). Is the correct way to deal with this to add an optional: true flag?
Relevant closed issue: https://github.com/aldeed/meteor-autoform/issues/1218

Hey Bandit,
Can you show us your simpl-schema ?

Here's an example schema showing my current approach to this problem
Items.schema = new SimpleSchema({
  _id: {
    type: String,
    label: 'The ID of this item',
    optional: true,
    custom() {
      // only required on an update
      if (!this.isSet && this.operator === '$set') return 'required';
    },
  },
  owner: {
    type: String,
    label: 'The ID of the account this item belongs to',
    optional: true,
    custom() {
      // only required on an insert
      if (!this.isSet && !this.operator) return 'required';
    },
  },
  createdAt: {
    type: String,
    label: 'The date this item was created',
    optional: true,
    autoValue() {
      if (this.isInsert) return (new Date()).toISOString();
    },
  },
  updatedAt: {
    type: String,
    label: 'The date this item was last updated',
    optional: true,
    autoValue() {
      if (this.isInsert || this.isUpdate) return (new Date()).toISOString();
    },
  },
  [...]
});

try running ss.clean frist then ss.validate.
Items.schema.clean(item);
Items.schema.validate(item);


[RFC] boards: msp432p401r: Add GPIO Support

Adds GPIO Support for the TI MSP432P4012R MCU
Signed-off-by: Dhruva Gole<EMAIL_ADDRESS>

This PR Doesn't build properly yet, need help on what changes need to be added exactly for adding gpio support to this board other than the gpio node in dts.


Refactored release logic to use liquibase-sdk

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Updates the logic used for creating release artifacts to:

Pull current versions of external components at "create artifact time" vs. expecting the .tar.gz to be correct
Use logic that was moved to liquibase-sdk for building final files

Fixes DAT-11427
Things to be aware of

Only needs to impact release logic
Prepares us to change the upstream build logic in a separate PR

Things to worry about

We can see the final artifacts in a test draft release and manually check them, but the real publish of them isn't tested until release day

For reviewing this PR, I ended up writing proposed changes vs. describing them. You can see them at https://github.com/liquibase/liquibase/pull/3308/commits/5810f8b42bdb4569a235d69d2dcce3c7f0e7261a and I see it as a discussion point more than "how it has to be".
Changes:

Use liquibase-sdk:download-snapshot-artifacts vs. action-download-artifact
Removed some lines that seemed unneeded now
Separated the "save the results" from "build intallers" partly because of the attempted re-use of create-release-artifact which can't run on mac and partly to prepare for other steps later like "make RPMs" etc.
Some wording/naming changes
Added liquibase-sdk to the base pom.xml file

I ran the action to see what works and doesn't. It failed now because the create-release-artifact call I do in the "finish" line to sign the new filese and  build the liquibase-additional.zip fails due to not finding any snapshot files to reversion.
That is easily fixed, but I didn't want to bother with that if we ended up wanting to do things completely differently than I have here.

This PR was left open originally to facilitate discussion with Nathan about the use of sdk. However it is deprecated now since   we will use Github Packages as a way to share build artifacts with downstream builds.

I think all the logic we have in here for improving how the release process works is just as valid even if we're getting snapshot builds from github packages vs. off the builds?
So not sure it should just be closed for that reason?


Change node-sass to sass

sass is now the recommended SaSS implementation and it is well supported by sass-loader.

Closing in favor of #10013


Deleting objects with bindings?

What binding does your question apply to, if any? (e.g. Blob Trigger, Event Hub Binding, etc)
Basically all of them
Question
How can I delete objects in a blob storage or from a Cosmos DB with bindings?

Thanks for informing.
you can refer this document to delete method.
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-delete#delete-a-blob


Cluster Mesh K3S / RKE2

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
A bug happened!
i have two cluster, one in  k3S, other in RKE2. each installed with cilium latest version and four node
the step to activate clustermesh are well passed but with K3S i have svclb who give me 4 adresses
when i try to connect cluster mesh, seems ok on rke2 side, but not on k3S side.
Cilium Version
1.15.4
on k3S side
#!/bin/bash

CILIUM_VERSION="1.15.4"
helm repo add cilium https://helm.cilium.io/
helm upgrade --install cilium cilium/cilium --version=${CILIUM_VERSION} \
    --namespace kube-system \
    --set kubeProxyReplacement="true" \
    --set bpf.masquerade="true" \
    --set ingressController.enabled=false \
    --set ingressController.default=false \
    --set hubble.relay.enabled=true \
    --set hubble.ui.enabled=true \
    --set cluster.name="k3s" \
    --set cluster.id=1 \
    --set cni.chainingMode="none" \
    --set hubble.metrics.enableOpenMetrics=true \
    --set hubble.metrics.enabled="{dns,drop,tcp,flow,port-distribution,icmp,httpV2:exemplars=true;labelsContext=source_ip\,source_namespace\,source_workload\,destination_ip\,destination_namespace\,destination_workload\,traffic_direction}" \
    --set encryption.enabled=true \
    --set encryption.type=wireguard

on rke2 side
#!/bin/bash

CILIUM_VERSION="1.15.4"
helm repo add cilium https://helm.cilium.io/
helm upgrade --install cilium cilium/cilium --version=${CILIUM_VERSION} \
    --namespace kube-system \
    --create-namespace \
    --set kubeProxyReplacement="true" \
    --set bpf.masquerade="true" \
    --set k8sServiceHost="<IP_ADDRESS>" \
    --set k8sServicePort="6443" \
    --set ingressController.enabled=false \
    --set ingressController.default=false \
    --set hubble.relay.enabled=true \
    --set hubble.ui.enabled=true \
    --set hubble.ui.ingress.enabled=true \
    --set cluster.name="rke2" \
    --set cluster.id=2 \
    --set hubble.metrics.enableOpenMetrics=true \
    --set hubble.metrics.enabled="{dns,drop,tcp,flow,port-distribution,icmp,httpV2:exemplars=true;labelsContext=source_ip\,source_namespace\,source_workload\,destination_ip\,destination_namespace\,destination_workload\,traffic_direction}" \
    --set encryption.enabled=true \
    --set encryption.type=wireguard

Kernel Version
rke2
Ubuntu 22.04.4 LTS   5.15.0-102-generic
k3s
Debian GNU/Linux 12 (bookworm)   6.6.20+rpt-rpi-2712
Kubernetes Version
1.27 k3S
1.29 RKE2
Regression
No response
Sysdump
to big :/
Relevant log output
➜  rke2 git:(main) ✗ cilium clustermesh status --context $CLUSTER2 -n kube-system --wait
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
✅ Cluster access information is available:
  - <IP_ADDRESS>:2379
✅ Deployment clustermesh-apiserver is ready
✅ All 4 nodes are connected to all clusters [min:1 / avg:1.0 / max:1]
🔌 Cluster Connections:
  - k3s: 4/4 configured, 4/4 connected
🔀 Global services: [ min:1 / avg:1.0 / max:1 ]

K3S side
✅ Service "clustermesh-apiserver" of type "LoadBalancer" found
✅ Cluster access information is available:
  - <IP_ADDRESS>:2379
  - <IP_ADDRESS>:2379
  - <IP_ADDRESS>:2379
  - <IP_ADDRESS>:2379
✅ Deployment clustermesh-apiserver is ready
⌛ Waiting (1s) for clusters to be connected: 4 nodes are not ready
⌛ Waiting (12s) for clusters to be connected: 4 nodes are not ready

Anything else?

Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

Hi @didlawowo,
Could you verify whether you can curl <IP_ADDRESS>:2379 from the RKE nodes?
Could you please also share a sysdump of the two clusters?

i have review the configuration
now i'm using cilium L2 with k3S cluster instead off servicelb
i can finish the setup of cluster mesh, but i'm make the connect, i have lost the dns, all control plane where down

Hmm, that's weird. A few questions to try to troubleshoot the issue:

Are you able to capture a sysdump of both clusters? i can, but to big to post here
Did the issue occur only after meshing the two clusters? after connecting the mesh, enabling is OK
Are the clusters configured with non-overlapping node/pod IPs? i the same network overlapping is not possible
Are you using Cilium to handle the LoadBalancer services? i did loadbalancer with cilium and metal lb
Is there any other service associated with the same IP? i don't think so
Does the DNS issue resolve if you manually edit the Cilium daemonset and remove the HostAlias section? i can't try it.

i have to rebuild the both cluster after this problem. so i can't go further because it's take a lot of time. and for me using the same network for thoses cluster i can now use gateway api to route traffic from on cluster to another
i'm thinking cluster mesh with k3s and rke2 need some particular configuration which i don't have. as i say before when i have servicelb, mesh not working, i have to move to only one load balancer (disable klipper) to have connection, maybe some test and more documentation could help

OK, I'm then closing this issue as it doesn't really contain enough information to reproduce and troubleshoot the underlying issue. Please feel free to reopen it if you encounter the same problem again.


Vendor swarmkit for 1.12.3

This updates swarmkit to include a few important bug fixes, including
some fixes for regressions.

LGTM

LGTM

@aaronlehmann can you list the fixes?

LGTM

@justincormack @aaronlehmann at least https://github.com/docker/docker/issues/27469 I believe

Fixes are as follows:

docker/swarmkit#1305: orchestrator: Avoid restarting a task that has already been restarted
-docker/swarmkit#1632: controlapi: Allow duplicate published ports when they use different protocols
docker/swarmkit#1657: controlapi: Allow multiple randomly assigned published ports on service
docker/swarmkit#1651: allocator: Fix panic when allocations happen at init time
docker/swarmkit#1661: Add an allocator test for preinit task object (technically not vendored as this is only a unit test change)

I won't close the corresponding issues in this repo until the fixes are vendored in master.

LGTM


Filter list of available authorized dashboards

This commit filters the dashboard list so that the navigation will not show Dashboards the user is not authorized to see (via the authorize() method on the dashboards. This allows for different sets of dashboard depending on authorization policies.

Damn, I thought i got them all. Thanks!


Make the sample program a bit more interesting

In particular, print out something when you run the binary installed so you know it does something.
Right now it just returns which isn't very fun.

maybe this will help https://github.com/ZOSOpenTools/zotsampleport/pull/8


Adding Download Feature : Qr Code Generator

Is your feature request related to a problem? Please describe.
I have seen various QR Code Generators with download options. But In Qr Code Project, There is no download option available, I would like to add an option of downloading the QR code as jpg or png. Hence, These QR Images will help users to share their QR Codes for scanning and networking purposes.
Describe the solution you'd like
When the QR Code will be generated, I want to use functions for the generation of images for QR Codes. I want to fetch image data from the API and then want to save it as a jpg or png.
Additional context
Instead of giving user download options. we can give users a sharing option where the user can share their QR code to Gmail, save it to Drive, save QR as Pdf, etc.

Hello @Risht11  I can work on this project  . Can you please assign me this issue...
Please assign this to me under @SSOC23


gnu(5440)=13405

gnu(5440)=13405
GAP      4.8.3
GrpConst 2.5
Runtime: 9856665 ms (2.74 hrs)
Isomorphic groups eliminated
In case this value is new, add the next line to data/gnudata.g
GNU_SAVE( 5440, 13405, WITH_GC );

gap>
System : Windows Vista

Thank you for submitting new gnu(n). We will recalculate it and add to the database if we get the same result.
Checklist for the reviewer:

[ ] checked and assigned labels "new (n<50000)" or "recomputation", if needed
[ ] set "replication needed" label (unless it starts immediately)
[ ] changed it to "replication in progress" label when the replication has been started
[ ] changed it to "replicated" after successful replication review
[ ] reproducible value of gnu(n)
[ ] no essential runtime differences
[ ] sufficient level of technical details

Checklist for the maintainer:

[ ] correct arguments of command to store data
[ ] correct location of new line in the data file
[ ] mention submitter and reviewer in the commit message
[ ] Close corresponding issue from the commit message

gnu(5440)=13405
GAP      4.8.3
GrpConst 2.5
Runtime: 5991769 ms (1.66 hrs)
Isomorphic groups eliminated
Replicated by @alex-konovalov on Ubuntu 16.04 on Azure cloud standard DS13 v2 instance (8 cores, 56 GB memory)
To maintainers: for new results, add to data/gnudata.g this line:
GNU_SAVE( 5440, 13405, WITH_GC );


Broken hyperlink

Broken link for requirement of Network share coverage and exclusions (preview)
Microsoft Defender April-2023 (Platform: 4.18.2304.8 | Engine: 1.1.20300.3)

Broken link: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-updates.md#april-2023-platform-41823048--engine-11203003

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

ID: 34f25ec8-d5a8-4a9d-ca72-bd61eacd9dbc
Version Independent ID: 34f25ec8-d5a8-4a9d-ca72-bd61eacd9dbc
Content: Configure endpoint DLP settings - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/dlp-configure-endpoint-settings.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@AndNovian Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12040
Once the author approves, the changes will be live.
Thanks
Sri


New updating algorithm without token - forward data updating on change instead of backward on request

Now, all data updates happen on change instead of on request which means, data updates are now always being forward updated, never backward.
Consequences:

self.exec_output(index) can now be called without having to worry about the token - there are no tokens anymore
potential updating problem with tokens caused by data reference from inside a loop to outside now not possible anymore - no tokens anymore
execution flows run slower now, partly significantly but that depends on the way they are programmed
data flows can run very fast now
also, a few names were changed ('update_event' instead of 'updating' for example)
and variables are now handled by a special handler, not the script itself anymore

it overall makes more sense to update this way.

All packages are updated and the examples project is adapted too. Should be working now as much as before with tokens.

update: since release v2.0 Ryven includes a feature that lets you choose between forward propagation on change of data or backward updating on request, both possible now which is pretty dope.


⚠ ClamAV has degraded performance

In d6f9858, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 223 ms

Resolved: ClamAV performance has improved in 8877866.


v0.8.4_09: Small pop up screen is disturbed

SEVERITY: Minor
MODULE:  Mountain Chart
Platform: iPhone-5 (iOS 7.1)
RELEASE: v0.8.4
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.4/preview/barchart.html
Bar chart page will be loaded
Click x axis description
Note that small pop up screen is disturbed

ACTUAL RESULTS:
Small pop up screen is disturbed by clicking X axis description
EXPECTED RESULTS:
Small pop up screen should not be disturbed by clicking X axis description
SCREENSHOT:

https://github.com/Gapminder/vizabi/pull/757

@k6Labz please retest on develop

Retest Result: Pass
Testing Environment - DEVELOP: http://dev-tools.gapminderdev.org:3001/


[FLOC-3009] Only use virtual disk serial number if the virtio_blk driver is detected

A release maintenance branch for #1921 which has already been reviewed and approved.

:+1: YOLO

The rackspace/ubuntu acceptance test failures revealed a problem with our _is_virtio_blk function.
root@acceptance-test-richardw-0:~# ls -l /sys/bus/virtio/drivers/virtio_blk
total 0
--w------- 1 root root 4096 Sep 14 10:05 bind
--w------- 1 root root 4096 Sep 14 10:05 uevent
--w------- 1 root root 4096 Sep 14 10:05 unbind

We need to find another way to detect that the guest uses virtio_blk.

I merged forward to pick up @jongiddy 's zfs fix (#1929) and to trigger a new build.
Let's see if it goes green this time.

I will go with your testing on Devstack. And it works for Rackspace acceptance tests, so go ahead and merge into 1.3.0 branch.
None of my comments are critical for making the system work. They are cleanups (DRY, clear names and comments) so I recommend merging this branch, and addressing the comments in the branch to be merged into master.


Build Options for Older CPU w/o AVX

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
source
TensorFlow version:
tensorflow-1.12.0rc0
Python version:
3.6
Installed using virtualenv? pip? conda?:
conda
Bazel version (if compiling from source):
0.17.2
GCC/Compiler version (if compiling from source):
gcc version 5.4.0
CUDA/cuDNN version:
no
GPU model and memory:
no

Describe the problem
I need to turn off AVX during build. However, the tf_configure.bazelrc doesn't have an explicit AVX flag. Since the build takes hours to complete, could you tell me what the flag is? Here is my tf_configure.bazelrc:
import %workspace%/tools/bazel.rc
build --action_env PYTHON_BIN_PATH="/home/me/anaconda3/bin/python"
build --action_env PYTHON_LIB_PATH="/home/me/anaconda3/lib/python3.6/site-packages"
build --python_path="/home/me/anaconda3/bin/python"
build:xla --define with_xla_support=true
build --action_env TF_NEED_OPENCL_SYCL="0"
build --action_env TF_NEED_ROCM="0"
build --action_env TF_NEED_CUDA="0"
build --action_env TF_DOWNLOAD_CLANG="0"
build:opt --copt=-march=native
build:opt --copt=-Wno-sign-compare
build:opt --host_copt=-march=native
build:opt --define with_default_optimizations=true
build:v2 --define=tf_api_version=2
Provide the exact sequence of commands / steps that you executed before running into the problem
2018-11-23 16:35:33.993987: F tensorflow/core/platform/cpu_feature_guard.cc:37] The TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine.
Aborted (core dumped)

What’s your bazel build command?

bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package
After ./configure, as in https://www.tensorflow.org/install/source

./configure
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]: -march=core2
Or change "core2" to the μarch which you are using.

What are the permitted "uarch" names?
I am building now  by sticking -mno-avx somewhere. It has been building
for a couple of hours.....
On Fri, Nov 23, 2018 at 9:37 PM Iamanorange<EMAIL_ADDRESS>wrote:

./configure
Please specify optimization flags to use during compilation when bazel
option "--config=opt" is specified [Default is -march=native]:
-march=core2
Or change "core2" to the μarch which you are using.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/23943#issuecomment-441345193,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX3ZAqJ8onghxQHESpBFNG7UEGdIZswOks5uyNsjgaJpZM4YxNk5
.

https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html

The proper way to find native μarch is
gcc -Q -march=native --help=target | grep march

Thanks. I specified -march=sandybridge but still get the same message:
2018-11-24 22:13:30.127860: F
tensorflow/core/platform/cpu_feature_guard.cc:37] The TensorFlow library
was compiled to use AVX instructions, but these aren't available on your
machine.
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
On Fri, Nov 23, 2018 at 11:21 PM Iamanorange<EMAIL_ADDRESS>wrote:

The proper way to find native μarch is
gcc -Q -march=native --help=target | grep march
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/23943#issuecomment-441349093,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX3ZAmESzkSZ4pSTBDJibcIC29di4G4Gks5uyPNcgaJpZM4YxNk5
.

Oh, I found out my architecture is sandybridge,using the command above. The
error message, however, says I don't have AVX. Is there a simple way of
turning off avx, regardless if the CPU supports it or not? I tried adding
-mno-avx in the configuration file, but it doesn't seem to have an effect,
still getting the same message.
On Sat, Nov 24, 2018 at 11:24 PM Iamanorange<EMAIL_ADDRESS>wrote:

Why did you build with -march=sandybridge? Sandybridge is the first
generation which support AVX.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/23943#issuecomment-441420918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX3ZAnRJ9YOK9ERzqpX3UcdiD99-8ybnks5uykWigaJpZM4YxNk5
.

Try -march=core2.

Just tried, still no luck. The message is the same.
On Sun, Nov 25, 2018 at 8:45 AM Iamanorange<EMAIL_ADDRESS>wrote:

Try -march=core2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/23943#issuecomment-441454007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX3ZApW5ha9tbtuJhOZlUPML-e0q6OjQks5uysksgaJpZM4YxNk5
.

Did you ‘bazel clean’ between your trials?

Just chipping in here that I have the exact same problem also relating to the use of Linux-Fake-Background-Webcam on an HP Pavilion 14-ce3510sa


@payloadcms/live-preview has multiple issues

Link to reproduction
No response
Describe the Bug
The library itself uses a function from Payload here and uses Payload as peerDependency. This may work great when you're using Next and Payload together in the same project, but in docs says No matter what front-end framework you are using, you can build your own hook using the same underlying tooling that Payload provides..
Issue 1: the library installs payload + its dependencies => a lot of dependencies for a simple library
Issue 2: Using yarn/pnpm can cause errors (see To Reproduce)
To Reproduce
Create an Angular application and try to add @payloadcms/live-preview.  You will receive errors like:
Error: node_modules/.pnpm/payload@2.1.1_typescript@5.2.2_webpack@5.89.0/node_modules/payload/dist/config/types.d.ts:2:58 - error TS7016: Could not find a declaration file for module 'express-fileupload'<EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/express-fileupload` if it exists or add a new declaration (.d.ts) file containing `declare module 'express-fileupload';`

2 import type { Options as ExpressFileUploadOptions } from 'express-fileupload';

Payload Version

Adapters and Plugins
No response

A solution would be to build and bundle with used functions from payload. This will break the dependency with payload.

traverseFields has depth argument that can be number | undefined, but passes to promise where should be number.

traverseFields should decrease the depth for each recursive call.

removing an item from relationship with hasMany doesn't sent MessageEvent

Thank you for reporting on this @GeorgeHulpoi and you're right, payload is only needed as a dev dependency because we're simply importing types from there. No js needs to be bundled. Same is true for the React package. I just opened #4308 to take care of these issues.

traverseFields has depth argument that can be number | undefined, but passes to promise where should be number.

I do see this issue, but wondering why ts is not catching it on my end. Is it throwing an error in your project? I will look into this.

removing an item from relationship with hasMany doesn't sent MessageEvent

This has likely been fixed with some of the recent updates, many of which have yet to go out. Just to be sure, are you on the latest versions of live preview and payload?

traverseFields has depth argument that can be number | undefined, but passes to promise where should be number.

Quick follow-up here, in #4315 the depth argument no longer drilled through traverseFields, and promise is being deprecated altogether in favor of batching the API requests.


Use CB as backend

Merge after https://github.com/openvinotoolkit/openvino.genai/pull/604

Included in https://github.com/openvinotoolkit/openvino.genai/pull/644

Included in https://github.com/openvinotoolkit/openvino.genai/pull/644


Thank you for your work!

Hello @itamarst and other contributors, normally you see issues here, but I wanted to praise and give you credit for the work you have done:
I built a pipeline using pyahocorasick automata as part of a fairly sophisticated ML pipeline https://github.com/applied-knowledge-systems/the-pattern , see pipeline 1. (which won https://redis.com/blog/build-on-redis-hackathon-winners/), and I was thinking of moving pipeline to Rust (even had a very nice email exchange with Andrew @burntSushi). However, I need HTTP fetch, and new RedisGears version 2  (using wasm runtime still doesn't have HTTP fetch), so I still rely on Python for the server-side pipeline.
Your work allows me to build a transition from Python pyahocorasick to Rust based Aho-Corasick.
Thank you.

Thank you!


opentelemetry-collector: 0.62.1 -> 0.63.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector/releases.
meta.description for opentelemetry-collector is: "OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data"
meta.homepage for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector"
meta.changelog for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.63.0/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.63.0 with grep in /nix/store/sb4p9fxsibjx849w2iydbghbb5dpawk4-opentelemetry-collector-0.63.0
found 0.63.0 in filename of file in /nix/store/sb4p9fxsibjx849w2iydbghbb5dpawk4-opentelemetry-collector-0.63.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
opentelemetry-collector

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sb4p9fxsibjx849w2iydbghbb5dpawk4-opentelemetry-collector-0.63.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sb4p9fxsibjx849w2iydbghbb5dpawk4-opentelemetry-collector-0.63.0
ls -la /nix/store/sb4p9fxsibjx849w2iydbghbb5dpawk4-opentelemetry-collector-0.63.0/bin

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

1 package built:

opentelemetry-collector

Maintainer pings
cc @uri-canva @06kellyjac for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector/releases.
meta.description for opentelemetry-collector is: "OpenTelemetry Collector offers a vendor-agnostic implementation on how to receive, process and export telemetry data"
meta.homepage for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector"
meta.changelog for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.63.1/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.63.1 with grep in /nix/store/d80z2q4dp35r6fz636byy0qzraf900ah-opentelemetry-collector-0.63.1
found 0.63.1 in filename of file in /nix/store/d80z2q4dp35r6fz636byy0qzraf900ah-opentelemetry-collector-0.63.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
opentelemetry-collector

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d80z2q4dp35r6fz636byy0qzraf900ah-opentelemetry-collector-0.63.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d80z2q4dp35r6fz636byy0qzraf900ah-opentelemetry-collector-0.63.1
ls -la /nix/store/d80z2q4dp35r6fz636byy0qzraf900ah-opentelemetry-collector-0.63.1/bin

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

1 package built:

opentelemetry-collector

Maintainer pings
cc @uri-canva @06kellyjac for testing.


No validation for billing_address2

Hello.
I noticed that in order/billing.rb there's no presence validation only for billing_address2. Is that ok?

I would add it on the front end may be?

Yes, I think I can add it on front end. Also I can remove all billing_address fields except billing_address1. But it's strange than exactly billing_address2 absent in code

It's the same as delivery_address2. Some times all the fields aren't required.