Pretrained model ?

Hi, Thanks for your work! It looks like very funny !
could you share your pre-trained model ? I want to test how nice it is ! I'm glad to see it !

I am interested in getting it too! It will be great if the author could provide more detailed instruction on how to train the model using our own data.
Thank you!

Could you share your skinColor.pkl? I want to test the model with my data，Thank you!

Hi, it's amazing in your work! I have finish skin detection with GMM and GDfilter. I really want to test it with my data for comparing. Could you shared you pre-trained model? Thanks a lot.

Tied to pip install keras_segmentation  ,   python test .py
File "test.py", line 18, in
from segmentation_models.backbones import get_preprocessing
ImportError: cannot import name 'get_preprocessing'
keras==2.3.1
tensorflow==1.14.0
Thanks

pip install -U segmentation-models==0.2.1
ok

Yes, you must install proper edtion.
But the author didn't share the pretrained model, we can't test the model.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年1月9日(星期四) 上午8:36
收件人<EMAIL_ADDRESS>抄送: "断了的纟戋"<1113280356<EMAIL_ADDRESS>主题: Re: [JACKYLUO1991/Face-skin-hair-segmentaiton-and-skin-color-evaluation] Pretrained model ? (#1)
pip install -U segmentation-models==0.2.1
ok
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

you must install proper edtion.
But the author didn't share the pretrained model, we can't test the model.

@onefish51 @yxt132 @xdhzhang1995 Thank you for your support. After the paper is published, I will disclose the detailed training steps.

@onefish51 @yxt132 @xdhzhang1995 Thank you for your support. After the paper is published, I will disclose the detailed training steps.

Ok, Thanks a lot

Replied.


updated postman (4.6.1)

Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download postman is error-free.
[x] brew cask style --fix postman left no offenses.

Thanks!


Infographic:  Data Pipeline

Create a flowchart/infographic which demonstrates the data flow during the aggregation stage of the portal (everything from data sources throughout to scoring).
Intend this to be an overview on Data Pipeline § Aggregation Stage
I have an approximation, but needs further input from @edm1 and creative input from @andrewhercules

Just a thought on this; it might be nice to tie in the data model schematics we currently have in the site (example below).

Sounds good.  Really like those as a tool to contextualise what you're looking at


Fix creating certificate authority doc

Motivation
wget a github link is downloading an html page, not the actual content.
if we want to fetch the actual content, we should use the githubusercontent link.
Changes
Change the github link to githubusercontent link.

run cpp tests

run integration tests


[FLINK-3087] [Table-API] support multi count in aggregation

The Literal(1) is used as the IntermediateField of Count aggregation, so multi Count looks the same in ExpandAggregations.

Hi,
the reason it was implemented as it was is to eliminate common subexpressions. For example, if you wrote:
select(a.count, b.count)

the resulting expansion would be
intermediate = select(1.count as intermediate.1)
agg = intermediate.aggregate(intermediate.1, sum)
result = agg.select(intermediate.1, intermediate.1)

You see, the 1 would only be aggregated once here.
The problem was that selecting intermediate.1 twice is not allowed since the field names have to be unique.
Changing ExpandAggregations to this should do the trick:
var intermediateCount = 0
var resultCount = 0
selection foreach {  f =>
  f.transformPre {
    case agg: Aggregation =>
      val intermediateReferences = agg.getIntermediateFields.zip(agg.getAggregations) map {
        case (expr, basicAgg) =>
          aggregations.get((expr, basicAgg)) match {
            case Some(intermediateName) =>
              resultCount = resultCount + 1
              val resultName = s"result.$resultCount"
              Naming(ResolvedFieldReference(intermediateName, expr.typeInfo), resultName)
            case None =>
              intermediateCount = intermediateCount + 1
              val intermediateName = s"intermediate.$intermediateCount"
              intermediateFields += Naming(expr, intermediateName)
              aggregations((expr, basicAgg)) = intermediateName
              resultCount = resultCount + 1
              val resultName = s"result.$resultCount"
              Naming(ResolvedFieldReference(intermediateName, expr.typeInfo), resultName)
          }
      }

      aggregationIntermediates(agg) = intermediateReferences
      // Return a NOP so that we don't add the children of the aggregation
      // to intermediate fields. We already added the necessary fields to the list
      // of intermediate fields.
      NopExpression()

    case fa: ResolvedFieldReference =>
      if (!fa.name.startsWith("intermediate")) {
        intermediateFields += Naming(fa, fa.name)
      }
      fa
  }
}

Now the aggregations will be expanded to:
intermediate = select(1.count as intermediate.1)
agg = intermediate.aggregate(intermediate.1, sum)
result = agg.select(intermediate.1 as result.1, intermediate.1 as result.2)

This also required changing ExpressionCodeGenerator.scala, line 111 to:
def cleanExpr(e: Expression): Expression = {
  e match {
    case expressions.Naming(namedExpr, _) => cleanExpr(namedExpr)
    case _ => e
  }
}

because there is another bug that doesn't allow having nested Namings à la Naming(Naming(expr, intermediate.1, result.1)).

It's good that you found the problem and added a test. :smile:

a.count and b.count may not the same all the times(for example is a contains NULL values), that's why i try to aggregate it twice. But NULL value is not allowed until now, so i can update the PR in your way and revisit this issue after NULL value handling in Table API is enabled.

Oh, you are way ahead of me. :sweat_smile: You are right, keep it that way since we will probably have support for Null values in the future.
I'll merge it later if there are no objections. @twalthr ?

Looks good. No objecttions.

Ah, I see you changed it to my (wrong) suggestion. @ChengXiangLi Do you want to change it back to your initial version (plus maybe the fix for the naming and cleanExpr). Or should it be changed when adding support for null values?

Let's reuse the count aggregation now, as it's better for performance now. I would revisit this after NULL value handling is enabled.

Alright, I merged it. Could you please close it if github doesn't do so automatically.
Thanks for the work!


Release v1.2 to NPM

Good evening,
thank you for this amazing project!
It seems as though version 1.2.0 has not been released to NPM, is that on purpose?
I'm still stuck on the onDidChangeContentFast bug.
Thanks again and best,
Nicolai

Hi @NicolaiSchmid,
I forgot to publish that version to npm
Thanks for pointing it out.
Version 1.2.0 is now available in npm v1.2.0

It works now, thank you very much!


[REQUEST] Implement shape contains points verification

Is your feature request related to a problem? Please describe.
A shape should have shape points. This is a GTFS rule implemented in Google Python validator as ValidateShapePoints.
Describe the solution you'd like
Actual Google GTFS validator behaviour : verifies if shape contains points.
https://github.com/google/transitfeed/blob/d727e97cb66ac2ca2d699a382ea1d449ee26c2a1/transitfeed/shape.py#L120
Describe alternatives you've considered
Additional context
Line 182 in Error support priorities https://docs.google.com/spreadsheets/d/1vqe6wq7ctqk1EhYkgtZ0_TbcQ91vccfs2daSjn20BLE/edit#gid=0

Implemented in https://github.com/MobilityData/gtfs-validator/pull/70


Is there any API equivalent to deprecated 'client.read_data()'

I need to log all vehicles and their status (transform, velocity, control...) at every moment.
This how I implement:
while logging:
    timestamp = world.wait_for_tick()
    vehicles = world.get_actors().filter('vehicle.*')
    for vehicle in vehicles:
        transform = vehicle.get_transform()
        velocity = vehicle.get_velocity()
        control = vehicle.get_control()
        log.append('%d,%f,%f,%d,%s,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%r,%r,%r,%d\n' % (timestamp.frame_count, timestamp.elapsed_seconds, timestamp.delta_seconds, vehicle.id, vehicle.type_id, transform.location.x, transform.location.y, transform.location.z, transform.rotation.pitch, transform.rotation.yaw, transform.rotation.roll, velocity.x, velocity.y, velocity.z, control.throttle, control.steer, control.brake, control.hand_brake, control.reverse, control.manual_gear_shift, control.gear))

However, I found that data may come from different ticks but not the timestamp I expect.
Say, I may get timestamp from frame 1, transform from frame 2, velocity from frame 3...
How do I correctly get all data at SAME time?

Use synchronous mode and fixed-step solver. Both can be found in their documentation. The you need to add a world.tick() inside your while loop, which advances the world exactly one frame every step.

I tried and it works like a charm.
Thank you so much.

@kouyoumin Can you tell how you managed to do this? I'm looking to log similar data from simulation.

@HarnarayanSingh Try this:
world = client.get_world()
settings = world.get_settings()
settings.synchronous_mode = True
world.apply_settings(settings)

world.tick()
while logging:
    timestamp = world.wait_for_tick()
    vehicles = world.get_actors().filter('vehicle.*')
    for vehicle in vehicles:
        transform = vehicle.get_transform()
        velocity = vehicle.get_velocity()
        control = vehicle.get_control()
        log.append('%d,%f,%f,%d,%s,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%f,%r,%r,%r,%d\n' % (timestamp.frame_count, timestamp.elapsed_seconds, timestamp.delta_seconds, vehicle.id, vehicle.type_id, transform.location.x, transform.location.y, transform.location.z, transform.rotation.pitch, transform.rotation.yaw, transform.rotation.roll, velocity.x, velocity.y, velocity.z, control.throttle, control.steer, control.brake, control.hand_brake, control.reverse, control.manual_gear_shift, control.gear))
    world.tick()

Be aware the code above is old and may not compatible with latest API.

@kouyoumin  Thanks for the reply. Could you tell which Carla version did you try this out with?

@HarnarayanSingh Possibly 0.9.5


Minor change to water right landing page

Let's make the "State Native Right Webpage" line a hyperlink instead using the provided WaterAllocationNativeURL value the states gives us. In some cases that native WaterAllocationNativeURL can somtimes be very long and could mess up the card orientation.
Let's also move this "State Native Right Webpage" line to the top of the card right after the "Native ID" field so its quickly visible and the first thing the user sees.
Let's rename both the Water Right and Site landing pages title into
"WaDE Water Right Landing Page"
"WaDE Site Landing Page"

@yxlee61 question, when no URL is available, is it the case that the webpage label doesn't show up at all? that's probably okay for now but wanted to understand the behavior since QA does not have a lot of data to let me test much
https://westdaatqa.westernstateswater.org/details/right/ORwr_WR74029?state=N4IgtgziBcIQhgFwKYBtUEsUFoBuBOEAGnHgAcZQAvAexrABllc0YBGABhNSSwFcAJshgAWAKwA6AMwAmDiIAcnfG3wip%2BGdxoA7AOb8hMbGxkyJ%2BAGwczMsQoUiA7PjFiAvu6A

Yes, that was how I ended up implementing it. Is there a preferred way you would like this to be displayed? maybe back to "State Water Right Webpage: Unknown"?

I think "State Water Right Webpage: "Unavailable" is probably the best. That way we hint to that state that they need to make it available like other states. If we hide it, no one knows that we support it. Farming with no shaming lol


Key got stuck when alternate(latch) key is mapped for physical key

Microsoft PowerToys version
0.57.2
Running as admin

[ ] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
Prerequisite; using Japanese keyboard.

Open powertoys and keyboard manager
Mapping VK242/245, so-called Katakana/Hiragara/Romaji (it changes depends on IME setting) key to physical key
Map destination key

✔ Expected Behavior
The physical VK242/245 keys and newly mapped key output should work momentary switch just like other modifier key.
❌ Actual Behavior
The keys got stuck, keep pressed down and unable to un-press unless lock and unlock the screen.
For example, if I using Explorer, when I press VK242/245 it got stuck and every mouse click on files open property window.
Other Software
No response

The cause of this problem is probably the same as the following link
https://github.com/microsoft/PowerToys/issues/3397
What environment is causing the problem? In the following cases, the powertoys team has tried to support Japanese IMEs in the past, but could not complete.
i. You are using a Japanese IME.
ii. you are using the keyboard driver in the following link
http://kbdlayout.info/kbd106n/virtualkeys?arrangement=OADG109A
iii. you are using a JIS keyboard.
https://en.wikipedia.org/wiki/Language_input_keys#/media/File:KB_Japanese.svg
I faced the same problem and checked how Windows understands the above environment. Software used: https://kts.sakaiweb.com/keymill.html
In kbd106, the following keys are toggle keys, but when any key is pressed, some of the other keys are key evented.
Simply put, a single keystroke causes key events for multiple keys.
i. "alphanumeric" key (same position as capslock but another key called vk_attn, capsclock is shift+alphanumeric).
ii. "Hiragana/katakana" key
iii. "Halfwidth/Fullwidth" key
For more information, please see here.
https://github.com/kiripon/kbddv106/blob/master/kbd106.c#L523
However, I don't know which program is executing multiple key events in one key event.

almost the same issue
https://github.com/microsoft/PowerToys/issues/13955

I couldn't find how to keyboard driver, but I think the situation meet all the three conditions.
I searched about scan code and virtual key code, and found this article which explains a lot. AutoHotKey で正常に扱えないキーとその対策 - Qiita
I myself examined keyboard behavior using AutoHotkey software, and the result is same. When I press Katakana/Hiragara/Romaji key (which sends sc070), firstly it sends UP, and immediately pressing DOWN and holding it. I think this is the reason why swapped key got stuck. It actually sticking.
The test also shows that regardless of vk value change, sc value is consistent so there could be the way to resolve this issue.
Hope this helps.


Type alias resolves to different type than placing the type inline

TypeScript Version:  2.3.1, VS 2017 Preview 2
Code
// A *self-contained* demonstration of the problem follows...
type S = { items: {whatever:true}};
type ExtractedItems<T> = ({[K in keyof (T | { items: {} })]: { [key: string]: T[K] }} & { items: {} })["items"];
let extractedInline:     ({[K in keyof (S | { items: {} })]: { [key: string]: S[K] }} & { items: {} })["items"];
let extractedWithType: ExtractedItems<S>;

Expected behavior:
extractedInline and extractedWithType should have the same type.
Actual behavior:
extractedInline is typed as expected, extractedWithType is typed as {}.

If this behaviour IS in some way expected, that's not made clear in the documentation. Our natural assumption is that a type alias used in this manner to provide a level of indirection should not change the type.

When used as a generic, keyof (T | { item: {} }) becomes never, since T is not known to have any keys. that is not the case when the type is specified explicitlly. if you are sure T will have an item, then add a constraint, even something like:
type ExtractedItems<T extends {items?: any}> = ({[K in keyof (T | { items: {} })]: { [key: string]: T[K] }} & { items: {} })["items"];

@mhegazy Ahh, well that won't work for us then. We were using that as a (hacky) filter system to say "do this if T has items".
Why does keyof (T | { item: {} }) not use the generic type of T? Is this generics behaviour documented somewhere?
Thanks for taking the time to reply, sorry that we're about to be really difficult about it.
Reading through the spec, it appeared to say wrapping in a type alias should make no difference. In 3.7 Named Types is says

TypeScript has a structural type system, and therefore an instantiation of a generic type is indistinguishable from an equivalent manually written expansion. For example, given the declaration

and similarly 3.10 Type Aliases  says

Writing a reference to a non-generic type alias has exactly the same effect as writing the aliased type itself, and writing a reference to a generic type alias has exactly the same effect as writing the resulting instantiation of the aliased type.

There's no obvious reference in the spec to the behaviour you describe, and nothing in the spec stands out as describing how constraints are used.
3.6.1 Parameter List is the closest we could see to describing this behaviour, but it's not immediately obvious that it accounts for this.

in property accesses (section 4.13), new operations (section 4.14), and function calls (section 4.15), type parameters appear to have the members of their base constraint, but no other members.

You say

When used as a generic, keyof (T | { item: {} }) becomes never

This doesn't appear to be true in the general case though, in fact the whole thing works as we expected it to until the ["items"] on the end. We recognise that this may be the above quoted behaviour described in 3.6.1 of the spec, but it's certainly not intuitive that the rest of that type alias works until the ["items"].
Apologies if there's something obvious we're not getting and wasting your time with here. We recognise that this likely is working as intended, but feel the documentation could use some improvement here as it's certainly not working as we would have intuitively expected.

@mhegazy Ahh, well that won't work for us then. We were using that as a (hacky) filter system to say "do this if T has items"

that is something that is not supported currently, you probably want https://github.com/Microsoft/TypeScript/issues/12424

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Kata Containers 1.3.0

agent: change 9pfs mount option to cache=mmap
vc: qemu: Add config option to choose entropy source.
virtcontainers: revert "fix shared dir resource remaining"
block: Fix how rootfs is passed to kata-agent using virtio-blk
agent: clean up proxy process if start sandbox failed
config: Add Memory slots config
virtcontainers: support vhost and physical endpoints in AddInterface
device: Add GPU device support
virtcontainers: fix the issue of missing starting builtin proxy
Cleanup template properly
cli: add systemd-cgroup option
netmon: Add signals handler support
versions: update containerd version
scripts: Add throttler details to collect script
virtcontainers: hotplug memory with kata-runtime update command.
factory: start proxy before assign vm to a sandbox
virtcontainers: netmon: Monitor network changes
versions: Bump golang from 1.8.3 to 1.9.7
cli: add configuration option to enable/disable vhost_net

41619e4 vc: qemu:  Add option to change entropy source
9e606b3 virtcontainers: revert "fix shared dir resource remaining"
58cf7fc block: Fix how rootfs is passed to kata-agent using virtio-blk
ec87dca virtcontainers: support vhost and physical endpoints in AddInterface
19801bf config: Add Memory slots configuration.
bb513a7 agent: change 9pfs mount option to cache=mmap
0ddf99d agent: clean up proxy process if start sandbox failed
5612694 virtcontainers: fix the issue of missing starting builtin proxy
67ffa2f factory: close factory in UT
b193f0f template: clean up template mountpoint on failures
37b83c8 device: Add GPU device support
2216d52 vendor: Update govmm to add vfio mediated device support on root bus
048616f netmon: Add signals handler
1675410 pkg: signals: Factorize signals handling through a Go package
723fbac versions: update containerd version
0075175 cli: add systemd-cgroup option
6fc13e9 scripts: Add throttler details to collect script
12a0354 sandbox: get and store guest details.
13bf7d1 virtcontainers: hotplug memory with kata-runtime update command
0928519 vendor: update agent to support memory update
0ffe81c cli: config: Make netmon configurable
1406d99 virtcontainers: Start network monitor from virtcontainers
29e2fa0 virtcontainers: Avoid conflict with network monitor
f6ce465 vendor: Update agent vendoring
55af108 netmon: Add unit testing
f131590 netmon: Build netmon from the master Makefile
fca7435 netmon: Add logrus support
bbf2a47 netmon: Don't rely on agent protocol
b708a4a netmon: Monitor network changes
d75841e ut: add more UTs
07c1f18 factory: start proxy after create new VM
4738d4e agent: add setProxy/getAgentURL interface
8f77c33 proxy: decouple from sandbox
f39fa5d proxy: remove newProxyConfig
c41c9de proxy: do not decode proxy config
225e10c cli: add configuration option to enable/disable vhost_net
5ebb7cf vendor: Update govmm to disable vhost when host doesn't support vhost-net
d814bc5 versions: Bump golang from 1.8.3 to 1.9.7

/test


Adds step to onboarding to capture personal information

Many clinical + research projects need to collect personal information in the onboarding process, such as patient name, date of birth, and gender. This PR adds a step to the onboarding process to allow entry of this information, and stores it within the user document in Cloud Firestore. The step is optional, and the types of data to collect can be configured in CKConfiguration.plist.

This needs to be refactored using ORKRegistrationStep.


FIPS indicator epic

Refer to the FIPS indicator design document (#23609).  This issue is meant to act as an epic covering the indicator work that remains.

[x] #24996
[x] disable 3DES encryption + indicator  #24960
[x] ECDSA B & K curves are deprecated (but still approved IG C.K Resolution 4) ${\textsf{\color{green}deprecated doesn't need an indicator}}$
[x] ECDH cofactor  #25139 #25548 #25582
[x] Ed25519 & Ed448 now approved #24882 #22112
[x] X25519 & X448 ${\textsf{\color{green}not approved}}$ (keygen and key exchange indicators)
[x] RSA encryption with PKCS ⌗1 version 1.5 padding no longer allowed #25070
[x] RSA ${\textsf{\color{green}signing using PKCS ⌗1 still allowed}}$
[x] RSA signing using X9.31 no longer allowed #24021 #24938
[x] RSA PSS saltlen restrictions #25115
[x] TLS1_PRF #23900
[x] #24937 #25032
[x] check allowed digests ${\textsf{\color{green}all completed}}$

[x] TLS_1_3_KDF only SHA 256, 384 are allowed due to RFC 8446 Appendix B.4 #23889
[x] TLS1_PRF only SHA256, 384, 512 are allowed #23889
[x] K963KDF SHA1 not allowed #23889
[x] X942KDF #24862
[x] PBKDF2 #24862
[x] HKDF #23889 #25093
[x] KBKDF ${\textsf{\color{green}relies on underlying CMAC, HMAC or KMAC for digest checking}}$
[x] SSKDF #23889
[x] SSHKDF #23889
[x] HMAC ${\textsf{\color{green}already fails if an XOF digest is used}}$
[x] KMAC ${\textsf{\color{green}doesn't allow a user specified digest}}$
[x] PKEY #24936 #25020

[x]  check allowed ciphers ${\textsf{\color{green}all completed}}$

[x] CMAC: ${\textsf{\color{green}checks for CBC mode cipher}}$ #25022
[x] KBKDF CMAC: ${\textsf{\color{green}checks for HMAC/CMAC correctly}}$
[x] GMAC: ${\textsf{\color{green}checks for GCM mode cipher}}$

[x] PBKDF2 iterations and salt length check #24120
[x] TEST_RAND not approved, add an indicator #24851
[x] KMAC lower bounds check on output size (SP800-185 Section 8.4.2) #24917
[x] HMAC output length (FIPS 140-3 IG C.D note when using a truncated HMAC) ${\textsf{\color{green}we never output less than a block from the underlying digest}}$
[x] key size checks ${\textsf{\color{green}all completed}}$

[x]   ≥112 bits for HKDF, SSHKDF and TLS KDF #23900
[x]   ≥112 bits for KBKDF #25095
[x]  ≥112 bits for PBKDF2 #24120
[x] RSA key size ≥ 2048 approved for keygen, signatures and key transport.  1024 allowed for verification #24623
[x]  ≥112 bits for HMAC, CMAC and KMAC #25049
[x] ≥112 bits for EC keygen #25008

[x] add indicator for P-192 which is now legacy ${\textsf{\color{green}covered by the minimum key strength indicator}}$
[x] disable DSA signing + indicator #24799
[x] DSA legacy verification only + keygen #24978
[x] unit test improvements / refactoring ${\textsf{\color{green}all completed}}$

[x] #25135
[x] #25136 #25160
[x] #25137 ${\textsf{\color{green}the existing tests seem to cover all interesting cases}}$

[x] #25162
[x] #25194
[x] #25178 #25223
[x] #25211
[x] #25217
[x] #25222
[x] #23832
[x] #25195
[x] #25517 #25572
[x] #25147 #25159
[x] #25118
[x] #25529
[ ] #25507 ??

All completed.

Add enforcement/indicator for 112 bits of output for PBKDF only.
Add documentation that all other KDFs produce "keying material" not "keys".

    /*
     * FIPS requires generation of AES-GCM IV's inside the FIPS module.
     * The IV can still be set externally (the security policy will state that
     * this is not FIPS compliant). There are some applications
     * where setting the IV externally is the only option available.
     */
    if (!gctx->iv_set) {
        if (!EVP_CIPHER_CTX_is_encrypting(ctx) || !aes_gcm_iv_generate(gctx, 0))
            return -1;
        CRYPTO_gcm128_setiv(&gctx->gcm, gctx->iv, gctx->ivlen);
        gctx->iv_set = 1;
        gctx->iv_gen_rand = 1;
    }

@paulidale I don't think this will fly anymore without an  unapproved indicator.

The GCM IV is problematic.  E.g. TLS sets it externally but this doesn't break the FIPS-ness since it's one of the protocols allowed to "break" the rules.
I'm reasonably confident that we've missed some indicators, I'm expecting the lab to point out the relevant ones (or at least the ones they check for).
3.4 beta is scheduled for later today and that means a feature freeze -- we'd have to argue new indicators as being bugs and have fixes ready to go very soon.


Work Mod on 1.19.3

Hello
please add the ability to use the mod on version 1.19.3 of the game.
seyas with this mod, with the latest version, we get an error "-1"
MOD version: BBOutlineReloaded-2.5-1.19.2-fabric
fabric-loader-1.19.3
release fabric-loader-0.14.11-1.19.3
error:
The game crashed whilst initializing game
Error: java.lang.IncompatibleClassChangeError: class com.irtimaled.bbor.client.gui.SettingsScreen$1 overrides final method net.minecraft.class_339.method_37020(Lnet/minecraft/class_6382;)V

You are getting this error because we have not yet released a version for 1.19.3 yet, and the 1.19.2 version will not work with any other version.


Emberwind character sheet

Changes / Comments
Character sheet for the TTRPG Emberwind. This is the first commit of this content.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[y] Does the pull request title have the sheet name(s)? Include each sheet name.
[n] Is this a bug fix?
[n] Does this add functional enhancements (new features or extending existing features) ?
[n] Does this add or change functional aesthetics (such as layout or color scheme) ?
[n] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[y] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

@clevett Am I supposed to update the approved.yaml or is my sheet still under review and it will be added later? I making sure I didn't miss any steps.
Thanks,
Lexi

Cassie does that part, you don't have to worry about it. Sheet updates are pushed live on Tuesdays, and does the yaml part if new sheets are added.

Ok thanks for clarifying. I was worried I missed a step because this is a new character sheet.


Implement CMS_INTERNAL_IPS

Coverage decreased (-0.3%) to 88.724% when pulling 97c50fee715d2d8781f651e6307de0e7934c06b7 on mkoistinen:feature/restrict_toolbar_to_internal_ips into 7af18a5aef69a6dc855200a61a46059b3b47d382 on divio:develop.

Ok to merge

Coverage decreased (-1.3%) to 87.726% when pulling bfafc7eca5599aa36fb71db1c32f2eb7604ea333 on mkoistinen:feature/restrict_toolbar_to_internal_ips into 7af18a5aef69a6dc855200a61a46059b3b47d382 on divio:develop.

Coverage decreased (-1.3%) to 87.726% when pulling 2c87e0540d2f9206ac7e4878d02055550cf9a232 on mkoistinen:feature/restrict_toolbar_to_internal_ips into 7af18a5aef69a6dc855200a61a46059b3b47d382 on divio:develop.

Coverage decreased (-1.3%) to 87.76% when pulling f9bdd34e9b628a96a2429ed82c470dca1f2dc953 on mkoistinen:feature/restrict_toolbar_to_internal_ips into 7af18a5aef69a6dc855200a61a46059b3b47d382 on divio:develop.

Ok to merge


Fix evaluate

Rewrites the evaluate command to actually work w/ the new trainer rewrite and the new vlosses rewrite.
At some point, the 'name' field was removed from the DualNetwork object, although not actually removed from places that either set or referenced it.  Happily, those codepaths did not diverge...
Perhaps the player object should keep track of its semantic 'name', distinct from the filename/path used to reference its network files, and also distinct from the identifier it uses for GTP.

/retest

/retest

'scandir' is not quite what i want.  i just want it to spit out 'ls -l' so i can verify there's some kind of nonzero-sized files.  I don't want to check what they are, or read them, or make any other assertions other than 'looks like small SGFs were written'.
Re: subprocess.x(foo.split()) right right right, fixed.


IE11 support - will running through babel solve it?

At the docs it states ES6 requirement, it doesn't specify which elements of ES6 are used.
I wonder whether running it through babel will provide IE11 support.

Anyway IE11 has a lot of bugs and I don't resolve it.

Even an ES6 polyfill generated by polyfill.io won't work here?
This subject should at least be discussed. at current time IE11 support is still widely requested.

Even an ES6 polyfill generated by polyfill.io won't work here?

I don't mean lack of modern APIs. So it doesn't help the problem.

So? what is the problem?

Polyfill also won't be a solution.


Add Contribution guidelines

And build instructions. Don't remember much for doing it from command line.

Google Java Style Guide, 4 spaces for ident and horizontal alignment when it makes sense.


Build controlled vocabularies for names by sex and incorporate results into logic

function built and base Spanish controlled vocab added to repo, not integrated into logic yet


IC: upon read failure, pause between tries, not after tries.

On the last try (or the only try, if failure_retries was 0), we were
needlessly delaying.

LGTM!


improve answer for 20.3.3

If you want to show

However, you can represent that value (exactly) with a numeric vector at the cost of about two times the memory.

you should show
> as.numeric(.Machine$integer.max) + 1
[1]<PHONE_NUMBER>

rather than
as.numeric(.Machine$integer.max) + 1
#> [1] 2.15e+09

By the way, I suspect that 2e-308 should mean 2*10^-308^ instead of 2^-308^

Since 1 is real it should coerce the value to numeric and as.numeric isn't needed. That's why you need to add by 1L to keep it an integer

Our intention should be spoke out by the code, not implied by (obscured) syntax rules.

Very good point. The distinction between 1L and 1 is still obscure, though appearing in more tidyverse stuff due the stricter error checking in R objects. And relying on people remembering coercion rules is impossible since I still figure it out by trial and error many times.


Entwined™ [PCSA00140]

App summary

App name: Entwined™
App serial: PCSA00140
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3168
Commit hash: https://github.com/vita3k/vita3k/commit/a7143567
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Sam
OS: Windows 10
CPU: AMD 5500u
GPU: AMD Radeon Graphics
RAM: 6 GB

Issues

Log
vita3k.log
Recommended labels

Playable
B?
C?

Having trouble with gameplay scene loading, but now I find how to fix it.
I'm using vita3k version 0.1.8 build 3249, and the game keeps locks when trying to start into game scene (as shown in the screenshot)

How to fix: Just turn off  in CPU settings, and game loads correctly.


and again, use simple-get

I definitely realized that it's better to use simple-get plus concat-stream. It's really small and really better and even smaller than github-request huh.
And return callback(err, buffer, stream) without JSON.parse, cuz Github have endpoints that not return JSON, like /markdown and it crash when you try to do that. Returning buffer instead of JSON.parse(res) would free us up. Also giving the readable stream is  good thing.
Another thing is duplication of defaulting opts.apiurl and sending everything from data to the body of the request. Which isn't okey for me. Like, now it's possible to define placeholders, headers, body, method and etc stuff through data from .post(path, data, cb), but you also pass them to the body of the request e.g.
var data = {
  owner: 'jonschlinkert',
  repo: 'github-base',
  headers: {
    foobar: 'baz'
  },
  title: 'foo bar',
  body: 'baz qux @chorks woohoo'
  body: {
    bar: 'qux'
  }
}
github.post('/repos/:owner/:repo/issues', data, console.log)

All that data would be stringified and send to the request (from the index.js .request() directly to github-request pkg), from which only 2 fields are needed for request body.
And here can view another problem. What means that body, because some endpoints expect that parameter, like above example - "Create an issue" endpoint. But in the utils.js in the one if you check that data exist, in the other that opts.body exist - which actually is data.body because the extend.
And exposing token or username+password directly to the server request... don't think so.

Other than that.. it's awesome, as always!

all good points, sorry you did some work on this that didn't get merged in, I already had most of the refactoring done. I think you're right about simple-get, I'd be happy to merge that in if you want to do a pr.

fwiw, because of the scope and amount of things I need to get accomplished, I try as hard as I can to make libs awesome - but I don't have as much time as I'd like to explore every possible alternative. So I really appreciate the feedback and help.

sorry you did some work on this that didn't get merged in, I already had most of the refactoring done.

Yea, it's normal, no problem.

I'd be happy to merge that in if you want to do a pr.

:+1:

but I don't have as much time as I'd

same here lol

@jonschlinkert okey, it's ready! :tada:
I'll PR when add tests and cover 100% coverage with test api server. :)

:+1:

so... closing this, because #4 merged.
/cc @jonschlinkert release and publish

oops meant to click comment. it's on the way


Added Kio to powered by list

Added a page with information about Kotlin DSL for Apache Beam Java SDK.

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

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

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

GitHub Actions Tests Status (on master branch)

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

R: @timrobertson100

Waiting for green but looks good. Thanks @chermenin


Fl4k skills not showing

Every other character works fine except Fl4k, Tested on a PC and laptop and got same results

Also having this issue

I'm not a fan of the official skill trees on borderlands.com.  I much prefer your easy-to-see and easy-to-navigate trees.  Please let us know when your FL4K tree is ready!

It's because (at least) all flak skill images are missing

1 month no reaction, I guess OP will not come to help

See: https://github.com/seigler/bl3skills.com/issues/13#issuecomment-520157696

This isnt working because the Fl4K tree needs filling in: https://github.com/seigler/bl3skills.com/blob/master/src/pages/Beastmaster/skills.js
An example of how these work can be found in Zanes tree here: https://github.com/seigler/bl3skills.com/blob/master/src/pages/Operative/skills.js

The actual tree fill I can add as part of https://github.com/seigler/bl3skills.com/issues/13.
Not sure what to do about the missing talent icons yet.

@seigler I fixed this on #15, could you merge the pull request so anyone can easily add the tests? Thanks

The icons now appear, but hovering them doesn't provide the correct text.

PR up for adding data to FL4K's skills.js
https://github.com/seigler/bl3skills.com/pull/18

Thank you @rlindsey28 for doing this! The update is live.


fossil: 2.22 -> 2.23

Description of changes
https://fossil-scm.org/home/doc/trunk/www/changes.wiki#v2_23
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2914

Result of nixpkgs-review pr 265115 run on x86_64-linux 1

1 package built:

fossil

Runs fine, LGTM. Thanks!


运行一会后报错

  File "/media/admin1/envs/anaconda3/envs/leng_lip/lib/python3.7/site-packages/transformers/models/clipseg/modeling_clipseg.py", line 1458, in forward
    conditional_pixel_values=conditional_pixel_values,
  File "/media/admin1/envs/anaconda3/envs/leng_lip/lib/python3.7/site-packages/transformers/models/clipseg/modeling_clipseg.py", line 1360, in get_conditional_embeddings
    raise ValueError("Make sure to pass as many prompt texts as there are query images")
ValueError: Make sure to pass as many prompt texts as there are query images

能成功100多张图片，然后就会出现这样的报错停止。
使用命令如下
python scripts/main_ssa_engine.py --data_dir=data/UCM_Captions --out_dir=output --world_size=4 --save_img --sam --ckpt_path=../../mydata/sam_vit_h_4b8939.pth --light_mode

遇到了同样的问题，请问楼主解决了么

我也遇到了同样的问题，请问有解决方法吗？

I have encountered the same issue. The problem occurs in the clipseg_segmentation function in the Semantic-Segment-Anything/scripts/clipseg.py file. When class_list contains only one class, it appears as a string instead of a list. Additionally, when there is only a single class, the output of clipseg_model's logits will have a shape of (H, W), which causes dimension inconsistency when using F.interpolate for scaling. Therefore, some modifications are needed. Here is the modified code:
def clipseg_segmentation(image, class_list, clipseg_processor, clipseg_model, rank):
    if isinstance(class_list, str):
        class_list = [class_list, ]
    inputs = clipseg_processor(
        text=class_list, images=[image] * len(class_list),
        padding=True, return_tensors="pt").to(rank)
    # resize inputs['pixel_values'] to the longest side of inputs['pixel_values']
    h, w = inputs['pixel_values'].shape[-2:]
    fixed_scale = (512, 512)
    inputs['pixel_values'] = F.interpolate(
        inputs['pixel_values'],
        size=fixed_scale,
        mode='bilinear',
        align_corners=False)
    outputs = clipseg_model(**inputs)
    try:
        logits = F.interpolate(outputs.logits[None], size=(h, w), mode='bilinear', align_corners=False)[0]
    except Exception as e:
        logits = F.interpolate(outputs.logits[None, None, ...], size=(h, w), mode='bilinear', align_corners=False)[0]
    return logits

This modification includes converting class_list from a string to a list when it is of type str. It also ensures consistent dimensions when using F.interpolate by handling the case when clipseg_model's logits have a shape of (H, W).


Alternate Advanced Code Solution

Solution directly calculating LCM without the GCD. Utilizes built-ins and is optimized in Firefox.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@ojeytonwilliams merge if it LGTY

@crystal-dawn I'm really sorry, but I found an earlier PR, #35884, that covers a lot of the same ground as yours.  As they have been waiting longer, their PR will have to take precedence.
If that PR gets merged (it needs to be reviewed), then we can do one of two things.  Close this as a duplicate or, if you still feel like the article could be improved, you could add some more changes.
Once again, apologies, I should have checked for the conflict earlier on.

@ojeytonwilliams No worries! I tried searching for an open PR before I submitted, but I didn't see that one. Fair is fair!

@crystal-dawn We have a fairly new tool you can use to find any PRs for a specified file.  You can find it at https://contribute.freecodecamp.org/dashboard.  It will be the Filename Search feature.  Just enter part of the filename and it will give you a list of files containing that name and any associated PRs.  Then you can open each PR to make sure the changes being made are not something you are considering making yourself.

@RandellDawson that's an awesome tool, will surely be useful in the future. Thanks for the info 👍

I going to go ahead and close this as duplicate, because we will be merging the earlier PR.
Thanks for understanding.


FR: Change Raster word in View menu

Since it's a grid, shouldn't it be called grid? Or keep raster and add (grid) like "Raster (Grid)" ?

Grid is better. In code I call it raster because Grid/Guide is too similiar.


Animation effect

In Our Chef section , the animation is very slow. So I would like to do this and resolve it under GSSOC'23

please assign this issue in under Gssoc'23
Thank You!


Encrypt credentials in properties file

Many organizations can not have passwords in the clear within a file.  It is generally not a good security practice.   The idea here is that the gradle.properties file would have the password encrypted and it would be descrypted at runtime before being used to authenticate to nexus.
Here are some possible help to implement this:

Gradle Creds
Gradle Maven Settings

But I will leave the implementation choice to you :)
At the vary least, provide a "hook" so that the password could be provided by one of these solutions and let the user do the integration.

It's not the purpose of this plugin to capture user input or read/encrypt credentials. That should be the responsibility of Gradle core or another plugin. You might want to use https://github.com/etiennestuder/gradle-credentials-plugin instead.


Parser

Finish the RFC 5322 parser on the 'dev' branch, with tests for each parse function.

Finished the main thrust, but I believe there are more restrictions in the text of RFC5322 (outside of the ABNF) which are not yet coded.

Parser is complete except for folding issue #3.  One more read of the RFC is still a good idea.


fixing appveyor

fixing appveyor, the branch name is incorrect cause I am bad at git

Pull Request Test Coverage Report for Build 367

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.797%

Totals

Change from base Build 365:
0.0%

Covered Lines:
238

Relevant Lines:
338

💛  - Coveralls


Add ABE for <amp-fx="fly-in">

This PR does the following:

Cleans up previous examples to follow pattern in demos on other ABEs
Adds demos for <amp-fx="fly-in">
Also adds demos on combining presets to make more complicated animations

@sebastianbenz sorry for the long PR. PTAL?

@nainar could you rebase from master for fixing the build issue? thanks!

@kul3r4 done!

No problem! :) thank you for taking a look!


Td 1113/feat/etcd

We probably need some unit tests too.

I will write them today and sent for review


CLOUD-670 username changed in azure and gcc

@keyki

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1119/

Username shall be configured from one common place for every provider and not multiple places like in the fix. Using the cloudbreak username as default is OK, but it shall be mentioned in the UI and documentation that the users will be able to log in to their cluster with cloudbreak user.

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1144/


mouse_exited signals when hovered over another control inside its Rect

Operating system or device, Godot version, GPU Model and driver (if graphics related):
3.0, w7 64-bit
For example:

mouse_exited() Emitted when the mouse leaves the control's Rect area.

However, in the example linked below, the signal is called even if you hover over a control that is inside its Rect2. That shouldn't be happening, right?  Maybe am missing something ^^
Link to minimal example project:
mouse_exited_bug.zip

So, I'm not really a C++ expert (only javascript dev here w/ nodejs )
I decided to dive into the code a bit more because I mean, I do use the engine a lot. But would much rather have the professionals take a whack at it.
However, I think the culprit relies somewhere here:
https://github.com/godotengine/godot/blob/master/scene/main/viewport.cpp#L1880
I think it's calling mouse_exited whenever the gui.mouse_over is true and if it's hovering over a new control compared to the last one? Except it's not taking into account the bounding Rect2? Not entirely

Note: The original issue reporter closed all their issues before deleting their account. If you are affected by a similar issue/want a similar feature, please file a new ticket (referencing this one if it contains useful information) so that it can be further looked at and eventually resolved.


Correct spelling error

Minor correction to something I noticed whilst writing blog post.

Codecov Report

Merging #208 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #208   +/-   ##
=======================================
  Coverage   99.64%   99.64%
=======================================
  Files          16       16
  Lines        1126     1126
=======================================
  Hits         1122     1122
  Misses          4        4

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 33da6bb...3fa77ee. Read the comment docs.


Explore/Spike: Blockchain hash algorithm

The blockchains' consensus uses a DAG, which needs to calculate the Hash.
We need to formally pick one.
The leading choice some previous team discussions:

BLAKE3
Keccak256 (SHA-3)

Given the frequency Hashing will be one in the blockchain, there a preference for speed but the usual "no collisions" is a hard must.
There's no functional or behavioral requirements at the moment.

Currently we have
https://github.com/pyrsia/pyrsia/blob/bbe6bc4c2b88c4401af36a55644dca8246861f58/src/blockchain/src/header.rs#L56
which is using https://github.com/multiformats/rust-multihash thats from the same team running libp2p
And it support both.

@fishseabowl I noticed in our Hackathons we used difference algorithms/crates.
Would you like to write the requirements for us to pick one?
You have the most experience, so I think this is best for you.
This was we can make an informed decision 😄

Keccak is a NIST approved hash algorithm. Ref: https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.202.pdf
Blake3 is designed for consistent high performance.   The chart below is an example benchmark of 16 KiB inputs on modern server hardware (a Cascade Lake-SP 8275CL processor).

Ref: https://github.com/BLAKE3-team/BLAKE3-specs/blob/master/blake3.pdf, https://github.com/BLAKE3-team/BLAKE3
I suggest at this moment we use keccak, but if the hash function is a performance bottleneck, we can switch to Blake3.


 Please help!

Please don't delete the bug template.

That information is very, very important for us to figure out what happened to your Terminal.

Please reopen this thread so I can get feedback on what is wrong with my terminal program.

This is my current system for consideration to the above reported bug.

Can we get the version of the Terminal that you're running? Perhaps share your profiles.json?

Windows Terminal (Preview)
Version: 0.9.433.0

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
"$schema": "https://aka.ms/terminal-profiles-schema",
"defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

"profiles":
{
    "defaults":
    {
        // Put settings here that you want to apply to all profiles
    },
    "list":
    [
        {
            // Make changes here to the powershell.exe profile
            "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
            "name": "Windows PowerShell",
            "commandline": "powershell.exe",
            "hidden": false
        },
        {
            // Make changes here to the cmd.exe profile
            "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
            "name": "cmd",
            "commandline": "cmd.exe",
            "hidden": false
        },
        {
            "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
            "hidden": false,
            "name": "Azure Cloud Shell",
            "source": "Windows.Terminal.Azure"
        }
    ]
},

// Add custom color schemes to this array
"schemes": [],

// Add any keybinding overrides to this array.
// To unbind a default keybinding, set the command to "unbound"
"keybindings": []

}

And what's your %PATH% environment variable set to?

PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\PuTTY;C:\Users\Captain\AppData\Local\Microsoft\WindowsApps;;C:\Users\Captain\AppData\Local\Programs\Microsoft VS Code\bin;C:\Program Files (x86)\Nmap

Any feedback on this issue?

/feedback


Implement Spatial Queries

[ ] Contains
[ ] Crosses
[ ] Disjoint
[ ] Intersects
[ ] Overlaps
[ ]  Touches
[ ]  Within
[ ]  Covers
[ ]  Covered By

Have some time over the next few days to work on these. Going to implement them as separate functions I think but it might also be good to have one that just takes the target GeoSeries / Geometry and a query type and returns a binary Series .
Similarly we will want to have the ability to pass the function either a single Geometry which the GeoSeries is evaluated against or a GeoSeries in which case the evaluation happens pair wise


Fixes for experiment 2

Fixes #152

Fix empty entries for initial storage level.
Use correct template depending on experiment
Distinguish central from decentral heat

TODO:

[x] Adapt postprocessing to heat distinction
[ ] Check postprocessed results to make sure that the changes leave results for experiment 1 the same

Added electricity-h2_cavern to scenario 2
Removed nuclear-st and electricity-h2_cavern from scenario 3
Removed nuclear-st from scenario 4
Added a fixed electricity demand for h2-electrolysis in scenarios 2 and 4.

Updated mapping for these scalar results:

[x] EnergyConversion_Losses_Electricity_Hydro_Reservoir
[x] EnergyConversion_SecondaryEnergy_Electricity_Hydro_ReservoirPump
[x] EnergyConversion_SecondaryEnergy_Electricity_Hydro_ReservoirTurbine
[x] EnergyConversion_VarOM_Electricity_Hydro_Reservoir
[x] Storage_Capacity_Heat_LargeCharge heat_central
[x] Storage_Capacity_Heat_LargeDischarge heat_central
[x] Storage_Capacity_Heat_SmallCharge heat_decentral
[x] Storage_Capacity_Heat_SmallDischargeheat_decentral

Renamed Storage_Electricity_H2Cavern to Storage_H2_H2Cavern according to new results template version.


⚠ Bofrost.de has degraded performance

In 51d00d9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 996 ms

Resolved: Bofrost.de performance has improved in 5578dc7 after 18 minutes.


Categorical Feature Handling

Hello,
I am looking to verify how categorical features are handled for models that support categorical features. I've found things here and there like this and this, but I'm looking for more definitive answers. Additionally, I'd like to test different variations of categorical feature handling and how I can adjust the parameters would be great to know.
Thanks!

We don't do anything special, we just pass them through. If you provide categorical columns and a model that doesn't support them you'll most likely get an error.


sha1 failed

i am having these issues lately upon converting games eventhough i already downloaded the patch... i was trying to convert the same game again due to blackscreen issues for nfs most wanted... that i should not resign it and just install through debug pkg enable... this happens on large patches but anything below 1gb seems to be success in sha1... i have a poor internet here at i dont want to download the patch again... :(

Updated to v13 and everything seems ok now... thanx senpai :)))


Broken styling on Drive homepage

Hi, it seems the recent updates have broken the styling on the home page. Could you please take a look at it? Thank you in advance.

It seems like it took a bit for the new design to get rolled out to me, but I'm seeing this now as well and looking into it.

This should be fixed with 574b4ae, so I'll be closing this — please feel free to open another issue if you're still seeing those issues!


[BUG] ArgumentNullException when calling CreateIfNotExistsAsync with OpenTelemetry populating a tag with the response message

Library name and version
Azure.Data.Tables v12.8.0
Describe the bug
After adding OpenTelemetry to our app, we are getting the following exception and stack trace when calling CreateIfNotExistsAsync:
System.ArgumentNullException: Value cannot be null. (Parameter 'value')
Stack trace:
System.ArgumentNullException:
   at Azure.Data.Tables.Models.TableErrorCode..ctor (Azure.Data.Tables, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Azure.Data.Tables.Models.TableErrorCode.op_Implicit (Azure.Data.Tables, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Azure.Data.Tables.TableClient+<CreateIfNotExistsAsync>d__39.MoveNext (Azure.Data.Tables, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   <client code omitted>

We have the following OpenTelemetry setup in Program.cs:
builder.Services.AddOpenTelemetry()
       .UseAzureMonitor()
       .WithTracing(traceBuilder =>
           traceBuilder
               .AddHttpClientInstrumentation(c =>
                {
                    c.EnrichWithHttpResponseMessage = (ac, res) =>
                    {
                        var statusCode = (int)res.StatusCode;
                        if (statusCode is >= (int)HttpStatusCode.BadRequest and < (int)HttpStatusCode.InternalServerError)
                        {
                            var body = res.Content.ReadAsStringAsync().Result;
                            if (!string.IsNullOrWhiteSpace(body))
                            {
                                ac.SetTag("http.response.body", body);
                            }
                        }
                    };
                })
               .AddAspNetCoreInstrumentation(config =>
               {
                   config.Filter = httpContext =>
                   {
                       var unwantedSegments = new[] { "/v1/healthchecks", "/metrics" };
                       foreach (var unwantedSegment in unwantedSegments)
                       {
                           if (httpContext.Request.Path.Value.StartsWith(unwantedSegment))
                           {
                               return false;
                           }
                       }

                       return true;
                   };
               })
       );

Versions:
Azure.Data.Tables v12.8.0
OpenTelemetry.Extensions.Hosting v1.6.0
OpenTelemetry.Instrumentation.AspNetCore v1.6.0-beta.3
OpenTelemetry.Instrumentation.Http v1.6.0-beta.3
Azure.Monitor.OpenTelemetry.AspNetCore v1.0.0

Expected behavior
An exception to not be thrown.
Actual behavior
An ArgumentNullException is getting thrown.
Reproduction Steps
Clone the following repo.
Environment
We are running this in Azure, but it is reproducible on a Windows 11 machine.
6.0.417 [/usr/local/share/dotnet/sdk]
Microsoft.AspNetCore.App 6.0.25 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Thanks!
I know that one shouldn't really call the .Result on an async method, but the EnrichWithHttpResponseMessage action in OpenTelemetry doesn't contain an async overload.

As an FYI, this works fine against Azurite, but I guess that is not identical as going against the real storage tables.

Does it still throw if you change .Result to GetAwaiter().GetResult() ?

Does it still throw if you change .Result to GetAwaiter().GetResult() ?

Yes.


Compiler segfault when cross-compiling a project for Windows

Hi,
I'm working on a small project using Raylib.zig and I'm experiencing some issues when I try to cross-compile the project from Linux to x86_64_windows_gnu. I've tried various recent Zig 0.11-dev versions but they all segfault when I try to build the project in any of the Release modes - Debug builds work fine.
Here's the failing GitHub Actions output from the minimal example project I'm trying to build: https://github.com/recursiveGecko/zig-raylib-segfault-repro/actions/runs/5624683409/job/15241992190#step:4:66
I've filed an issue in the Zig repo, but I'd like to know if there's anything I can do in the meantime to work around it?
Any tips, example projects or guides would be really appreciated! Thanks :)

I encounter the same problem on Windows machine with my example repo.
Unfortunately I have no idea what causes that error 😅
Thanks for filing an issue in the zig repo. I hope this get fixed soon.
I set a reminder for myself to test this periodically and let you know if it works again.

Same here on MacOS M1

This works only on linux, because it links with LIBC


AUTH_KEY_DUPLICATED

Hi, I am trying to develop Telegram Service using TdLib (C-sharp) where I have to retrieve the Chat Info from a public Channel.
The service was working fine, but I am getting AUTH_KEY_DUPLICATED error : { code = 406 }, whenever I am trying to use GetChatHistory for any public Channel.
Any help would be greatly appreciated. Thanks

Hi, Thanks for the response. But I am unable to figure out, how to delete the database directory. Please suggest.
Thanks

You can use TDLib's destroy method for that. Or you can delete it manually through any file manager like Explorer.

Many thanks, the issue is resolved after using destroy method.

Is it possible in 1.4.0 to just reset the keys without destroying cached content?

TDLib doesn't delete cached files while logging out, only database is deleted, because it contains private data and can't be reused.


Update to the latest clp submodule commit.

References

Description

This PR updates to the latest version of CLP.
Validation performed

Tested locally to ensure the build flow worked and unit tests passed.
GitHub workflow all passed.

Can we also pick the change from https://github.com/y-scope/clp/pull/341 after it is merged?
(#56 needs that)

Can we also pick the change from y-scope/clp#341 after it is merged?
(#56 needs that)

Sure. I will update the submodule commit after CLP PR#341 merged.

Can we also pick the change from y-scope/clp#341 after it is merged?
(#56 needs that)

Done. Can u help review this PR?


istio/pkg return structured.Error through error interface

structured logging/dictionary embeds data (labels, pointer to dictionary entry) which is rendered only when outputting to log. It's currently not possible to neatly return this data when returning an error from a function.

First pass at a solution: https://github.com/istio/pkg/pull/215
Needs some more iteration.

Fixed in https://github.com/istio/pkg/pull/236.


@supabase/auth-helpers-nextjs: upgrade devDependencies to Next.js v13

Chore
Describe the chore
@supabase/auth-helpers-nextjs has a devDependencies of "next": "^12.2.5".
I think this is causing a TypeScript issue with the context object (unstable_revalidate has been deprecated in v13):

Done.


Incorrect location for the Access Policies

At least based on the today's UI it is in a different section.
Module: Module 03 - Secure data and applications
Lab/Demo: 10 - Key Vault (Implementing Secure Data by setting up Always Encrypted)
Exercise 2: Configure the Key Vault resource with a key and a secret
Task 1: Create and configure a Key Vault
On the Key Vault blade, in the Settings section, click Access Policies and then click + Add Access Policy.
Fixes # .
Based on the UI it looks like this;

Changes proposed in this pull request:
Replace the "Settings" with "Quick Access Menu".

The correction was applied.


Design and create contacts page

[ ] Decide what text to be shown
[ ] Write all texts that are needed and add to database
[ ] Build the page and display

Text to show:
Image
Name
Bio/education
ex. Evalyn Horemans
Environmental Science, Montreal, Canada

Possible solution draft:

Need to make a /contacts endpoint in the backend


Import: resolve urls only once

Only resolve the urls for the current scenePath on sceneNode (instead of on merged root)
Tested with loading tron as relative path ./tangram -f tron/tron.yaml
@blair1618 This should also fix the issue with Android assets.

Good that Importer has do many unit test - I'll dig more into it tomorrow.

Yeah, the change I made for Android assets isn't sufficient - the same problem happens for the relative paths used in iOS/macOS app bundles. However, I was leaning towards giving more things an absolute URL.

I agree with the asset:// scheme approach to make URL resolution idempotent. Thought it would be nicer if URL resolution could be applied only once in the first place.


Code Refactoring

changes getDarajaPhoneNumber conditional from if to when

@MamboBryan All code changes should go through develop branch. To fix the CI build issue, merge the latest change from develop and the main branch into the chore/code-formatting branch and run the gradle command ./gradlew ktLintFormat and ./gradlew detekt from android studio.

Okay let me fix that ASAP


[BEAM-14112] Avoid storing a generator in _CustomBigQuerySource

Second attempt to avoid storing generator in _CustomBigQuerySource. See description from last attempt (#17100) below.
This time, export table schema is retrieved before the temp dataset is deleted. Because TableSchema is not picklable (see https://github.com/apache/beam/pull/17100#issuecomment-1075505398), I convert it into a JSON string before storing it as an instance variable.

Avoid storing a generator in _CustomBigQuerySource so that it can be used with the Python interactive runner. See details in https://issues.apache.org/jira/browse/BEAM-14112 .
Likely related to https://github.com/apache/beam/pull/15610

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

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

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

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

Run Python 3.8 PostCommit

Run PythonLint PreCommit

R: @KevinGG
R: @chamikaramj

Python integration tests passed in postcommit AFAICT, but there was a failure in :sdks:java:io:google-cloud-platform:expansion-service:shadowJar.

Python integration tests passed in postcommit AFAICT, but there was a failure in :sdks:java:io:google-cloud-platform:expansion-service:shadowJar.

Could you plz share information about the failure? The PR looks nice, IIUIC: similar to the reverted one but export the files before the temp dataset gets cleaned up. The reason to add the intermediate JSON conversion is because InteractiveRunner needs to pickle the PTransform while the table schema nor a generator are pickle-able as an attribute.

Could you plz share information about the failure?

I don't know much other than what the console output is showing. Something about failing to load/store cache entries.
14:29:57 [...]
14:29:57 FAILURE: Build completed with 2 failures.
14:29:57
14:29:57 1: Task failed with an exception.
14:29:57 -----------
14:29:57 * What went wrong:
14:29:57 Execution failed for task ':runners:flink:1.14:job-server:shadowJar'.
14:29:57 > Failed to load cache entry for task ':runners:flink:1.14:job-server:shadowJar'
14:29:57 [...]
14:29:57 2: Task failed with an exception.
14:29:57 -----------
14:29:57 * What went wrong:
14:29:57 Execution failed for task ':sdks:java:io:google-cloud-platform:expansion-service:shadowJar'.
14:29:57 > Failed to store cache entry for task ':sdks:java:io:google-cloud-platform:expansion-service:shadowJar'
14:29:57 [...]

Just to explore some other options other than converting schema to JSON, prior to #15610, there was no generator or TableSchema to cause pickling errors.
Instead of storing the generator as an instance attribute, a list of TextSource and notably its coder attribute were stored instead (we can assume use_json_exports=True for this discussion). The default coder, _JsonToDictCoder, had a method _convert_to_tuple to marshal the TableSchema into an object more amenable to pickling.
Perhaps I can use the same _convert_to_tuple method to create a picklable version of TableSchema and store that as an attribute rather than going the JSON route?

Could you plz share information about the failure?

I don't know much other than what the console output is showing. Something about failing to load/store cache entries.
14:29:57 [...]
14:29:57 FAILURE: Build completed with 2 failures.
14:29:57
14:29:57 1: Task failed with an exception.
14:29:57 -----------
14:29:57 * What went wrong:
14:29:57 Execution failed for task ':runners:flink:1.14:job-server:shadowJar'.
14:29:57 > Failed to load cache entry for task ':runners:flink:1.14:job-server:shadowJar'
14:29:57 [...]
14:29:57 2: Task failed with an exception.
14:29:57 -----------
14:29:57 * What went wrong:
14:29:57 Execution failed for task ':sdks:java:io:google-cloud-platform:expansion-service:shadowJar'.
14:29:57 > Failed to store cache entry for task ':sdks:java:io:google-cloud-platform:expansion-service:shadowJar'
14:29:57 [...]

I doubt this Python code change would affect the target :runners:flink:1.14:job-server:shadowJar, should be unrelated.

@chunyang, thanks for contributing to Beam and provide quality solutions to the issue! Is this PR still in active development?

Hi Ning, yes I plan to get back to this, just have been swamped with some
other things at the moment. Feel free to piggyback off of the work if you
have the bandwidth.
On Tue, Apr 5, 2022, 11:10 AM Ning Kang @.***> wrote:

@chunyang https://github.com/chunyang, thanks for contributing to Beam
and provide quality solutions to the issue! Is this PR still in active
development?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/17153#issuecomment-1089135887, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADPAHHCBGOZCWCRKVVMSGDVDR6XRANCNFSM5RL2RCVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi chunyang, I thought we had already fixed this in the other PR https://github.com/apache/beam/pull/17306. We can close this PR permanently if this is no longer an issue.

Woah strange, there's some email necromancy going on--I sent that last reply in April but for some reason Github shows it's from 9 hours ago. Anyway, we can close this as it's fixed in #17306 as you mentioned. Thanks!


frontend: injections don't work in legacy-content

See https://de.serlo-development.dev/mathe
Injections aren't shown and console throws error because of fonts:
downloadable font: download failed (font-family: "Karmilla" style:normal weight:400 stretch:100 src index:1): status=2147746065 source: https://de.serlo-development.dev/karmilla-regular.woff

Feature flags:
['client-frontend' => true, 'donation-banner' => true, 'frontend-content' => true, 'frontend-diff' => true, 'frontend-donation-banner' => true, 'frontend-editor' => true, 'frontend-footer' => true, 'frontend-legacy-content' => true, 'key-value-store' => true]

Also doesn't work in staging: https://de.serlo-staging.dev/mathe
This time, the font download error isn't shown (since the footer isn't active and therefore doesn't load global styles).
Feature flags:
['client-frontend' => true, 'donation-banner' => true, 'frontend-content' => true, 'frontend-diff' => true, 'frontend-donation-banner' => true, 'frontend-editor' => true, 'frontend-footer' => true, 'frontend-legacy-content' => true, 'key-value-store' => true]

The fonts error is strange, but may be unrelated to injections ...
Looking at the dev tools I see three ajax request made for each exercise, and the images are loaded, but when react renders the page client side, this would probably remove the injections from DOM again.
Proposal: Allow nextjs to render a page as static HTML and don't include any frontend javascript.

I'll try to make a PR for this ...


Mount secret to tide.

Mount secret to tide.
Problem description
Some error happens when we apply our new prow with our updated image of tide.
My Opinion
Is it possible that it's the consequence of forgetting to mount our github-token-robot secret token to tide?

can you squash to one commit?


Create update-version script to more easily update version

Similar to npm version, but updates the version number in all the
files we need to.
Usage:
./scripts/update-version.js [major|minor|patch]

It will:

Get current npm version.
Determine what type of version bump: major, minor, patch
Update the files:

package.json
android/gradle.properties
react-native-maps.podspec
react-native-google-maps.podspec

Make Git commit.
Create Git tag.

to: @lelandrichardson @gilbox
cc: @ljharb

If you add this script under "preversion", "version", or "postversion" then npm version should invoke it for you.

very cool! 👍

ok PTAL Jordan


Make slsa_source_correlated generic

This PR includes two related changes:
Make slsa_source_correlated generic

This commit modifies the rules in the `slsa_source_correlated` package
so they work with any SLSA Provenance attestation regardless of the
producer. Prior to this change, only attestations generated by Tekton
Chains were taken into account.

Make source_code_reference_provided a failure

Prior to this commit, the
`slsa_source_correlated.source_code_reference_provided` policy rule
generated a warning if the expected source code reference was not
provided in the input. When that information is not available, the other
policy rules in the package will pass because there is nothing to match
against. Given that it's easy to ignore errors in different contexts,
this behavior may give users a false sense of security.

This commit changes the policy rule to emit a violation instead of a
warning, making it obvious when an incorrect validation call needs to be
corrected.

These essentially bring in the validations provided by this sample policy package.
Ref: EC-679

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

Project coverage is 100.00%. Comparing base (44ad2c4) to head (27b636e).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1036   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          111       111
  Lines         5308      5341   +33
=========================================
+ Hits          5308      5341   +33

Files
Coverage Δ

policy/release/lib/attestations.rego
100.00% <100.00%> (ø)

policy/release/lib/attestations_test.rego
100.00% <100.00%> (ø)

policy/release/slsa_source_correlated.rego
100.00% <100.00%> (ø)

policy/release/slsa_source_correlated_test.rego
100.00% <100.00%> (ø)


How to create a docker image by using source code?

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
How to create a docker image by using source code? Is there any relevant guidance document here?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
master
💻 Operating System and Arch
centos8
🌐 Browser
google chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response

See https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

When i see the package.json.  "npm run build && node ./extra/env2arg.js docker buildx build -f docker/dockerfile --platform linux/amd64 -t louislam/uptime-kuma1 --target release . --load" is work for me

See https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

Thanks

while building the image
facing the above issue from last two days
container exited state after starting

@Aj7Ay I already answered you in https://github.com/louislam/uptime-kuma/issues/4645
Duplicate posts mean duplicate support effort..


v1.1 AboutUs.md

Includes each group member's name and picture. GitHub links and portfolio pages are also added for each member for further reference.
The distribution of responsibilities should be further discussed.

LGTM


Build files: when using $(CPP), use the C flags alongside the CPP flags

The reason for this is that some of the C flags affect built in macros
that we may depend on.

Merged.  8bc0147ff863bcf47dea5c71cf1d4f17b3b6914e


Test Only: Engage Filter Logic By Account type- allowance sub types

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)
[x] Does this have a dev link been provided in the design?
[x] Is this traceable to a feature, epic, or PI?

User Story
As a custom data download user I want the filter logic to function for account type So that I can avoid producing an allowance query with no results
Acceptance Criteria
Given that a user has applied account info or allowance holdings as a data sub type
When the filter panel functionality is displayed
Then the filter logic is engaged
Given that the filter logic is engaged for allowance transactions
When filter criteria is applied for account type
Then all other filters are narrowed based on the applied account type criteria
Given that a user has selected an allowance sub type (allowance holdings and account info)
When filter criteria is applied for account type
Then all other filters are narrowed based on the applied account type criteria
Given that the filter logic is engaged (allowance holdings, account info, allowance transactions)
When filter criteria is applied
Then the account type filter is narrowed based on the applied criteria
Given that the filter logic is engaged
When new filter criteria is applied
Then all previously selected criteria that are still valid are maintained
Given that the filter logic is engaged
When the filter panel functionality is displayed
Then non applicable selections are removed from the combo box filter list
AND grayed out from the check lists
Given that the filter logic is engaged
When account type criteria is removed (ex filter tags, filters)
Then the filters are narrowed based on the applied criteria
Given that the filer logic is engaged
When the the checklist functionality is displayed
Then the user can not select or apply filter criteria for greyed out items
Given that the filter logic is engaged
When the "select all" functionality is selected on the checklist component
Then the system selects criteria that is not greyed out
Given that the filter logic is engaged
When the checklist functionality is displayed
Then the select all functionality is disabled for groupings that only contain greyed out criteria
Development Notes

address account type filter logic for account info, allowance holdings, allowance transactions

Will need to switch over to using account type code instead of account type

The scope of this ticket includes the following:

Narrow other filters based on applied account type criteria
Narrow the account type filter based on applied criteria

Does this Story require 508 Testing?

[ ] Implementing a new authoring tool that will produce code / content for the application
[ ] Implementing a 3rd party widget that will be part of the application
[ ] Adding new / updating custom functionality
[ ] Adding new / updating a page template
[ ] Adding new / replacing existing functionality (unless the replacement has already passed 508 testing)
[ ] Full Site Review prior to a scheduled EPA 508 review
[ ] Planning a video that will appear on the application
[ ] Producing a video that will appear on the application
[ ] Producing Training materials
[ ] Producing documents

Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Dependency:

Will wait on the ERG to make db changes to work on this ticket.
Will need the script that the ERG ran to make the db changes

Testing
Test Case:TC470
Tester: @JanellC
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Is the user story ready to be deployed to the test/staging environments?

@tlageman-epa TC 470 Failed, bug logged to address the changes #2582


No timediff/timestamp in logs from go test

The time field is missing in Go test output (there's neither the full timestamp nor the 4-digit time diff), I don't set any special things besides lowering the log level to trace for the particular test.
I noticed this behavior after upgrading logrus from 1.7.0 to 1.7.1, the same also applies to v1.8.0.
Sometimes the time field is present for some time and then disappears randomly after few dozens of log lines.
I use Go 1.15 if that matters
expected (v1.7.0)
=== RUN   TestFoo
time="2021-02-18T14:06:52+01:00" level=trace msg="foo"

buggy (v1.7.1 and v1.8.0)
=== RUN   TestFoo
level=trace msg="foo"

OR
=== RUN   TestFoo
time="2021-02-18T14:06:52+01:00" level=trace msg="foo"
(...)
level=trace msg="bar"

I didn't see anything yet which could be the source of the behaviour. Would you mind sharing a trimmed down test case which would exhibit this bug ?


CLOUD-3171 add cookie jar for websocket client to handle liveid cookie

@tifayuki can you also take a quick look to this?

Why didn't we add all the cookie jar like the rest APIs, which also includes device_id?

I looked for a cookie jar implementation for the websocket client on Gorilla websocket but couldn't find any.
Maybe there is, but if there isn't I might submit a PR to the repo of the package

https://github.com/gorilla/websocket/pull/166 when this PR is merged we can merge this one

@tifayuki review again please


Forcefeeding is immediate, has no text log and cannot be prevented.

Description
Forcefeeding whether with pills, drinks, syringes or pneumatic cannons aimed at the skull is immediate, leaves no evidence besides a munching or slurping sound. This even works with pneumatic cannons. One recent round had a traitor RD filling his pneumatic cannon with lexorin and killing everybody on the station, bar one, who he explicitly allowed to live.
Steps:

Acquire a food object or container. A pill, syringe, beaker, slice of bread, pizza, etc.
Determine delivery method. By Hand? By Syringe? Or by Pneumatic Cannon?
Find your target. Click on them with the active item, or aim at the head with the pneumatic cannon and fire after following normal construction and loading procedures.
There is a quiet munching or slurping sound effect (completely silent if syringe) and your target will metabolise the reagents.

Solution: Have a timed bar, a visual log and stop the feeding procedure if there is a mask in the way (or exosuit item such as labcoat or hardsuit).
Screenshots

Additional context
It's infrequent to see, but it's extremely hard to prevent or even work out who's doing it when someone decides to use poisonous (i,e non explosive) chems en masse on everyone they come across.

#5582 Should fix the direct forcefeeding of food & drink part of this. Syringes need to be fixed separately.
The pneumatic cannon actually gets "buffed" by #5582 by not making the target swallow the food whole instead of nibbling on it ... maybe that's a bad idea? But on the other hand, we have logging now so it should be easy to find the culprit. And it's funny.
And yeah, masks & such should block all force feeding. I'm happy to work on that after the basic do-after PR is merged.

Can be closed after #5658 and #5656 are merged.


Adding code to extract (glass transition temperature) Tg and minor ad…

…ditions to extract melting point using Tm.

I got this when I run pytest:
Ran 348 test cases in 29.89s (12.40s CPU), 1 errors
28 modules OK (1 failed)
failures: /home/roselyne/ChemDataExtractor/tests/test_nlp_tokenize [1/120]
I don't think I have modified that file. I added some test for tg and tm and I believe they passed.

Thanks Matt!!!! I'm really glad to have participated!
On Thu, Feb 2, 2017 at 4:30 PM, Matt Swain<EMAIL_ADDRESS>wrote:

Merged #13 https://github.com/mcs07/ChemDataExtractor/pull/13.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mcs07/ChemDataExtractor/pull/13#event-947259321, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADfma554VxsbuqfkGAYS-zwPcMIMp3dKks5rYlkHgaJpZM4LtGsL
.


ADBDEV-5036: Fix gpstop -u not updating GUCs on segments

Fix gpstop -u not updating GUCs on segments
Backend process GUCs marked as GUC_GPDB_NEED_SYNC are overwritten by coordinator
upon receiving a new connection. The coordinator sends it's configuration to the
segments the same way as if it were a frontend communicating with the
coordinator. This means the default priority for these GUCs becomes client
priority.
Previously, when gpstop -u was executed, it sent a SIGHUP signal, prompting the
coordinator and segments to re-read their configuration files. However, the
priority of options derived from the configuration file is lower than that of
client options. This difference caused the segments to ignore overwritten
GUCs when they re-read their configuration files, and these GUCs were not
re-dispatched by the QD either. This situation resulted in a desynchronization
of GUCs that are required to be synchronized between the coordinator and the
segments.
The solution is to explicitly dispatch the changed configuration from the
coordinator to the segments, similar to how it is done when initializing the
backend process.
When the QD receives a SIGHUP signal, it reads its configuration file to
identify any GUCs that have been modified. If these GUCs are marked with the
GUC_GPDB_NEED_SYNC flag, the QD dispatches SET commands containing these
modified GUCs to the QEs. To differentiate between this type of synchronization
and user-initiated SET commands, a flag GP_OPT_SYNCHRONIZATION_SET has been
introduced to the distributed transaction options.

Allure report https://allure-ee.adsw.io/launch/66010

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1129929

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1129920

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1129922

Failed job Regression tests with Postgres on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1129921

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1129923

Allure report https://allure.adsw.io/launch/66592

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1157844

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1157845

Failed job Behave tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1157843

Allure report https://allure.adsw.io/launch/66678

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1163674

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1163675

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1163667

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1163669

Allure report https://allure.adsw.io/launch/66965

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179655

@RekGRpth If for some reason there's an error in the try block in send_guc_to_QE(), and we call DisconnectAndDestroyAllGangs(false) from the catch block, temp tables will be left in a half deleted state. Is this ok?
Repro:
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c
index fe0305111d4..85d47ad9b84 100644
--- a/src/backend/tcop/postgres.c
+++ b/src/backend/tcop/postgres.c
@@ -1581,6 +1581,7 @@ send_guc_to_QE(List *guc_list, bool is_restore)
                PG_TRY();
                {
                        DispatchSyncPGVariable(gconfig);
+                       elog(ERROR, "test");
                }
                PG_CATCH();
                {

In psql:
postgres=# create temporary table test(a int) distributed by (a);
CREATE TABLE
postgres=# \!gpstop -u
...
postgres=# select * from test;
ERROR:  relation not found (OID 366810)  (seg0 slice1 <IP_ADDRESS>:6002 pid=249929)
DETAIL:  This can be validly caused by a concurrent delete operation on this object.

Should we call DisconnectAndDestroyAllGangs(true) and CheckForResetSession() instead to finalize session reset?

Should we call DisconnectAndDestroyAllGangs(true) and CheckForResetSession() instead to finalize session reset?

Maybe this is a separate task?

Allure report https://allure.adsw.io/launch/66987

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179867

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179868

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179864

Allure report https://allure.adsw.io/launch/67123

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1188422

Allure report https://allure.adsw.io/launch/67145

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1189299

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1189300

Allure report https://allure.adsw.io/launch/67162

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1190195

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1190196

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1190192

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1190187

Some remarks of the description:
gpstop -u not updating -> gpstop -u doesn't update
The segment’s backend process GUCs marked -> backend process GUCs, which are marked
the segments as if it -> the segments the same as
some frontend that communicates -> which communicates
configuration file is lower than that client’s configuration -> than the client’s
GUCs with overwritten values are not read -> don't read
They are not re-sent either -> don't re-sent
These GUCs become desynchronized -> These GUCs are desynchronized
The solution is to explicitly re-send -> The solution is to re-send explicitly

Allure report https://allure.adsw.io/launch/67538

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210248

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210249

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210246

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210240

Failed job Regression tests with Postgres on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210241

new flaky test?
DIFF FILE: ../gpdb_src/src/test/regress/regression.diffs
----------------------------------------------------------------------
--- \/home\/gpadmin\/gpdb_src\/src\/test\/regress\/expected\/dispatch\.out	2024-03-27 07:19:55.439070087 +0000
+++ \/home\/gpadmin\/gpdb_src\/src\/test\/regress\/results\/dispatch\.out	2024-03-27 07:19:55.475071263 +0000
@@ -1210,10 +1246,9 @@
 -- present. If it's not, something is terribly wrong and we were silently
 -- disconnected.
 SELECT * FROM dispatch_test_session_not_dead;
- a
----
-(0 rows)
-
+ERROR:  relation not found (OID 67184)
+DETAIL:  This can be validly caused by a concurrent delete operation on this object.
 DROP TABLE dispatch_test_session_not_dead;
+ERROR:  table "dispatch_test_session_not_dead" does not exist
 DROP FUNCTION show_on_segments(show_name text);
 DROP ROLE dispatch_test_user2;

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210242

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1210243

new flaky test and test?

FYI: not flaky, these are new tests that cover more cases. The method used in this patch probably would not work for synchronization, because it does not account for dispatching SET from non-superuser roles. Currently, I'm looking into the problem to see what can be done, but this patch will probably be scrapped for another approach.

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1235550

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1235551

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1235543

fix abi test

Allure report https://allure.adsw.io/launch/68303

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1240843

Allure report https://allure.adsw.io/launch/68324

Allure report https://allure.adsw.io/launch/68370

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1241831

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1241824

Allure report https://allure.adsw.io/launch/68643

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1259919

Allure report https://allure.adsw.io/launch/68648

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1260222

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1260659

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1260660

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1260656

Allure report https://allure.adsw.io/launch/68671

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1262276

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1262277

After some discussion, tests for problem related to https://github.com/arenadata/gpdb/pull/881#issuecomment-2006929685 were decided to be moved to a different PR.

Allure report https://allure.adsw.io/launch/68895

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1274943

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1274944

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1274937

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1274938

Allure report https://allure.adsw.io/launch/69086

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1285025

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1285026

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1285023


Minor edit to correct numbering in the comment/documentation of testShowScale() method.

Minor edit to correct numbering in the comment of testShowScale() method inside the MapTest class, which unit tests the Map component.
Edited ! to 1 in the comment of testShowScale() method of the MapTest.java class.

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


Error handling in constructors

Description of change
Error handling in constructors
Links to any relevant issues
Fixes #692
Type of change

Bug fix (a non-breaking change which fixes an issue)

How the change has been tested
import { Wallet, initLogger } from '@iota/sdk';
require('dotenv').config({ path: '.env' });

async function run() {
    initLogger();
    try {
        const wallet = new Wallet({
            storagePath: process.env.WALLET_DB_PATH,
            secretManager: {
                stronghold: {
                    snapshotPath: `example.stronghold`,
                    password: "a", // wrong password
                },
            },
        });
    } catch (error) {
        console.error('Error: ', error);
    }
}

run().then(() => process.exit());

prints now
Error:  Error: {"type":"error","payload":{"type":"wallet","error":"`invalid stronghold password`"}}

instead of
thread '<unnamed>' panicked at 'error initializing wallet: Client(Stronghold(InvalidPassword))', bindings/nodejs/src/wallet.rs:38:14

Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that new and existing unit tests pass locally with my changes

Error:  Error: {"type":"error","payload":{"type":"wallet","error":"invalid stronghold password"}}
Can we remove one of these Error?

Can we remove one of these Error?
Do you mean mean the Error: or in the JSON?

Can we remove one of these Error?

Do you mean mean the Error: or in the JSON?

Yeah I guess the first one since we already have one in the JSON

Can we remove one of these Error?

Do you mean mean the Error: or in the JSON?

Yeah I guess the first one since we already have one in the JSON

Ignore me that's just a dummy example, I'm a bit sleepy today.


Clarify on homepage that without meltano select, all entities and properties are selected by default

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2034
Originally created by @DouweM on 2020-05-15 16:25:07

View 3 previous comments from the original issue on GitLab